Who this is for
Business owners and finance leaders who suspect a legacy system is costing more than it's worth but need a framework to confirm it.
Question this answers
How do I calculate whether our old system costs more to maintain than it would cost to replace?
What you'll leave with
- The hidden costs most businesses don't track
- A framework for calculating true total cost of ownership
- Clear warning signs that a system has become a net liability
- How to build the case for replacement
The hidden costs of legacy systems
When asked "how much does this system cost?" most businesses answer with the direct costs: licensing, hosting, support contract. But those are typically only 30-40% of the real figure.
The rest is hidden across the business:
- Workaround time: Staff exporting to Excel, manually reformatting data, re-keying information between systems
- Integration friction: Custom middleware, manual data transfers, scripts that nobody fully understands
- Training overhead: New staff take longer to learn clunky systems; institutional knowledge is needed for basic tasks
- Opportunity cost: Features you can't build, integrations you can't make, customers you can't serve
- Risk cost: What would a system failure actually cost? What about a security breach through unpatched vulnerabilities?
- Morale cost: Hard to quantify, but real — team frustration with tools affects retention and productivity
Calculating the true cost
Use this framework to estimate the total annual cost of your legacy system:
- Direct costs: Licensing + hosting + support contracts + maintenance developer time
- Indirect labour costs: Hours per week spent on workarounds × hourly cost × 48 weeks
- Integration costs: Cost of maintaining custom connections, middleware, manual data transfers
- Error costs: Estimate the cost of errors caused by the system per year (rework, customer impact, compliance issues)
- Opportunity cost: Estimate revenue or efficiency lost because the system can't support new requirements (this is the hardest to quantify — use conservative estimates)
Total annual legacy cost = Direct + Indirect labour + Integration + Error + Opportunity
Warning signs
Your system is probably a net cost if
- Maintenance costs have increased year-on-year for 3+ years
- Staff regularly export data to Excel to do their actual work
- You've turned down business because the system couldn't support it
- New staff complain about the system within their first month
- The one person who understands it is a single point of failure
- You're paying for custom middleware just to connect it to other systems
- Security updates are no longer available from the vendor
The break-even analysis
Once you have the total annual legacy cost, compare it to replacement cost:
- Replacement cost: Get a ballpark estimate for building or buying a replacement (including data migration, training, and transition costs)
- Break-even period: Replacement cost ÷ (Annual legacy cost – Annual new system cost) = years to break even
If the break-even period is under 3 years, replacement is almost always the right financial decision. Under 2 years, it's urgent.
What to do about it
- Run the numbers: Use the framework above to calculate your true legacy cost. Be honest about the hidden costs.
- Get replacement estimates: Talk to development partners about ballpark replacement costs.
- Present the case: Frame it as a financial decision, not a technology decision. "This system costs us $105K/year. Replacing it costs $80K. Break-even is 14 months."
- Start small: If the full replacement is too large, identify the highest-cost component and modernise that first.
Key takeaways
- Direct licensing and hosting costs are only 30-40% of the true cost — the rest is hidden in workarounds, lost time, and missed opportunities
- If staff spend more than 2 hours per week working around the system, those hours are a direct legacy cost
- Opportunity cost is real: business you can't win because the system can't support it
- When annual total cost exceeds 25-30% of replacement cost, replacement usually makes financial sense
- The decision should be quantitative, not emotional — use the framework, run the numbers