What does legacy software really cost your organization?

Legacy software costs organizations more than they think. According to widely cited industry estimates, organizations spend 60 to 80 percent of their IT budget on maintaining existing systems, a large part of which is legacy software.

That means less than a quarter of the budget remains for innovation, new functionality, or growth. And that ratio worsens every year.

In this article, we explain exactly where the costs of legacy software lie—both visible and hidden—and when the balance tips.


How much of your IT budget is spent on legacy software?

Anyone spending 60 to 80 percent of a 10 million euro IT budget on maintenance is left with less than 2 million for innovation and new development.

That money goes toward patching, licenses, infrastructure, and specialized support for systems that are no longer actively developed. These are recurring annual costs, without the system actually improving.

Moreover, the ratio deteriorates every year. Maintenance costs for legacy software increase by an average of 10 to 15 percent per year after the warranty period expires. To illustrate: a system that currently costs 2 million euros per year to maintain will, at that rate, cost around 3.5 million in five years—for the exact same functionality.


Why do the costs of legacy software increase every year?

Three factors drive costs up further each year, in addition to regular maintenance increases.

First, knowledge disappears. Developers who know the system leave. Replacements take longer to onboard and make mistakes more often. Specialists for outdated technology become scarcer and more expensive.

Second, security issues accumulate. Systems that no longer receive updates develop vulnerabilities that must be patched manually. That costs time and budget, year after year.

Third, technical debt grows. Every temporary workaround built to keep the old system running makes the system more complex. And more complex systems are more expensive to maintain.

At a certain point, these rising costs outweigh the investment in modernization.

To learn how to tackle legacy step by step, read our page on legacy and modernization.


How much of your developers' time does legacy software cost?

On average, a developer spends a third of their working time on technical debt and legacy code. This is shown by the Developer Coefficient study by Stripe among more than 1,000 developers across five countries.

For a team of ten developers, that means: three full-time developers are permanently busy with old work. Time that could otherwise be spent on new functionality, improvement, and innovation. So it not only costs increasingly more money, but also a great deal of time.

This translates directly into delays. Releases take longer. New features take more time. And the developers who are most experienced with the old system are the least available for what the organization actually needs.

The problem also scales with the team. Hiring more developers doesn't solve it as long as the system continues to make the same demands. A third of every new developer's time is still consumed by legacy.


What does legacy software cost you in terms of employees?

Employees who work daily with slow, outdated systems become frustrated. This has direct consequences. According to British research, 48 percent of employees waste three hours or more per day due to inefficient systems.

A common problem with legacy software is knowledge concentration. The knowledge of how the system works resides with only one or two people. If they leave, that knowledge disappears with them. New employees cannot work independently with the system and remain dependent on those who still know it.

This makes the organization vulnerable. And it makes the system increasingly difficult to replace, because no one knows exactly what it all does anymore.

The costs of turnover are also direct. Replacing an experienced employee costs an average of six to nine months' salary, including recruitment, onboarding, and lost productivity.

Legacy software also pulls talent away from interesting work. Developers who spend their time maintaining old systems do not learn new skills. That makes it harder to retain them and to attract new talent.


What are the compliance and security risks of legacy software?

Legacy software no longer receives security updates. Vulnerabilities accumulate and go unpatched. This makes the system an attractive target for attackers.

The consequences can be severe. In 2018, Marriott International was hit by a data breach through an acquired legacy system. Initially reported as affecting 500 million guests, the figure was later adjusted to approximately 383 million guest records. The UK regulator imposed a fine of 18.4 million pounds.

Systems that do not comply with GDPR, NIS2, or other regulations carry direct financial risks. In 2023, European regulators collectively issued over 2 billion euros in GDPR fines.

Legacy software also makes compliance operationally more difficult. Audits take longer because data is scattered across systems that do not communicate with each other. Reports have to be compiled manually. And proving that you meet requirements becomes increasingly complex as regulations tighten.


Curious about what legacy costs your organization? 

Want to know where your organization stands? With the legacy scan, you can quickly identify which systems are at risk and where costs are mounting.

Would you like to discuss the results or brainstorm directly about modernization? Contact Maarten. He’ll be happy to think along with you.

Anything to amaze you.

Frequently asked questions about legacy

What exactly is legacy software?

Legacy software is outdated software that is still in use, but no longer actively developed. Critical business operations often depend on it, while maintenance becomes increasingly expensive and risky.

When is it cheaper to replace legacy systems than to maintain them?

The tipping point is reached when annual maintenance costs and risks become structurally higher than the investment in renewal. A scan of your systems provides clear and actionable insight into that point.

Is legacy software always a problem?

No. A stable system that does its job and requires little maintenance doesn't need to be replaced. It only becomes a problem when the costs, risks, or dependency on a few individuals become too great.

How do I know which systems are at risk?

With a legacy scan, you map out which systems are outdated, identify security and compliance risks, and pinpoint where costs are rising. This lets you know where modernization delivers the greatest value.

B. Amsterdam (B.2)

John M. Keynesplein 12-46

1066 EP Amsterdam

Follow us on LinkedIn for updates

© 2022 - 2026 Koodin | Koodin is an SNA-certified company

|

|

B. Amsterdam (B.2)

John M. Keynesplein 12-46

1066 EP Amsterdam

Follow us on LinkedIn for updates

© 2022 - 2026 Koodin | Koodin is an SNA-certified company

|

|

B. Amsterdam (B.2)

John M. Keynesplein 12-46

1066 EP Amsterdam

Follow us on LinkedIn for updates

© 2022 - 2026 Koodin | Koodin is an SNA-certified company

|

|