Legacy System Cost: A Working Definition
A legacy system is one where the cost of ownership, visible and hidden, is growing faster than the value it delivers. The defining financial signal: maintenance and support are consuming the majority of the IT budget, leaving insufficient capacity for development and growth.
What Makes a System "Legacy" in Financial Terms
The simplest financial test for a legacy system is whether the cost of keeping it running is growing faster than the value it produces. A system that was a sound investment five years ago can cross into legacy territory not because it has broken down, but because the maintenance burden has grown to the point where it is consuming resources that would otherwise fund capability development.
The most useful diagnostic number is the ratio of maintenance spend to development spend within the IT budget. In a well-functioning technology environment, maintenance typically accounts for 30–40% of IT spend, with the remainder going on building new capabilities. Legacy systems invert that ratio. The UK Government's State of Digital Government Review (January 2025) found that many organisations spend 70–85% of their technology budgets on upkeep rather than modernisation, compared to around 60% among digital leaders in the private sector.
Legacy vs Modern System — Cost Profile
| Legacy System | Modern System | |
|---|---|---|
| Maintenance share of IT budget | 70–85% | 30–40% |
| Integration cost per new tool | £5,000–£20,000 custom build | Near-zero standard connection |
| Specialist day rate | £600–800 | £400–500 |
| Security patching | None (end-of-life) | Vendor-managed |
| Typical annual cost growth | 10–15% | Predictable, contractual |
| Change delivery time | 3–5× longer than benchmark | Benchmark |
A UK SMB with an annual IT budget of £200,000, of which £150,000 is committed to supporting an existing ERP, is running at 75% maintenance. At that ratio, the technology function is a cost centre rather than a value driver, and it is unlikely to change without deliberate intervention.
The Iceberg Model: Visible and Hidden Costs
Because the problem's structure is similar to that of an iceberg — a visible, easily measurable portion above the waterline and a larger, more consequential mass below — the iceberg is a helpful tool for thinking about legacy system costs.
Things you can see, such as licensing, hosting, support contracts, and dedicated IT staff, typically account for 30–40% of the true cost. The remaining 60–70% sits in operational budgets, absorbed into headcount across the business, or spread across project expenditure that has never been traced back to the system causing it.
Visible Costs
The costs that appear in the IT budget are: software licensing and subscription fees, hosting and infrastructure, vendor support and maintenance contracts, the salaries of staff whose primary role is maintaining the system, and external contractor costs for routine maintenance. For the majority of businesses using legacy systems, these numbers are already higher than they should be, and they tend to rise annually as vendors prey on clients who have few viable options.
Hidden Cost 1: Maintenance Overhead
Every legacy system accumulates a layer of unofficial processes over time. To manage tasks that the system is unable to automate, staff members create workarounds, which are then ingrained in the daily routine. Consider a single example: one member of staff who spends 45 minutes each morning manually transferring data between two systems because the integration no longer functions correctly. At £15 per hour, that is roughly £2,800 per year for one task performed by one person. A typical SMB running on legacy software has dozens of tasks like this distributed across the team. None of them is important enough on their own to show up in any budget report, but collectively they represent a substantial and invisible overhead.
McKinsey & Company research found that the accumulated cost of these deferred decisions and workarounds, commonly referred to as technical debt, can account for up to 40% of the total value of an organisation's technology estate. Our guide to technical debt explains how that accumulates over time.
Hidden Cost 2: Opportunity Cost of Slow Delivery
Development work on a legacy system takes three to five times longer than equivalent work on a modern platform, and the financial consequence of that delay is rarely calculated. An e-commerce business that cannot launch mobile checkout because the legacy backend does not support modern payment integrations is facing more than a future development cost. For every month that feature is unavailable, the business loses revenue to competitors who already offer it. That lost revenue does not appear on any invoice and is not attributed to the IT system, though it is a direct financial consequence of running on legacy infrastructure.
Hidden Cost 3: Integration Tax
A CRM, an accounting platform, a logistics provider, and a payment processor must all be able to communicate with one another in order for modern business operations to function. When the core system is legacy, each of those connections requires custom development rather than a standard integration. A single custom integration with a legacy system typically costs between £5,000 and £20,000, depending on the complexity. A business that has added three new tools over the past two years and required custom integration work for each has spent £15,000–£60,000 on connections that would have been near-zero cost on a modern platform. That expense is distributed across project budgets and is almost never attributed to the legacy system that necessitated it.
Hidden Cost 4: Talent Premium
The number of developers who are still working with older technologies, including Delphi, COBOL, Visual Basic 6, and older versions of .NET, is decreasing, and the specialists who remain command rates that reflect scarcity. In the UK, legacy technology contractors typically charge £600–800 per day, compared to £400–500 for modern stack equivalents. Beyond the direct rate difference, there is a concentration risk that carries its own financial exposure. When a single person holds critical knowledge about a system, their departure sets off a recovery process that few businesses have estimated in terms of recruitment, contracting, and operational disruption costs.
Hidden Cost 5: Compliance and Security Risk
Software that no longer receives vendor support accumulates known vulnerabilities with no available remediation. The NCSC reports that 1 in 2 small UK businesses suffers a cyber incident every year, and unsupported software is consistently identified as one of the most exploited entry points. Managing the resulting exposure requires additional monitoring, manual controls, and compensating processes that substitute for protections the system can no longer provide natively. Should an incident occur, UK GDPR fines run up to £17.5 million or 4% of global annual turnover, thresholds that apply equally to a 20-person firm and a large corporate.
Hidden Cost 6: Staff Productivity Loss
The productivity cost of a slow or unreliable system is calculable, despite the fact that it is rarely included in any formal analysis. A system that takes two minutes to load at each login, used by 20 people who log in five times daily, accounts for approximately 800 hours per year of idle time. At an average fully-loaded cost of £20 per hour, that is £16,000 annually from a single system limitation across a single team.
Hidden Cost 7: Vendor Lock-In Premium
The competitive pressures that normally constrain vendor pricing cease to operate when switching platforms is too costly or technically difficult. Annual price increases of 10–20% are common for legacy systems whose customers have limited realistic alternatives. These increases are absorbed by the business annually because the perceived cost of migration is still greater than the cost of the most recent price rise. This calculation is consistent until the cumulative total is discussed by the board.
How to Calculate Your Legacy System's True Cost
Step 1: Map All Direct Costs
Start with what is already visible: licensing, hosting, support contracts, the proportion of IT staff salaries attributable to the system, and external contractor costs. Get these from an accountancy system, bills from vendors, and a breakdown of the IT budget. This is the starting figure, not the complete picture.
Step 2: Quantify the Hidden Costs
Work through each hidden cost category methodically. The table below shows the calculation approach and illustrative figures for a UK SMB of 30–50 people.
TCO Calculator — Illustrative Figures
| Cost Category | How to Measure | Illustrative Annual Figure |
|---|---|---|
| Visible costs | Finance system + vendor invoices | £150,000 |
| Maintenance overhead | Hours on workarounds × staff cost | £18,000 |
| Opportunity cost | Delayed project revenue estimates | £25,000+ |
| Integration tax | Custom integration projects ÷ 3 years | £12,000 |
| Talent premium | Legacy rate vs modern rate × days | £8,000 |
| Compliance and security | Cost of compensating controls | £6,000 |
| Productivity loss | Idle hours × fully-loaded staff cost | £16,000 |
| Vendor lock-in | Annual price increase over market rate | £4,000 |
| Estimated true total | ~£239,000 |
Figures are illustrative. Your numbers will differ depending on system complexity, team size, and sector.
Businesses that begin this exercise expecting a figure of £150,000 per year regularly arrive at £250,000–£350,000 once the hidden costs are included.
Step 3: Project the Three-Year Trajectory
Legacy costs are not static. Vendor prices increase, the specialist talent pool contracts, and workarounds multiply year on year. Project the current total cost forward at a growth rate of 10–15% annually and compare that trajectory against the projected cost of legacy system modernisation.
Three-Year Projection — Status Quo vs Modernisation
| Year 1 | Year 2 | Year 3 | Total | |
|---|---|---|---|---|
| Status quo (£200k base, +15%/yr) | £230,000 | £255,000 | £275,000 | £760,000 |
| After modernisation (£150k upfront + £100k/yr) | £250,000 | £100,000 | £100,000 | £450,000 |
| Saving | –£20,000 | +£155,000 | +£175,000 | +£310,000 |
Break-even at approximately 18 months. Figures illustrative — actual numbers depend on the system and context.
The "Do Nothing" Fallacy
Choosing not to change is not a cost-free decision. The cost of the status quo is real; it is simply distributed across multiple budget lines and absorbed gradually, rather than appearing as a single approved expenditure. Nobody signs off on a decision to spend £760,000 over three years maintaining a legacy system. The money leaves in increments, across IT, operations, HR, and project budgets, with nothing to make the total visible at once.
The UK Parliament's Public Accounts Committee noted in its review of government services that legacy IT systems are a significant cost driver precisely because they require additional people and processes to work around their limitations. Because those expenses are included in operating budgets rather than technology budgets, the true amount is hidden from any one budget holder. This is also true for SMBs in the private sector.
Legacy systems remain in use because the visible costs are manageable, the hidden costs are distributed and invisible, and the perceived risk of a major change tends to feel larger than the perceived cost of maintaining the status quo. But that perception is often wrong and persists only until someone does the calculation.
When to Act: Three Financial Triggers
The following thresholds indicate that the cost of inaction has likely crossed the cost of change. Any one warrants a thorough review of the numbers, but all three in combination make a compelling case for action.
| Trigger | Threshold | What It Signals |
|---|---|---|
| Maintenance share of IT budget | Above 70% | No capacity left for development; system is consuming the IT function |
| Cost of next integration | Above £20,000 | Legacy system is driving commercial decisions, not business fit |
| Key-person replacement cost | Above £50,000 | Material financial exposure that belongs on the risk register |
Building the Business Case for Modernisation
A TCO analysis and a three-year projection provide the board with most of what it needs. Present visible and hidden costs separately, with clear methodology for each. The hidden cost calculation is often what changes the conversation because it shows a total that no one had seen before as a single number. The payback period becomes tangible when both trajectories are displayed with a break-even point.
A phased approach to legacy system modernisation tends to be more persuasive than an all-or-nothing proposal. Starting with the highest-cost, highest-risk components distributes the investment over time and limits operational disruption. The board should be asked not how much the program will cost, but rather what it will yield and how long it will take. This is the same question that should be asked of any other capital investment. Once the cost picture is clear, the next question is usually whether to rewrite or modernise.
The starting point for most businesses is an independent view of what the current system is actually costing, and that is what the Legacy Health Check provides. If the financial picture also depends on a bespoke database that has quietly become business-critical, our guide to Access database modernisation covers the realistic options. For exposure that goes beyond cost — outages, compliance, data loss — pair it with a structured legacy system risk assessment.
Key Takeaways
- Visible IT costs typically represent 30–40% of the true cost of a legacy system. The remaining 60–70% is distributed across operational budgets and headcount, with none of it attributed to the system responsible.
- The seven hidden cost categories to quantify: maintenance overhead, opportunity cost of slow delivery, integration tax, talent premium, compliance and security risk, staff productivity loss, and vendor lock-in premium.
- The cost of inaction compounds annually across multiple budget lines. It is rarely visible as a total until someone calculates it.
- Three financial triggers indicate the case for change: maintenance above 70% of the IT budget, integration costs above £20,000, and key-person dependency with a replacement cost above £50,000.
- The business case for modernisation rests on a TCO analysis and a three-year projection. The starting point is knowing what the current system is actually costing.