Modernise a legacy system when it still does valuable work but is hard to change, integrate or support. Replace it when it blocks the way your business needs to work, or when keeping it costs more and carries more risk than moving on. In practice, most UK businesses end up with a mix: modernising some parts, replacing others and retiring what nobody uses. This guide gives you a scorecard to make the call, compares cost, time and risk, and shows how real SME scenarios play out.
- The system holds valuable business rules
- Problems are mainly technical: speed, security, hosting, integrations
- Your processes still broadly work
- You can't afford major disruption
- Your processes have outgrown the system
- It runs on unsupported technology that can't be upgraded safely
- A good off-the-shelf product now fits your needs
- Keeping it would lock in problems you need to fix
1. Your Options: More Than Modernise or Replace
"Modernise or replace" is a useful shorthand, but there are really seven routes. Choosing the right one starts with knowing them all.
| Route | What it means | Best when |
|---|---|---|
| Retain | Keep the system and support it properly | It's stable, secure and still fits, or will be replaced soon anyway |
| Rehost | Move it to the cloud as it is | Ageing servers or hosting are the main risk |
| Replatform | Upgrade the platform underneath, such as the framework or database | The code is sound but the technology is going out of support |
| Refactor | Restructure the code without changing what it does | Changes are slow and risky, but the logic is valuable |
| Wrap | Add APIs around the system so other tools can connect | The core can't safely change but needs to integrate |
| Replace | Move to a SaaS product or a new custom system | The system blocks how the business needs to work |
| Retire | Switch it off | Nobody depends on it, or its job is done elsewhere |
The first five are forms of modernisation. A single system can use several: for example, rehosting now, wrapping it with APIs next quarter and replacing one module next year.
2. Signs Your Legacy System Needs Action
Age alone isn't a reason to act. These signs are:
- It runs on software or servers that no longer receive security updates
- Only one or two people, or one contractor, understand it
- Small changes take weeks and often break something else
- Staff rely on spreadsheets and re-keying to work around it
- It can't connect to newer tools such as your CRM, website or payment system
- Reports are slow, unreliable or done by hand
- Outages or performance problems are becoming more frequent
- You can't easily use your data for analytics or AI
- Support costs rise every year
If several apply, the next question is whether to modernise or replace. If none apply, the right answer may be to keep it and support it well; see our legacy application support.
3. The Modernise or Replace Scorecard
Score your system from 1 (low) to 5 (high) on each question. Ideally, ask both a business owner and a technical lead to score it, then compare.
| Question | Your score (1–5) |
|---|---|
| A. Business value: how important are the processes and rules inside the system? | |
| B. Process fit: how well does it match how you work today? | |
| C. Code health: how safely can developers change it? | |
| D. Technical risk: how exposed is it to unsupported platforms, security gaps or skills shortages? | |
| E. Future fit: how badly does it hold back plans such as integrations, growth or new services? | |
| F. Market alternatives: how well would an off-the-shelf product cover your needs? |
How to read your scores
- A, B and C high (4–5), D and E low: retain or lightly modernise. The system is healthy; keep it supported.
- A and B high, C low or D high: modernise. The logic and process are worth keeping; the technology needs work.
- B low and E high: replace. The business has outgrown the system.
- Replace, with F high: consider a SaaS product. With F low, consider a custom build.
- A low: consider retiring it.
4. Modernisation vs Replacement: Cost, Time and Risk Compared
| Modernise | Replace with SaaS | Replace with a custom build | |
|---|---|---|---|
| Typical upfront cost | £10,000 – £150,000+ | Implementation from £10,000, plus subscriptions | £50,000 – £500,000+ |
| Typical timeline | Weeks to months, in phases | 2 – 9 months | 6 – 18 months+ |
| Disruption to staff | Low to medium | Medium to high (new processes) | Medium to high |
| Delivery risk | Lower | Medium | Highest |
| Keeps your business rules | Yes | Only if the product supports them | Yes, if documented first |
| Ongoing cost | Support and hosting | Per-user or per-month fees | Support and hosting |
| Fixes process problems | Rarely | Often, by adopting standard processes | Yes, if processes are redesigned |
Indicative UK ranges excluding VAT. For a detailed breakdown by approach and system size, see our legacy software modernisation cost guide.
5. A Five-Year Cost of Ownership Example
Upfront price is only part of the picture. Compare the total cost over five years. Here's an illustrative example for a mid-sized operations system used by 40 staff:
| Five-year cost | Keep as is | Modernise | Replace with SaaS |
|---|---|---|---|
| Upfront project | £0 | £80,000 | £35,000 |
| Support and hosting (5 years) | £150,000 | £75,000 | £20,000 |
| Licences or subscriptions (5 years) | £10,000 | £10,000 | £120,000 |
| Staff workarounds and re-keying (5 years) | £100,000 | £30,000 | £30,000 |
| Five-year total | £260,000 | £195,000 | £205,000 |
Illustrative figures only. Use your own support invoices, licence costs and an estimate of staff time spent on workarounds.
In this example, both modernising and replacing cost less over five years than doing nothing, and modernisation edges ahead. A different business, with a SaaS product that fits better or a system that's harder to fix, could get the opposite result. That's why the numbers should be worked out for your own system.
6. Replacing: Off-the-Shelf SaaS or a Custom Build?
If replacement wins, the next decision is what to replace it with.
| SaaS or off-the-shelf | Custom build | |
|---|---|---|
| Best for | Standard processes such as accounting, HR or CRM | Processes that differentiate your business |
| Speed | Faster to start | Slower, but built around you |
| Long-term cost | Grows with users and price rises | Mainly support and hosting |
| Control | Vendor's roadmap | You own it |
| Watch out for | Customisation limits and data export | Scope creep and dependency on documentation |
A common middle route is SaaS for standard functions plus custom software for what makes you different, connected through integrations. Read our full bespoke software vs SaaS comparison, or see our bespoke software development services.
7. How to Replace a Legacy System Safely, Piece by Piece
The riskiest way to replace a system is to switch everything over on one weekend. A safer approach, often called the strangler fig pattern, replaces it gradually:
- Wrap the old system with APIs, so new parts can work alongside it.
- Pick one area to move first: something valuable but contained, such as customer bookings or reporting.
- Build the new part and route that work to it, while everything else stays on the old system.
- Prove it works with real users before moving on.
- Repeat for each area, moving data in stages.
- Switch off the old system once nothing depends on it, and confirm hidden reports and exports have been replaced.
Each step delivers value, and you can pause or change course without losing everything. Starting with a small first version is similar to an MVP; see our MVP development approach.
We'll review your system, score it against the options and give you a phased recommendation with indicative GBP costs. No obligation.
Get my free recommendation8. Three UK SME Scenarios
Scenario 1: Modernise. A distributor's .NET order system
A Midlands distributor runs a 12-year-old .NET Framework order system with years of pricing rules built in. It works, but it's slow, hosted on an ageing server and can't connect to the new ecommerce site.
Decision: modernise. The rules are valuable and the process still fits. They rehost to the cloud, upgrade to modern .NET and add APIs for the website, in phases over about six months. See our .NET development services.
Scenario 2: Replace with SaaS. A spreadsheet-based CRM
A professional services firm tracks clients in an old Access database plus shared spreadsheets. Its processes are standard, and several CRM products fit well.
Decision: replace with a SaaS CRM, migrate the data and connect it to email and accounts. The custom work is limited to data migration and integration.
Scenario 3: Replace with a custom build. A booking platform that limits growth
A training provider's booking system can't handle online payments, multiple venues or a customer portal, and the original developer has left. Its booking rules are unusual, so off-the-shelf products don't fit.
Decision: replace with a custom platform, area by area: bookings first, then payments, then the portal, retiring the old system at the end.
9. UK Compliance and Support Deadlines to Factor In
- End of support: older platforms such as Windows Server 2012 (October 2023) and SQL Server 2014 (July 2024) no longer receive standard security updates, and .NET versions have fixed support end dates. Check yours.
- Security guidance: the NCSC advises organisations to manage the risks of obsolete products and plan their replacement.
- UK GDPR: any route involving data migration needs secure handling, a clear lawful basis and often a data protection impact assessment.
- Cyber Essentials: unsupported software can stop you meeting the scheme's requirements, which some customers and contracts require.
- Financial services: FCA operational resilience rules expect firms to keep important business services within impact tolerances, which brings fragile legacy systems into scope.
10. Data Migration Checklist
Whether you modernise or replace, data is usually where projects slip. Before you start:
- List every data source, including spreadsheets and exports people rely on
- Decide what to migrate, archive or delete under your retention rules
- Clean duplicates and fix inconsistencies before migration, not after
- Map old fields to new ones and agree who signs off the mapping
- Run trial migrations and compare record counts and totals
- Plan a cutover window and a rollback option
- Keep the old data accessible, read-only, for an agreed period
If you're also moving infrastructure, see our cloud migration services.
11. Building the Business Case for Your Board
A strong business case for modernising or replacing a legacy system covers:
- The problem in business terms: outages, lost sales, staff time, security exposure.
- The options considered, including doing nothing.
- Five-year costs for each option, as in the example above.
- Risks and how each is reduced, such as phased delivery and parallel running.
- Benefits you'll measure: faster changes, fewer incidents, hours saved, new capabilities.
- The first phase: a small, low-risk step that proves value quickly.
- The exit plan for the old system, with a target date.
For wider programmes, our digital transformation cost guide can help with budgeting.
12. Common Mistakes to Avoid
- Replacing because it's old, not because it's a problem. Stable, valuable systems can often be modernised for less.
- Copying old processes into a new system. Fix the process first, or you'll rebuild the same problems.
- Losing hidden business rules. Document what the old system actually does before replacing it.
- The "big bang" cutover. Phased delivery is almost always safer.
- Never switching off the old system. Running both indefinitely doubles the cost.
- Assuming the cloud fixes everything. Rehosting reduces hosting risk but doesn't fix code, data or process problems.
- Ignoring AI readiness. If your data is locked inside the old system, plan how to make it accessible. See AI integration.
How Fulminous Software Can Help
Fulminous Software is a London-headquartered development company that helps UK organisations decide what to do with legacy systems, then delivers it: modernising, integrating, replacing or supporting them in phases. See our legacy application modernisation services, or our enterprise software development for larger replacement programmes.
13. Frequently Asked Questions
What is the difference between legacy modernisation and replacement?
Modernisation improves the existing system, for example by moving it to the cloud, upgrading its platform, restructuring its code or adding APIs. Replacement moves to a different system, either an off-the-shelf SaaS product or a new custom build, and retires the old one.
Is it cheaper to modernise or replace a legacy system?
Modernisation usually costs less upfront and carries less risk, typically £10,000 to £150,000 or more depending on the approach. Replacement can cost less over five years if a SaaS product fits well, or more if a large custom build is needed. Compare five-year costs, not just the upfront price.
How do I decide whether to modernise or replace?
Score the system on business value, process fit, code health, technical risk, future fit and available alternatives. Valuable systems with technical problems usually suit modernisation; systems that no longer fit how the business works usually suit replacement.
When should a legacy system be retired?
When it no longer supports a meaningful business need. Before switching it off, check that no users, reports, exports or integrations still depend on it.
Is moving to the cloud the same as modernisation?
No. Moving a system to the cloud as it is reduces hosting and hardware risk, but it doesn't fix outdated code, poor integrations or process problems. It's often a useful first step rather than the whole answer.
What is the strangler fig pattern?
It's a way of replacing a legacy system gradually: you wrap the old system with APIs, rebuild one area at a time and route work to the new parts, then switch off the old system once nothing depends on it. It avoids a risky big-bang cutover.
How long does legacy modernisation or replacement take?
Modernisation is often delivered in phases over weeks to months. Replacing with SaaS typically takes 2 to 9 months, and a custom replacement 6 to 18 months or more, depending on size and data migration.
Should we replace our system with SaaS or build custom software?
Choose SaaS when your processes are standard and a product fits well. Build custom software when your processes are distinctive or give you a competitive edge. Many businesses combine both.
Book a free consultation. We'll assess your legacy system, compare modernisation and replacement, and outline a phased plan with costs.
Book a free consultation Our modernisation services
Verified
Expert in Software & Web App Engineering


