Most enterprises running CFML today are not running it by accident. The application works, it encodes years of business rules, and replacing it carries risk that rarely appears in the rewrite budget.
The real cost of a rewrite
A rewrite does not just reproduce features — it has to reproduce undocumented behaviour that the business has quietly depended on for a decade.
- Business rules buried in query logic and scheduled tasks
- Integrations with reporting, finance, and identity systems
- Edge cases that only surface at month-end or year-end
- Retraining and change management for internal users
When support is the right call
- The application is stable and the backlog is mostly small fixes
- Your risk is concentrated in security posture, not architecture
- The original team has moved on and you need continuity, not change
The modernization middle ground
Between 'leave it alone' and 'replace it' sits the option most teams actually need: upgrade the engine, harden the server, tune the database, and expose modern APIs so new front ends can be built incrementally.