Legacy software modernisation
Legacy software modernisation, when I do it, starts with whether the old system should be modernised at all. Sometimes the right answer is keeping it running safely for as long as you need it, and when it isn’t, I move you off it in stages without taking the business down. Either way it’s the system that does something important and that one or two people half understand.
What this is
This is senior, careful work on systems that matter and are old enough to be dangerous. Sometimes the job is keeping a critical legacy system stable and maintainable for as long as you genuinely need it — taming it enough that it stops being a liability hanging over you. Sometimes it’s planning and steering the move off it onto something current, without the migration becoming its own disaster. Often it’s telling you honestly which of those is the right call, because that decision is where most of the money is won or lost.
The thing that makes legacy work hard isn’t the age of the code — it’s that the system is load-bearing and poorly understood at the same time. The people who built it have moved on. The documentation is folklore. Nobody’s certain what’ll break if you change the wrong line, so nobody changes anything, and the risk compounds. Walking into that and forming a clear, honest picture of what the system actually does and how to handle it safely is the core of the work.
It is not a thrilling rebuild dressed up as progress. The instinct with old systems is “rip it out and start fresh,” and sometimes that’s right — but it’s also the most expensive answer and frequently the wrong one. A working system you understand is worth more than a clean one you’re still building. My bias is toward the least dramatic move that gets you out of danger, not the rewrite that feels good to propose.
When you need this
You need this when something old and important has become a quiet, growing risk you can’t keep ignoring. The familiar cases:
- A critical system is running on technology that’s ageing out — unsupported, unpatched, or held together by someone who’s leaving.
- You’re afraid to change it because nobody fully understands it, so it’s frozen while the business around it moves on.
- You need to migrate off it — to integrate, to scale, to stay compliant — and you’re rightly worried about breaking what works during the move.
- One or two people are the only ones who know how it runs, and that key-person risk is keeping you up at night.
The thread is dependence on something fragile and irreplaceable. The danger with legacy systems isn’t that they’re old — it’s that they fail at the worst time, when the one person who understood them is gone. Getting ahead of that is the whole point.
How working with me goes
I start by understanding what the system actually does before touching anything, because the fastest way to cause a legacy disaster is to change something whose purpose you only half-grasped. So the first work is genuine comprehension — what it does, what depends on it, where the live wires are — turning folklore back into something knowable.
Then I give you the honest strategic call: stabilise and maintain, or migrate off — and if migrate, how, in what order, and with what fallback when a step goes wrong. Legacy migrations fail when they go big-bang; they succeed when they go in safe, reversible steps with the old system carrying the load until the new piece has earned its place. I work that way, and I get the knowledge out of one person’s head and into something durable as we go, so you’re not back in the same trap in three years. The aim throughout is the least risk to a running business, not the most elegant outcome.
What you walk away with
- A clear, honest picture of what the system does and where its real risks are — folklore turned into knowledge.
- The strategic call made plainly: stabilise and keep it, or move off it — with the reasoning.
- If you’re staying: a system tamed enough to maintain safely, no longer a liability hanging over you.
- If you’re moving: a safe, staged migration plan with fallbacks, not a big-bang gamble.
- Key-person risk reduced — what lived in one head, captured where the business can rely on it.
Who this isn’t for
If you want someone to greenlight ripping the whole thing out and rebuilding it fresh because that’s more exciting, I’m probably not your person — I’ll often tell you the cheaper, safer answer is to keep and tame what works. This is for people who care more about not breaking the business than about a clean rewrite.
When you need a team instead
Rescue gives you the picture, the call, and a safe path. If that path is a substantial migration or a full rebuild onto modern foundations, executing it is sustained delivery — a team’s job, not one person’s. That’s my agency, Digital Royalty: taking the strategy and doing the migration or rebuild at scale, with the team and process to move a business off a critical system without dropping it. I can hand the plan across so the heavy lifting starts from a clear, de-risked map.
Talk to me
If you’ve got an old system that’s become a quiet risk and you can’t tell whether to keep it or leave it, that’s exactly what this is for. Tell me about the system and I’ll tell you straight what I’d do. If the trouble is a current build that’s stalled rather than an old one that’s fragile, that’s project rescue; if you need to know how sound the underlying structure is before deciding, an architecture review is the right first step; and the other ways I help cover where this isn’t the right fit. The broader strategy work behind this lives in system architecture.