{"id":15224,"date":"2026-10-02T11:24:17","date_gmt":"2026-10-02T11:24:17","guid":{"rendered":"https:\/\/www.sparxitsolutions.com\/blog\/?p=15224"},"modified":"2026-10-01T09:56:35","modified_gmt":"2026-10-01T09:56:35","slug":"cost-of-maintaining-legacy-systems","status":"publish","type":"post","link":"https:\/\/www.sparxitsolutions.com\/blog\/cost-of-maintaining-legacy-systems\/","title":{"rendered":"Cost of Maintaining Legacy Systems in 2026"},"content":{"rendered":"

Legacy systems rarely become expensive overnight. Their costs often rise gradually through support fees, specialist labour, security controls and operational friction.<\/p>\n

Microsoft charges $61 per device for the first year of Extended Security Updates on Windows 10. The second year costs $122. The third costs $244. In Microsoft’s own words, “the price doubles every consecutive year, for a maximum of three years.”<\/p>\n

That is what the cost of maintaining legacy systems looks like when a vendor is willing to publish it: not a flat line, but a curve that steepens on a schedule. Many legacy costs can behave this way, particularly when vendor support and specialist resources become more expensive. Very little of it is documented as clearly.<\/p>\n

This guide separates what can actually be verified from what circulates as an estimate. It covers the prices vendors publish, the direct and hidden cost categories, why the number grows every year, a model you can run against your own estate, and the point at which continuing to pay stops being the cheaper option.<\/p>\n

<\/span>What Does it Cost to Maintain Legacy Systems?<\/span><\/h2>\n

That last point is worth being blunt about. Search this topic and you will find confident numbers: 60 to 80% of IT budgets go to legacy maintenance, a mid-size business spends $2 to $3 million a year, a single application costs $700,000 to $3 million. Trace them and most lead to another marketing page, an undated “industry data” attribution, or nothing at all. Any single figure quoted as the legacy system maintenance cost in 2026 should be treated cautiously, because legacy estates vary widely in complexity.<\/p>\n

Three categories of figures are actually verifiable: prices vendors publish for extended support, spending that public bodies disclose, and research with a named author and methodology. The rest of this guide is built on those, and says so where it is estimating.<\/p>\n

Public-sector disclosure gives the clearest view of the cost of legacy systems at scale. In GAO-25-107795<\/a>, published 17 July 2025, the US Government Accountability Office reported that federal agencies have typically spent about 80% of their IT budgets operating and maintaining what already exists, amounting to roughly $83 billion of planned IT spending in FY2025. The same report examined the 11 federal legacy systems most in need of modernization: they ranged from about 23 to 60 years old and cost approximately $754 million a year to run between them. Eight of the 11 had no complete modernization plan.<\/p>\n

That is one estate with unusual disclosure obligations, so it is not a benchmark for a private company. It is evidence that the 80% figure everyone quotes has a real source behind it, for at least one very large organization.<\/p>\n

<\/span>The Prices Vendors Actually Publish<\/span><\/h2>\n

The cleanest evidence of what legacy costs comes from the vendors charging for it. Two current examples set the pattern.<\/p>\n

Microsoft, Windows 10<\/strong>. Support ended on 14 October 2025. Organizations that need patched machines past that date buy Extended Security Updates, priced per device through volume licensing.<\/p>\n\n\n\n\n\n\n
ESU year<\/b><\/td>\nPrice per device<\/b><\/td>\nChange<\/b><\/td>\n<\/tr>\n
Year 1<\/span><\/td>\n$61<\/span><\/td>\nBaseline<\/span><\/td>\n<\/tr>\n
Year 2<\/span><\/td>\n$122<\/span><\/td>\nDoubles<\/span><\/td>\n<\/tr>\n
Year 3<\/span><\/td>\n$244<\/span><\/td>\nDoubles again<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Table: Microsoft’s published Windows 10 ESU pricing<\/a>, per device, via volume licensing. Total over three years is $427 per device, and the programme ends after year three.<\/p>\n

Two details matter beyond the headline. Devices must be running version 22H2 to be eligible, so the cost of staying may include an upgrade you were avoiding. And Windows 10 virtual machines running on Azure, Windows 365 and Azure Virtual Desktop receive ESU at no additional cost, which is a pricing structure designed to make staying put more expensive than moving.<\/p>\n

SAP, Business Suite 7<\/strong>. SAP’s published maintenance strategy<\/a> runs mainstream maintenance for Business Suite 7 core applications until the end of 2027. Extended maintenance is then available for three years, from the start of 2028 to the end of 2030, at “a premium of two percent points on the maintenance basis for all support offerings.” After 2030, remaining customers move to customer-specific maintenance.<\/p>\n

A two-point uplift sounds modest until you apply it to an eight-figure maintenance base and multiply by three years, and it arrives alongside every other cost in the sections below rather than instead of them.<\/p>\n

The pattern generalises. When vendors price extended support at a premium, the additional cost can strengthen the business case for migration.<\/p>\n

<\/span>Direct Costs of Maintaining Legacy Systems<\/span><\/h2>\n

These are the legacy system maintenance costs that appear somewhere in a budget line, even if not always under a heading that names them. They are the easiest to quantify and the least likely to be the largest.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Cost category<\/b><\/td>\nWhat drives it<\/b><\/td>\nWhere it sits<\/b><\/td>\n<\/tr>\n
Extended or premium vendor support<\/span><\/td>\nPer-device or percentage uplifts on retired versions, escalating annually<\/span><\/td>\nIT operations<\/span><\/td>\n<\/tr>\n
Hardware and hosting<\/span><\/td>\nAging servers, out-of-warranty equipment, specialist hardware with thin supply<\/span><\/td>\nInfrastructure<\/span><\/td>\n<\/tr>\n
Third-party licences<\/span><\/td>\nMiddleware, database and tooling versions pinned by the legacy application<\/span><\/td>\nSoftware licensing<\/span><\/td>\n<\/tr>\n
Specialist labour<\/span><\/td>\nPremium rates for COBOL, RPG, PL\/I, legacy middleware and retired framework skills<\/span><\/td>\nContractors and payroll<\/span><\/td>\n<\/tr>\n
Compensating security controls<\/span><\/td>\nSegmentation, virtual patching and dedicated monitoring for systems that cannot be patched<\/span><\/td>\nSecurity<\/span><\/td>\n<\/tr>\n
Interface upkeep<\/span><\/td>\nPoint-to-point integrations that break whenever anything upstream changes<\/span><\/td>\nIntegration and delivery<\/span><\/td>\n<\/tr>\n
Regression testing<\/span><\/td>\nLong manual test cycles because automated coverage was never built<\/span><\/td>\nDelivery capacity<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Table: Seven direct cost categories in legacy maintenance. Only the first three usually appear as an identifiable line item on a budget.<\/p>\n

The direct number most organizations can produce quickly is support and licensing spend. For some estates, it may also be smaller than labour, infrastructure, security and integration costs.<\/p>\n

Two of these lines behave differently from the rest. Specialist labour can become increasingly expensive as fewer engineers maintain expertise in retired platforms. And compensating security controls tend to accumulate, because each audit cycle more often adds a control than removes one, so the line can grow even in a year when nothing about the system changed.<\/p>\n

<\/span>Hidden Costs of Legacy Systems<\/span><\/h2>\n

The hidden costs of legacy systems are not hidden because anyone conceals them. They are hidden because they land in budgets that nobody connects back to the system causing them.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Hidden cost<\/b><\/td>\nHow it shows up<\/b><\/td>\nWhose budget absorbs it<\/b><\/td>\n<\/tr>\n
Manual workarounds<\/span><\/td>\nStaff re-keying between systems that cannot exchange data<\/span><\/td>\nOperations headcount<\/span><\/td>\n<\/tr>\n
Change friction<\/span><\/td>\nReleases take months because nobody trusts the blast radius<\/span><\/td>\nDelivery capacity, never itemised<\/span><\/td>\n<\/tr>\n
Blocked initiatives<\/span><\/td>\nAnalytics, AI and customer-facing projects stalled on data access<\/span><\/td>\nNo budget line at all<\/span><\/td>\n<\/tr>\n
Downtime and remediation<\/span><\/td>\nIncident response, recovery and customer impact after failures<\/span><\/td>\nOperational risk<\/span><\/td>\n<\/tr>\n
Recruitment drag<\/span><\/td>\nLonger hiring cycles and salary premiums for unfashionable skills<\/span><\/td>\nHR and recruitment<\/span><\/td>\n<\/tr>\n
Knowledge concentration<\/span><\/td>\nWork stops when one person is unavailable, and their retirement is a live risk<\/span><\/td>\nUnquantified until it happens<\/span><\/td>\n<\/tr>\n
Insurance and audit<\/span><\/td>\nHigher cyber premiums, more audit findings, more remediation commitments<\/span><\/td>\nRisk and compliance<\/span><\/td>\n<\/tr>\n
Opportunity cost of capital<\/span><\/td>\nMoney spent standing still is money not spent on anything that grows<\/span><\/td>\nNever measured<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Table: Eight hidden cost categories. Each lands in a budget other than the one paying for the legacy system, which is why the total is routinely understated.<\/p>\n

Research puts a scale on the aggregate. The Consortium for Information and Software Quality, in its Cost of Poor Software Quality in the US: A 2022 Report<\/a> authored by Herb Krasner, estimated the cost of poor software quality in the United States at at least $2.41 trillion, with accumulated technical debt at approximately $1.52 trillion, and named technical debt the largest barrier to modifying existing codebases. That report covers 2022 and has not been superseded with a comparable figure, so treat it as an order-of-magnitude anchor rather than a current-year number.<\/p>\n

<\/span>Why is the Cost of Maintaining Legacy Systems Rising Every Year?<\/span><\/h2>\n