Software modernisation without a big bang
Your legacy system carries day-to-day operations, but every change gets more expensive and the knowledge sits in a few heads. We modernise step by step: the old system keeps running until the new one takes over piece by piece. For companies with 50+ employees in Austria and Germany.
Signs that your legacy system is becoming a risk
- Small changes take weeks because nobody can safely judge the consequences.
- Only one or two people really know the system.
- The vendor no longer ships updates, or the technology only runs on old hardware.
- Excel lists grow next to the system because it cannot handle new requirements.
- Integrations with ERP, web shop or partners are missing or run on manual file exports.
Modernise, replace or keep running?
Not every legacy system needs replacing. We answer that question first, using your real process.
Keep running
if the system is stable, rarely changes and is well documented. A clean interface to the outside is often enough.
Replace with standard software
if good standard software covers your process almost completely. Building your own would then be too expensive.
Modernise step by step
if the process is your edge but the legacy system holds you back. Then we replace it piece by piece without stopping operations.
How we modernise: layer by layer
Analysis on the real system
We look at code, data and processes and decide which parts to replace first. Result: a plan in stages and a fixed price per stage.
Put an interface in front
An interface goes in front of the legacy system. New applications talk to it instead of directly to the old system.
Carve out processes
One process after another moves into the new software, starting with the one that causes the most trouble.
Run in parallel
Old and new run side by side for a while. We only switch over once the new system demonstrably carries the load.
Switch off the legacy system
In the end nothing is left that the legacy system would have to do. Then it is switched off, planned and without cut-over risk.
Migrating data without stopping operations
Old data is rarely clean: duplicate customers, free-text fields, special cases from many years. We clean and migrate it in stages, check every migration with automated tests and keep the legacy system readable until nobody needs to look anything up any more.
A bought-in third-party system replaced
At a window manufacturer with several sites, the new field service planning replaced a bought-in third-party system. The shared software has been in daily use since 2022, is synchronised every night with the ERP of 11 sites and is secured by around 6,000 automated tests.
See the field service planning in the showcaseWhat a modernisation costs
It starts with the analysis: one to two weeks, €3,000 to €6,000 net, fully credited. After that you get a fixed price per stage. How large the stages are depends mainly on the number of processes, the integrations and the data migration.
See price ranges and a worked exampleModernising with AI: what gets faster and what stays manual
AI helps exactly where modernisation used to take the most time: reading and explaining old code, adding missing tests, converting data formats. We use Claude Code for this.
What stays with people: deciding what gets replaced, clarifying the business logic with you and reviewing every change. No change goes live without automated tests, code review and sign-off by a person.
Frequently asked questions
Do we have to switch off the legacy system in one go?
No. We modernise in stages. The legacy system keeps running until the new software demonstrably takes over a process. It is only switched off once nothing is left that it would have to do.
What does a modernisation cost, and how long does it take?
The analysis takes one to two weeks and costs €3,000 to €6,000 net; it is fully credited. After that you receive a fixed price per stage. A first stage is often in use after a few weeks; the overall duration depends on the size of the legacy system.
What happens to our data and processes during the switch?
Your processes keep running. We migrate data in stages, check every migration with automated tests and run old and new in parallel until the new software carries the load.
Who owns the source code afterwards?
You do. You receive the complete source code including documentation in your own repository. The software runs on your premises or in a data centre in Austria.
Let's talk about your legacy system.
In the intro call we clarify whether a modernisation pays off and where you should start. Free and without obligation.