Replacing a legacy system: step by step instead of an oil tanker project.
You're best off not replacing a legacy system in a two-year project, but piece by piece: first what annoys most in daily work, then the next part. Specialised tools with open APIs take over single tasks, the old system shrinks. Sometimes two days are enough for that.
What is a legacy system?
A legacy system is an old system that still runs but can barely be changed: outdated technology, missing interfaces, knowledge in a few heads.
The problem is rarely the age alone. It gets expensive when the system needs workarounds for workarounds and every small change becomes a project. Then it costs time and nerves every day that are missing elsewhere.
"Never change a running system" sounds pragmatic. Often it's just postponed.
The system in question doesn't run anymore. It limps. The interface looks like Windows 95, and some people have built up knowledge over the years that's written down nowhere.
When sales or customer service does extra work every day because the system is a pain, and the fix keeps getting pushed back, at some point the best people leave. Rightly so.
Three situations when the legacy system becomes permanent.
We know these situations from many companies.
The ticket nobody works on
Sales needs a small change to the quote generator. IT's answer: not right now, we're in the middle of the big rollout. So sales builds quotes with workarounds for another year. Frustration grows, and the best people start looking around.
The knowledge written down nowhere
One long-serving employee is the only one who knows how certain things work in the system. No manual, no documentation. When he leaves, the knowledge leaves too, and the company depends on a system nobody understands anymore.
The mega project that freezes everything
The standard answer: rip everything out, new system, runtime of several years. While IT works on it, there's no time left for everyday changes. And when the new system goes live, it's sometimes already yesterday's news.
Oil tanker or best of breed?
| The oil tanker project | Best of breed, step by step |
|---|---|
| Replace everything at once | Solve the most annoying thing first |
| IT is blocked for years | Teams introduce their own tools |
| One vendor for everything | The best tool per task, connected via API |
| If the vendor fails, everything shakes | If a tool fails, it gets swapped |
| Benefit only after cut-over | Benefit from the first step |
Oil tanker or nothing. Why that's wrong.
For a long time the IT world had one answer to legacy systems: rip everything out, big platform project, new ERP. Holistic, future-proof, integrated. That sounds good, but it freezes all IT capacity for years. Every request from daily business gets the same answer: no capacity.
Then there's the fear of isolated solutions. It used to be justified. Today almost every modern tool has open APIs and can be connected via Make, Zapier or n8n, or with a small Python script. How we build such connections is covered under API development.
For the website, the old CMS is often exactly such a legacy system. What the alternative can do is in our overview of headless CMS.
No mega project. A problem solved that has waited for years.
A sales team works with an old CRM that can't do what it needs. IT says: we'll replace it completely, next year at the earliest. The team has heard that before.
Typically we first look at what concretely annoys people. Often there's a single manual process behind it that can be solved with an API connection to a specialised tool. No new ERP, no year-long project. As IT problem solvers we always start with what annoys most.
- Problem analysed in a few days
- API connection to a specialised tool
- Daily manual process eliminated
- IT capacity stays free
- The team develops the tool further itself
- Next issue found, also without a mega project
Sometimes we lock ourselves in with IT for two days. Afterwards, what was planned for two years from now is done.
What you usually ask us about legacy systems.
Usually not right away. We first look at what concretely annoys people and whether it can be solved without touching the foundation. Often a targeted addition or interface is enough to remove the biggest pain. The old system can then shrink step by step instead of being replaced completely on one cut-over date.
It used to be. Today almost every modern tool has an open API. Connections can be built via Make, Zapier or n8n, or with a small script. What matters are clear rules about which system owns which data. Then integration is no black magic, and a weak tool can be swapped out on its own.
Then we look at what can be solved in parallel without straining IT capacity. Many teams can introduce and adapt specialised tools themselves, we help with setup and integration. IT stays informed and has a say on security and data, but doesn't have to build everything itself.
We get an honest assessment with concrete recommendations done in two to three days. No long-term consulting, no slide deck. Just the answer to two questions: where does it hurt most, and what's the fastest first step? Then you decide whether we take that step together.
Stuck in a big project? Let's talk.
Briefly describe where it hurts most. We'll tell you in a conversation what's realistic and quickly solvable.