IT Glossary
What is legacy software?
Inherited software: old systems rooted deep in the company, too important to switch off and too fragile to ignore.
Most established companies have one program everybody discusses with a mixture of gratitude and dread. It has run for fifteen years, it holds inventory or production together, it was written by somebody who no longer answers the phone, and nobody dares touch it. That is legacy software: technology past its support window, code nobody understands any more, integration that is effectively impossible (no API, in a world that lives on APIs) and, frequently, dependence on one particular person or one particular machine that must never be switched off. The paradox defining the category is that legacy systems are usually the most important ones in the business — which is exactly why they survived — while their risk is silent and compounding: every year adds unpatched vulnerabilities, fresh incompatibilities (the new printer, the new operating system, the new e-invoicing mandate) and a higher eventual cost of exit. The good news, against the panic instinct, is that modernisation almost never means throwing everything away and rewriting. The mature route is incremental: reduce immediate risk first with verified backups, written documentation of what the system actually does and a virtualized copy of the fragile environment; then strangle it gradually, migrating functions one by one to new systems with data bridges in between, until the dinosaur stands empty and is powered down without drama. The trigger is not a calendar date but a question — if this system dies on Friday, what happens on Monday?
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
The existential risk defused
Documentation, verified backups and a migration plan turn “if it dies, we die” into a manageable project with owners and deadlines.
The door to integrations reopens
Bridges built onto the old system — intermediate APIs, structured exports — reconnect the company to e-invoicing, e-commerce and automation.
Modernisation without stopping the factory
Gradual strangulation, function by function, avoids the risky big bang; operations never pause for a single working day.
Frequently asked questions
How do I decide between maintaining, modernising and replacing an old system?
Three arbitration questions. How much risk am I carrying — vanished support, one irreplaceable person, no verified backup all mean urgency. What does it cost annually, counting maintenance, manual work caused by missing integrations and opportunities blocked. And does an off-the-shelf replacement exist: if a modern ERP covers most of what the dinosaur does, migration beats modernisation, whereas a system that is your unique advantage deserves the investment.
We no longer have the source code of the old application — what options are left?
More than it appears. Running it inside a controlled virtualized environment buys time and removes the dependency on one relic machine. Rebuilding behaviour by observation lets a new system replicate what the old one does, verified by running both in parallel. Data-level bridges can read the database directly where that is accessible. Missing source code makes the road more expensive without closing it.
How long does a typical modernisation take, and what does it cost?
Honestly: from a few months for an isolated application moved onto current technology, to one or two years in phases for a central system with many tentacles, with budgets starting in the tens of thousands of euros. Those figures frighten people until they sit beside the alternative — the annual cost of the status quo plus the risk of a total stop — and until phasing starts delivering value in the first months rather than at the end.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247