The Hidden Costs of Maintaining Legacy Systems
When CFOs evaluate whether to replace an old system, they compare the known replacement cost against the apparent maintenance cost. The problem is the apparent maintenance cost understates the actual cost by a factor that can exceed three — because most legacy system costs are invisible in standard accounting.
The Hidden Costs of Maintaining Legacy Systems
When Nigerian companies evaluate their software portfolio, legacy systems almost always look like the economical choice to keep. The licensing fees are paid, sometimes years ago as a perpetual licence. The system runs. Staff know how to use it. Replacing it means a large capital outlay, disruption, training, and uncertainty.
That analysis is correct as far as it goes. It does not go far enough. The visible costs of maintaining a legacy system — licence fees, support contracts, server hardware, the occasional vendor patch — represent, in most cases, less than one-third of the total ongoing cost. The majority of legacy system cost is invisible in standard cost accounting, distributed across personnel time, opportunity cost, workaround infrastructure, and security risk that has not yet materialised as an incident.
This article provides a framework for calculating the real total cost of a legacy system, so the replacement decision is made with accurate numbers on both sides of the equation.
Visible Legacy System Costs
These are the costs that appear in IT budgets:
- Annual support and maintenance fees (typically 18–22% of original licence cost per year)
- Server infrastructure: hardware refresh, data centre costs, or cloud hosting
- Security patching and compliance work performed by internal or external IT staff
- Integration maintenance: sustaining data flows between the legacy system and other tools
For a Nigerian company running a ₦12M perpetual ERP licence with ₦2.5M annual support, ₦800K in server costs, and ₦600K in IT staff time maintaining it, the visible cost is approximately ₦3.9M per year. This is the number the CFO sees.
Invisible Legacy System Costs
1. Productivity Tax on Users
Legacy systems are typically slower and harder to use than modern alternatives. Industry analyses consistently suggest that users of legacy systems lose an average of 20–30 minutes per day to slower interfaces, more complex navigation, and manual workarounds.
For a Nigerian company with 80 users of a legacy ERP, at an average cost of ₦280,000 per user per month (including salary, benefits, and overhead), 20 minutes per day represents:
- 20 minutes × 22 working days = 7.3 hours per month per user
- 7.3 hours ÷ 176 monthly working hours × ₦280,000 = ₦11,600 per month per user
- 80 users × ₦11,600 = ₦928,000 per month / ₦11.1M per year
This productivity tax rarely appears in any budget line. Its existence is verifiable by time-and-motion observation but rarely measured.
2. Workaround Infrastructure
Legacy systems frequently cannot do everything the business needs them to do. The response is a proliferation of workarounds: Excel spreadsheets that bridge the gaps, Access databases that extend the system's data model, and shadow systems built in newer tools that partially replicate the legacy system's data.
Each workaround has maintenance cost: the person who owns the spreadsheet spends time keeping it current; when that person leaves, institutional knowledge is lost; integration between the workaround and the core system creates reconciliation work and error risk.
Common in Nigerian businesses: a finance team that exports data from their accounting system into Excel monthly, performs consolidation and reporting in Excel, then manually re-enters results into the system. The double-entry risk (errors in re-entry not caught until period close) and the staff time for the process are both legacy system costs. They appear in the accounting as normal finance department expenditure.
3. Integration Costs
Modern business software communicates via APIs. Legacy systems frequently do not. Connecting a legacy system to a new tool — a payment gateway, a CRM, an e-commerce platform — requires custom integration work, often at the level of database access or file export/import, that modern systems would handle through standard connectors.
Each integration built to accommodate a legacy system's limitations is an ongoing maintenance cost (the integration must be maintained when either the legacy system or the connected tool changes) and a fragility cost (integrations built against legacy system internals are brittle — vendor upgrades frequently break them).
4. Talent Cost and Recruitment Difficulty
Technical staff who work with legacy systems are a shrinking population. A Nigerian company running a 15-year-old system built on discontinued technology faces increasing difficulty finding developers and administrators who know the platform.
The effects: higher per-hour rates for the specialists who can maintain it; higher staff turnover as younger IT staff prefer working with modern technologies; project risk from key-person dependency (one staff member who knows how the system works at a level no one else does).
5. Security Exposure
Legacy systems that are no longer actively developed receive limited or no security updates. Each year without patching increases the number of unmitigated vulnerabilities.
For Nigerian businesses with regulatory exposure — financial services firms under CBN oversight, healthcare operators, companies processing cardholder data — running an unpatched legacy system creates compliance risk that may not have materialised as a fine but represents a probability-weighted cost. A data breach facilitated by a legacy system vulnerability, at Nigerian regulatory penalty rates of ₦10M–₦2B plus remediation costs, is a real liability.
6. Opportunity Cost
This is the hardest cost to quantify and the most significant. Legacy systems constrain what the business can do digitally. A company that cannot deliver a usable customer portal because its backend system has no APIs cannot compete with competitors who can. A company that cannot analyse customer behaviour at a granular level because its data is locked in a legacy schema cannot personalise its service offering.
Opportunity cost does not appear in any budget line. It appears in competitive position — in market share slowly ceded to competitors with better digital infrastructure — and is typically invisible until a threshold effect triggers a visible revenue decline.
Building the Full Cost Picture
A structured total cost of ownership (TCO) framework for an existing legacy system should include, at minimum:
| Category | Estimation Method |
|---|---|
| Direct IT costs | Budget data, vendor invoices |
| User productivity loss | Time-and-motion × user count × cost per hour |
| Workaround infrastructure | IT staff time + data error incident costs |
| Integration maintenance | Developer hours × hourly cost |
| Talent premium and turnover | Recruitment cost + salary premium vs. market |
| Security risk | Probability × estimated breach cost |
| Opportunity cost | Estimated revenue impact or competitive disadvantage |
When Nigerian companies conduct this analysis rigorously, the result consistently shows legacy system total cost at 2.5–4× the visible cost. The ₦3.9M visible annual cost in the earlier example, under a full TCO analysis, typically resolves to ₦9M–₦15M.
The Replacement Economics
With full TCO established on the legacy side, replacement economics change significantly. A replacement project with a one-time cost of ₦18M and an ongoing annual cost of ₦4M — which appeared expensive against a perceived ₦3.9M annual cost — looks different against a real annual cost of ₦12M.
At ₦12M per year legacy cost and ₦4M per year replacement system cost, the ₦8M per year savings pays back the ₦18M development cost in 2.25 years. That is a viable investment decision.
The framework also helps prioritise which legacy systems to address first. Not all legacy systems have equal TCO. The company's primary transaction system with 200 users has a much higher productivity cost than a legacy reporting tool used by five finance staff. Prioritising replacement effort toward highest-TCO systems maximises return on modernisation investment.
Migrating Without Disruption
The legitimate concern in legacy system replacement is business disruption. The risk is real, and it should be part of the project design — not a reason to delay indefinitely.
An incremental modernisation approach: run the legacy system and its replacement in parallel during a transition period, migrating users and data progressively rather than in a single cutover. This increases project cost by 20–30% but reduces business risk substantially.
For Nigerian companies with complex operational dependencies on legacy systems, a phased decommission plan — identifying which functions to migrate in which order, with defined rollback conditions — provides a structured path to modernisation without the risk of a big-bang cutover.
The Decision Framework
The decision to replace a legacy system should rest on a TCO comparison across a 5-year planning horizon:
- Year 0: Legacy TCO × 5 vs. (Replacement project cost + replacement annual TCO × 5)
- Adjust for net present value of future costs
- Include a risk-weighted estimate of legacy system security or compliance incident cost
- Include strategic value of capabilities the replacement system enables
Most Nigerian businesses that conduct this analysis with accurate legacy TCO data find modernisation is the more economical choice within a 3–5 year horizon. The analysis is rarely done because it requires acknowledging costs that are not in anyone's budget line — which is precisely why this document is recommended reading for every CFO who has been told that keeping the old system is the conservative choice.
The conservative choice is the one based on accurate numbers. Usually, that means replacing.
Related Articles
- Custom Software vs SaaS: An Honest Comparison — When to build vs when to buy
- Technical Debt: Measuring, Managing, and Selling It to the CFO — Quantifying the cost of code quality neglect
- Measuring Software ROI — Framework for calculating return on technology investment