When should you replace your software?
There is rarely a single moment when outdated business software becomes unusable. Usually, small signals pile up until maintenance costs more than it delivers. Seven concrete signals to watch for, and what they say about how urgent replacement is.
7 signs that replacement is closer than you think
None of these signals is a reason to replace immediately on its own. Together, however, they form a pattern: the more of them you recognise, the greater the chance that further maintenance is a temporary fix for a problem that is becoming structural.
Many organisations work with a fixed replacement schedule, for example "we evaluate the core system every seven years". That works well for budget planning, but says little about the actual state of a system. A fifteen-year-old application that runs stably, is well documented and whose knowledge is widely shared can be healthier than a five-year-old application that already shows three of the seven signals below. The signals say more about urgency than the age of the system does.
A simple integration turns into a separate project
New requirements almost always call for an API these days: an accounting package that wants to receive invoices automatically, a customer who requests real-time stock data, a regulator that requires digital submission. If your system can only deliver a file through a nightly batch export, every new integration suddenly becomes a manual custom project instead of a configuration job that takes a few days. This often only becomes visible when a customer or partner makes the integration a condition, and the delay has immediate commercial consequences.
Knowledge of the system fits in one person's head
Systems built in languages such as Cobol, Delphi or RPG (the language behind an AS/400) have not been taught as a core subject for decades. For Cobol this pattern is widely documented: the average age of active Cobol programmers is around 60, while the number of open vacancies for these languages keeps growing. The person maintaining your system today is often the same person who helped build it years ago.
Patches and security updates stop or have to be purchased separately
The operating systems and databases that many legacy applications run on eventually reach the end of their support cycle. Windows Server 2012 and 2012 R2, for example, reached the end of regular support in October 2023; the last paid security updates (Extended Security Updates) expire for good in October 2026. If your application runs on a platform in that phase, known vulnerabilities will remain permanently open after that date.
Shadow processes emerge alongside the official system
Employees build their own Excel files, Access databases or shared spreadsheets to do what the system no longer supports smoothly. Data ends up scattered across several unconnected sources, and reports have to be compiled manually before a manager can do anything with them. Often only the author of such a spreadsheet knows exactly which assumptions are built into it, which makes it particularly fragile as soon as that person goes on holiday or changes jobs.
Performance stalls as volume grows
Nightly batch processing that creeps ever closer to the start of the next working day, or a report running on a single database server with no way to scale horizontally. Growth in transactions, customers or employees exposes a design that was once built for a smaller scale. The first reaction is often a bigger server or more memory, which eases the problem temporarily without addressing the underlying architectural choice.
Maintenance structurally costs more than replacement would
Hourly rates for scarce legacy specialists are often higher than standard development rates, precisely because the scarcity described in signal two drives up the price. On top of that, every change takes disproportionately long, because nobody has a complete overview of the whole system any more and every change first has to be investigated before anything is altered. What looks like a small change on paper turns into days of archaeology in the existing code.
Users actively avoid the system
Employees only log in when they have no other option, deliberately look for workarounds, or ask a colleague to enter something "in the real system" for them. That is a stronger signal than a technical error message, because it means the people who work with it every day have already written the system off.
Recognise several signals? Here are the next steps
If you recognise three or more of these signals, a no-obligation conversation about your options is more useful than yet another emergency fix. Depending on the system you are replacing, the process can look very different.
Is it running on Delphi?
Delphi applications often contain solid business logic that is worth keeping, just not in its original form.
Modernising a Delphi application →Is it running on a Cobol mainframe?
With Cobol systems, the risk usually lies not in the code itself, but in the shrinking pool of people who can still read it.
Replacing a Cobol system →Is it running on an AS/400?
An AS/400 often keeps running stably for years, until the surrounding knowledge disappears and every change means downtime.
Replacing an AS/400 with a modern platform →Is it running on WinCC?
With industrial control systems (SCADA/HMI), the question of how to connect securely to modern cloud and IoT integrations often comes into play as well.
Replacing WinCC →Recognise the signals, but your system runs on a different platform from those above? We also guide the process of building custom software, from initial analysis to go-live.
Want to understand first why these kinds of risks arise? Read our background page on technical debt and legacy software.
A first, no-obligation step is usually a technical intake: which parts of the current system are still healthy, which contain useful business logic worth carrying over, and which are simply outdated. That intake determines whether a full replacement is needed, or whether a phased approach with a modern interface layer around the existing system is enough.
Frequently asked questions
Go through the seven signals and count how many you recognise. With one or two signals, targeted maintenance is often still the sensible choice. With three or more, especially combined with rising maintenance costs, a replacement project deserves serious consideration.
In practice, a step-by-step approach is more often the sensible choice than a full big-bang replacement. Decoupling critical components first behind a modern interface, and then replacing the rest of the system in phases, limits risk and keeps your organisation running throughout.
Data analysis and migration are usually a separate workstream: first mapping out which data is usable and which is historical clutter that has been dragged along for years, and only then migrating. That way you don't automatically carry the old system's data quality problems over to the new one.
Sometimes, yes. A system that runs stably, needs no integrations and whose knowledge is held by more than one person can last for years. Postponing becomes risky once several signs appear at the same time, because costs and risks then tend to rise not in a straight line but at an accelerating rate.
A single sign is usually no reason for a full replacement project, but it is a reason to keep monitoring it. Signs two (knowledge) and three (support ending) deserve extra attention, because they rarely improve on their own.
Yes, and for larger systems it is often the wisest route. A stable core component can keep running for a while behind a new interface layer, while the components showing the most warning signs are replaced first.
With the process. A replacement that merely puts the old screens in a new coat of paint often carries the bottlenecks of the old process over without anyone noticing. Mapping out how the work actually runs today, including the shadow processes from sign four, prevents that.
Not sure whether your system needs replacing?
Briefly describe which signs you recognise and what your current system looks like. We'll think along with you, without obligation, about what a realistic first step would be.
Do you already know what should take its place? On applatenmaken.com we explain which custom software we build per sector and process.