The real 5-year TCO of staying on your current stack
The cost of staying on a legacy content platform compounds every year. A working model for the true 5-year TCO, including the four cost categories that never appear on the vendor invoice.
Every year a legacy content platform stays in production, its real cost rises. Maintenance consumes more engineering time, vendor contracts escalate at renewal, and the integration work required to connect the platform to modern tools accumulates. The 5-year cost of staying is almost always higher than the cost of migrating. Discovering this at year four costs more than modelling it at year one.
Why the invoice is not the cost
The line item in the finance system captures the visible spend: platform license, hosting, support contract. It does not capture four categories of cost that grow every year on a legacy platform and that, together, typically exceed the visible spend by a factor of two to three.
Maintenance engineering
Maintenance absorption on legacy enterprise CMSes varies widely depending on codebase age and technical debt load. Organisations running lighter implementations may be closer to 25%; those with years of accumulated workarounds and custom integrations run significantly higher. The model uses 40% as a working input for a heavily customised platform, which is conservative for the systems that most commonly prompt a migration conversation.
At a team of 10 engineers with a fully-loaded annual cost of $150,000 each, 40% maintenance absorption means $600,000 per year in engineering capacity not building anything new.
Vendor contract escalation
Enterprise platform contracts do not hold flat at renewal. It is common to see double-digit price increases at the next contract cycle with no change in scope and no new features, simply a higher number. NPI Financial’s analysis of enterprise SaaS procurement puts the average annual price increase across the market at 8.7%, with larger software estates consistently seeing higher figures. NPI notes that at least 9 cents of every IT software dollar now goes toward paying more for capabilities already owned.
Technical debt accumulation
Profound Logic’s industry analysis of legacy application maintenance puts technical debt growth at approximately 20% annually when left unaddressed. That rate compounds: a codebase with moderate debt in year one has materially more in year three, as patch-on-patch remediation and custom integration workarounds layer on top of each other. The practical result is that the same engineering task costs more every year: features take longer to ship and incidents take longer to resolve, with no change to the team or the vendor contract.
Opportunity cost
When a legacy platform constrains marketing, product, or AI initiatives, the organisation pays an opportunity cost that is difficult to model but not difficult to estimate. A content platform that prevents a campaign from launching in three weeks instead of twelve has a calculable revenue impact. A platform that cannot support the content layer an AI initiative requires introduces delay with a cost.
The compounding model: year by year
The following model represents a mid-market organisation running a commercial enterprise CMS (AEM, Sitecore, or WordPress VIP) with these baseline assumptions:
- Annual platform license/contract: $300,000
- Hosting and infrastructure: $60,000
- Engineering team: 10 engineers at $150,000 fully-loaded annually
- Maintenance absorption rate: 40% of engineering time
- Annual contract escalation rate: 8% (NPI Financial enterprise benchmark)
- Annual productivity degradation from technical debt: 15% (conservative estimate)
Year 1 baseline
| Cost category | Annual amount |
|---|---|
| Platform license / contract | $300,000 |
| Hosting and infrastructure | $60,000 |
| Maintenance engineering (40% of 10 engineers × $150K) | $600,000 |
| Integration and workaround development | $80,000 |
| Year 1 total | $1,040,000 |
The $300,000 is what shows in the finance system. The $1,040,000 is what the organisation actually pays.
Year 2
Contract escalates at 8% and maintenance absorption increases as integration debt grows. Technical debt degradation adds 15% to per-change engineering cost, showing up as longer timelines for the same output.
| Cost category | Annual amount |
|---|---|
| Platform license / contract (+8%) | $324,000 |
| Hosting and infrastructure (+5%) | $63,000 |
| Maintenance engineering (+15% time absorption growth) | $690,000 |
| Integration and workaround development (+20%) | $96,000 |
| Year 2 total | $1,173,000 |
Year 3
By year 3, the compound effect is visible. The contract is 17% above the year-1 baseline, maintenance absorption continues growing, and the organisation begins experiencing operational symptoms: deploys that took days now take weeks, incidents that took hours now take days.
| Cost category | Annual amount |
|---|---|
| Platform license / contract (+8%) | $350,000 |
| Hosting and infrastructure (+5%) | $66,000 |
| Maintenance engineering (+15%) | $793,500 |
| Integration and workaround development (+25%) | $120,000 |
| Year 3 total | $1,329,500 |
Year 4
By year 4, the organisation is paying 26% more in contract costs for the same platform capabilities. The gap between what the platform can do and what the business needs has widened every quarter.
| Cost category | Annual amount |
|---|---|
| Platform license / contract (+8%) | $378,000 |
| Hosting and infrastructure (+5%) | $69,000 |
| Maintenance engineering (+15%) | $912,525 |
| Integration and workaround development (+30%) | $156,000 |
| Year 4 total | $1,515,525 |
Year 5
By year 5, the platform is 36% more expensive on contract alone than it was at the start. The engineering team is spending nearly twice what the license costs just keeping the system running.
| Cost category | Annual amount |
|---|---|
| Platform license / contract (+8%) | $408,000 |
| Hosting and infrastructure (+5%) | $72,450 |
| Maintenance engineering (+15%) | $1,049,404 |
| Integration and workaround development (+35%) | $210,600 |
| Year 5 total | $1,740,454 |
5-year summary
| Cost category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 | 5-year total |
|---|---|---|---|---|---|---|
| Platform license | $300K | $324K | $350K | $378K | $408K | $1,760K |
| Hosting | $60K | $63K | $66K | $69K | $72K | $330K |
| Maintenance engineering | $600K | $690K | $794K | $913K | $1,049K | $4,046K |
| Integration / workarounds | $80K | $96K | $120K | $156K | $211K | $663K |
| Annual total | $1,040K | $1,173K | $1,330K | $1,516K | $1,740K | $6,799K |
The 5-year cost of staying: $6.8 million, against a platform line item that looked like $1.5 million over the same period.
The migration alternative: what the same 5 years looks like
For comparison: a migration to a composable stack (Payload + Next.js) with a one-time migration investment, followed by lower recurring costs.
| Cost category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 | 5-year total |
|---|---|---|---|---|---|---|
| Migration cost (one-time) | $200K | $0 | $0 | $0 | $0 | $200K |
| Platform license (Payload: $0) | $0 | $0 | $0 | $0 | $0 | $0 |
| Hosting and infrastructure | $15K | $15K | $18K | $18K | $20K | $86K |
| Maintenance engineering (20% absorption post-migration) | $300K | $315K | $331K | $347K | $365K | $1,658K |
| Integration and workaround development | $30K | $30K | $35K | $35K | $40K | $170K |
| Annual total | $545K | $360K | $384K | $400K | $425K | $2,114K |
The 5-year cost of migrating: $2.1 million, including the full migration investment. The 5-year savings: $4.7 million.
The breakeven point in this model is month 18, when the cumulative cost of the migration path crosses below the cumulative cost of staying. This is consistent with what modernisation research documents: Mobisoft Infotech’s analysis of legacy modernisation projects reports payback periods commonly within the first 12 to 18 months, with 200 to 300% ROI over three years as a typical outcome.
The variables that move the output
The model above uses specific assumptions. Four variables determine what the number is for any individual organisation.
Maintenance absorption is set at 40%, a working input for a heavily customised legacy CMS. Organisations running cleaner implementations may be closer to 25%; those with extensive integration layers or long-standing custom code frequently run at 55 to 65%. Each additional 10% adds approximately $150,000 per year at a 10-engineer, $150K fully-loaded team.
Contract escalation is set at 8%, the NPI Financial enterprise benchmark. Renewal uplifts of 20% or more do occur in enterprise contracts, and each additional 5% in the escalation rate adds approximately $85,000 to $200,000 over five years depending on the contract base value.
Migration cost is assumed at $200,000, reflecting a mid-size marketing site migration with standard content types and no mobile app complexity. Migrations involving multiple surfaces, custom integrations, or compliance requirements in regulated industries run higher, typically $300,000 to $600,000. At $600,000, the 5-year savings in this model remain above $4 million.
Post-migration maintenance absorption is set at 20%, down from 40% on the legacy platform. McKinsey’s research on banking technology found that at large banks, up to 70% of IT budgets go toward run-the-bank activities including legacy maintenance, with high-performing technology transformations targeting a reversal of that ratio. For non-banking organisations the ratio varies, but the directional shift from migrating off legacy infrastructure is consistent across industries.
How to build your organisation’s version
Four numbers produce a version of this model with your actual inputs.
- Your current all-in platform cost,
not just the license. Add the contract value, the hosting or infrastructure cost, and the engineering time spent on maintenance. For engineering time: estimate the percentage of your engineering team's hours that go to maintaining the platform rather than building new features, then multiply by headcount and average fully-loaded cost. - Your contract escalation history.
Look at the last two or three renewals. What was the percentage increase each time? If you do not know, this is the first data gap to close. Your vendor's renewal team knows the number. - Your integration overhead.
Estimate the engineering time spent building and maintaining workarounds for things the platform cannot do natively: custom integrations, non-standard deployment configurations, manual processes that exist because the platform does not support automation. This cost is frequently invisible in the budget because it is buried in sprint work. - A migration cost estimate.
A scoped discovery engagement produces a specific number. Before that, the range for a mid-market CMS migration is $150,000 to $500,000 depending on scope. The midpoint works as a placeholder.
With those four inputs, the model above becomes your organisation’s number rather than a benchmark.
What this model doesn’t capture
This model quantifies four cost categories. Two additional categories are real but harder to put a number on.
Security exposure. IBM’s Cost of a Data Breach Report 2024 puts the average global breach cost at $4.88 million. Organisations running outdated platforms and end-of-life software, no longer receiving security updates, carry elevated exposure relative to that average. Organisations in regulated industries should add a risk-weighted estimate to their 5-year calculation.
Competitive cost. Organisations whose content platform cannot support personalisation, mobile delivery, AI integration, or rapid campaign deployment pay a cost relative to those whose platforms can. Quantifying it in a TCO model is difficult, but migration advocates should name it in the board conversation rather than leaving it implied.
FAQ
-
What is total cost of ownership (TCO) for a CMS?
CMS total cost of ownership is the sum of all costs associated with running the platform over a defined period: platform licensing or contract fees, hosting and infrastructure, engineering time for maintenance, and integration development for connecting the platform to other systems. Most organisations calculate only the first two categories. The complete TCO is typically two to three times the visible contract value when maintenance engineering and integration costs are included.
-
How fast do legacy CMS maintenance costs grow?
Profound Logic's industry analysis of legacy application maintenance puts technical debt growth at approximately 20% annually when unaddressed. That compounds: an organisation spending $1 million on legacy maintenance in year one will spend approximately $1.5 to $2 million on the same system in year five, not because the platform changed but because the debt accumulated. LegacyLeap's analysis of legacy system maintenance costs puts the annual increase at 10 to 20% when left unaddressed, consistent with the technical debt growth rate applied conservatively.
-
What is a typical payback period for a CMS migration?
Modernisation investment analyses commonly document payback periods within the first 12 to 18 months for enterprise systems, with ROI of 200 to 300% over three years. The payback period depends primarily on three variables: the pre-migration maintenance cost (higher costs produce shorter payback periods), the migration cost (lower costs produce shorter payback periods), and the post-migration maintenance reduction (larger reductions produce shorter payback periods). For most mid-market CMS migrations, the breakeven falls between months 12 and 24.
-
What is the maintenance-to-innovation ratio on legacy IT systems?
McKinsey's research on banking technology found that "run the bank" activities, including legacy maintenance, consume up to 70% of IT budgets at large banks, leaving 30% or less for capability investment. The research documents high-performing technology transformations targeting a reversal of that ratio. The specific ratio varies by industry and organisation, but the direction is consistent: legacy maintenance crowds out investment in new capability, and the crowding gets worse as debt accumulates.
-
What does "technical debt compounds at 20% annually" mean in practice?
If a legacy system carries $500,000 in accumulated technical debt, that figure reaches $600,000 after one year if unaddressed, then $720,000 after two years. In practice this shows up as features that take progressively longer to ship, incidents that take progressively longer to resolve, and integrations that require progressively more custom work to maintain. The cost comes out of engineering output, not the vendor invoice.
-
How much does a CMS migration cost?
For a mid-market organisation with a standard marketing site (one domain, standard content types, no mobile app, no compliance-specific requirements), migration projects typically run $150,000 to $300,000. Organisations with multiple surfaces, complex content models, regulatory compliance requirements, or significant content volume run higher, typically $300,000 to $600,000. At $600,000, the 5-year savings from migrating off a $300,000-per-year enterprise platform contract typically exceed the migration cost by a factor of three to five.
WAYF builds content platform migrations, and can help you model the cost case before you commit to one.
Sources
- NPI Financial: The End of Easy SaaS — How Vendor Economics Are Reshaping Enterprise Procurement* IBM: Cost of a Data Breach Report 2024
- McKinsey: Winning in digital banking — legacy technology and IT spending
- LegacyLeap: The True Cost of Maintaining Legacy Systems in 2026
- Profound Logic: The True Cost of Maintaining Legacy Applications
- Mobisoft Infotech: Legacy System Modernization — Strategy, Cost and ROI 2026
We're booking content platform
engagements for 2026.
Twenty-five minutes to walk through the work and decide if we're the right team for it. Scoping and a fixed price come after.