You probably already know the answer. The system is slow, the vendor support is ending, integrating anything new with it requires a workaround, and your team has developed an entire shadow infrastructure of spreadsheets and manual processes to compensate for what it can't do.
The question isn't really "is it time?" — it's "how do I make the case, and how do I do this without it becoming a two-year disaster?"
The signs that are easy to rationalise away
"It still works"
This is the most dangerous one. Legacy systems don't usually fail dramatically — they fail slowly, in ways that become normal. The nightly batch job that occasionally needs a manual restart. The report that takes an hour to run. The new hire who needs three weeks to understand how to use it. None of these feel like crises. Together, they represent a significant drag on productivity and agility that's almost impossible to quantify because it's baked into how everyone works.
"We know its quirks"
Institutional knowledge about how to work around a system's limitations is often treated as an asset. It isn't. It's a risk. The people who hold that knowledge leave. The workarounds multiply. And every workaround is a process your organisation is running in parallel with the system it's supposed to replace.
At a legal services firm, we found over forty documented workarounds for a case management system that had been in place for twelve years. Several of them were known only to individuals who had since left the business. The system "worked" — but the true operational cost of running it was invisible in the technology budget.
"The replacement will cost more"
This is often true in year one. It's almost never true over five years, once you account for maintenance costs, licence fees for a system the vendor is winding down, developer time spent on integrations, and the opportunity cost of everything you can't do because the system can't support it.
"We can't afford the disruption"
The disruption of a planned migration is finite and manageable. The disruption of an unplanned failure, a security incident, or a vendor end-of-life forced migration is not.
The real blocker: making the case
The technical case for replacing a legacy system is usually obvious to the people who work with it. The financial case — the one that moves budget — is harder to construct.
A credible business case usually includes:
Total cost of ownership, honestly calculated. Not just the licence fee, but: internal resource time spent on maintenance and workarounds, third-party integration costs, any specialist support for ageing technology, and the cost of manual processes that exist because the system can't automate them.
Opportunity cost. What can't you do right now because this system is in the way? New business processes, AI initiatives, customer experience improvements — what's on the roadmap that's blocked?
Risk quantification. What happens if the vendor ends support? What's the exposure if the system fails? What's the security posture of a system that may not be receiving regular patches?
A realistic migration estimate. The case gets more credible when the proposed alternative is properly scoped — not just "modern cloud platform" but a specific architecture, realistic timeline, and phased approach that de-risks the transition.
The AI connection most people miss
There's a reason legacy systems are increasingly urgent to address, beyond the usual arguments. AI and data capabilities — the things that will define competitive advantage over the next decade — almost universally require modern, accessible, well-structured data.
Legacy systems trap data in formats and architectures that AI tools can't easily use. This is the less-visible cost: it's not just that the system is slow or expensive to maintain. It's that every month it remains in place is another month your AI ambitions are blocked at the data layer.
Here's the shift worth understanding. For most organisations, genuine AI capability used to be out of reach — not because the technology didn't exist, but because building it required modern infrastructure, clean data, and skilled teams that only large enterprises could afford. Legacy systems were one of the structural barriers that kept that advantage with the big players.
Modern cloud architecture, combined with cloud co-funding programmes that cover significant portions of migration costs, has fundamentally changed that equation. A well-executed migration to a modern, AI-ready architecture opens up capabilities — predictive analytics, intelligent automation, real-time data — that weren't economically accessible before. The migration cost that used to be a multi-year commitment can now be phased, funded in part by cloud partners, and delivered in a fraction of the time.
The organisations moving now aren't just fixing an IT problem. They're removing the last structural barrier between where they are and the AI capability that will define competitive advantage in their sector.
How to approach the migration itself
Phase it. A big-bang replacement of a critical system is high risk. Most successful migrations move workloads incrementally, running old and new systems in parallel, validating data integrity at each stage before cutting over.
Start with the data. Before migrating functionality, understand the data. What's there, how clean is it, what needs remediation? Data quality problems discovered mid-migration are the most common cause of delays and cost overruns.
Define what success looks like before you start. A migration that goes "smoothly" is one where the definition of done was agreed upfront — data integrity validation, performance benchmarks, user acceptance criteria. Without these, the project never ends.
Plan for knowledge transfer. If you're bringing in external help, the engagement should end with your team understanding the new system deeply enough to own and extend it. A migration that leaves you dependent on an external party is a different kind of legacy problem.
When it's not time yet
Sometimes the honest answer is that the timing isn't right. If the business is in a period of significant operational change, if there's no budget certainty for the next 12 months, or if the people needed to make a migration succeed are already at capacity — forcing a major system replacement through anyway is how projects fail.
Better to define the case clearly, sequence it properly, and execute it well than to start a migration the organisation isn't ready to land.
If you're trying to build the case for a legacy replacement — or work out whether your systems are holding back your AI and data ambitions — our Cloud Migration Assessment will give you the architecture options, cost comparison, and business case framework to make a confident decision.