The hidden costs of staying on a legacy CMS

When a team weighs whether to stay on an ageing content platform, the number that comes up first is the licence fee, because it is the one on the invoice. That number is almost never the real cost. The larger spending sits in places no line item captures: the time people lose working around the system, the risk that accumulates as it ages, and the value of the things the platform prevents you from doing at all. None of it shows up when you compare renewal quotes, which is exactly why it is worth naming.

This is the buyer’s map of those hidden costs. For a worked financial model that puts numbers against them, our colleagues laid out the real 5-year cost of staying on your current stack. This piece is the plain-language version of what that model is measuring.

The cost of waiting

The most expensive thing a legacy CMS does is make people wait. When the marketing team cannot publish without a developer, every routine change enters a queue. A landing page that should take an afternoon takes a sprint. A price correction waits for the next release. Multiply that by every content change across a year and you have a standing tax on the speed of the whole business, paid in salaried hours and in opportunities that closed while the change sat in a backlog. It never appears as a cost because nobody invoices for a delay, but it is real and it compounds.

The cost of workarounds

An old platform that no longer fits accumulates custom code whose only job is to make it behave: plugins, patches, and conventions layered on over years. Each of those is software someone has to maintain, understand, and be careful around. The cost is engineering attention spent keeping the existing thing standing rather than building anything new, and it grows with every workaround added. When onboarding a developer means teaching them the list of things not to touch, that is the workaround tax made visible.

The cost of licences you have stopped noticing

Legacy platforms rarely sit alone. Around them grows a ring of subscriptions bought to cover their gaps: the plugin with its own fee, the hosting add-on, the third-party service filling a hole the CMS left. Each one is small on its own, but the ring around a legacy platform adds up to a real number, and it usually stays invisible to whoever signs the renewals because no single line item is big enough to question. Our piece on the shadow stack of SaaS subscriptions covers how much of this a large organisation typically carries without realising. Per-seat editor pricing belongs in this category too: a model that charges for every person who touches the content quietly penalises the thing you actually want, which is more people able to contribute.

The cost of risk

Every year a platform ages without being kept current, the risk attached to it rises. Deferred upgrades pile up. Security patches sit unapplied because nobody is confident they are safe to install. And underneath it all, many legacy products have a vendor end-of-support date, after which security fixes simply stop. Reaching that date does not break the site on the day, but it converts a manageable project into an urgent one, usually on someone else’s timeline rather than yours. Our CMS end-of-life matrix shows where the major platforms stand. The cost of risk is the cost of a forced migration later, at a worse moment, instead of a planned one now.

The cost of what you never ship

The hardest cost to see is the one that never happens. A platform that cannot deliver content to a mobile app, cannot support a second market without a second build, or cannot feed the structured content that newer tools expect, is quietly setting the ceiling on what the business can do. The AI shift has sharpened this: systems that cannot expose content in a structured, machine-readable form are increasingly locked out of the tools built on top of it, a cost we covered in the AI tax on legacy stacks. Opportunity cost does not appear in any budget, because you cannot invoice for a product you were never able to build. It is often the largest number of all.

Why none of this is on the invoice

These costs stay hidden for a structural reason: each one is spread thin, a few hours of waiting here, a small subscription there, a risk that has not yet come due, an opportunity that quietly closed, and no single instance is large enough to demand attention on its own. The renewal quote, by contrast, is a single visible number, which is why the decision to stay usually gets made by comparing it against a migration quote and stopping there.

The honest comparison weighs the licence fee against the migration cost, and it also weighs the waiting, the workarounds, the risk, and the closed-off opportunities against the one-time cost of moving. When you weigh it that way, the answer changes for a lot of teams, though not for all of them: if your current setup is genuinely well matched to what you need, staying is the right call. If you want help doing that comparison honestly, including the parts that are hard to price, book a call and we will work through it with you.