Legacy software modernisation in the UK typically costs £15,000 to £50,000 for a small internal system, £50,000 to £150,000 for a mid-sized business application, and £150,000 to £500,000 or more for a core enterprise platform. The biggest factor isn't the size of the system but the approach you choose: moving an application to the cloud as it is costs far less than redesigning or rebuilding it. This guide breaks down the cost of each approach, what drives the price, the hidden costs, and the cost of doing nothing.
- Assessment and roadmap: £3,000 – £15,000
- Small internal system: £15,000 – £50,000
- Mid-sized business application: £50,000 – £150,000
- Core enterprise platform: £150,000 – £500,000+
- Ongoing support after modernisation: often 15–20% of the project cost a year
Indicative UK ranges excluding VAT, cloud hosting and licences.
1. Legacy Modernisation Cost by Approach
Most modernisation projects use one, or a mix, of these approaches. Each comes with a very different price and level of risk.
| Approach | What it means | Indicative cost | Risk |
|---|---|---|---|
| Rehost ("lift and shift") | Move the application to the cloud with minimal code changes | £10,000 – £50,000 | Low |
| Replatform | Upgrade the platform, such as .NET Framework to modern .NET or a newer database | £20,000 – £80,000 | Low to medium |
| Refactor | Restructure and clean up the code without changing what it does | £30,000 – £150,000 | Medium |
| Rearchitect | Redesign into modular or cloud-native services | £80,000 – £300,000+ | Medium to high |
| Rebuild | Rewrite the application from scratch on modern technology | £50,000 – £500,000+ | High |
| Replace | Move to an off-the-shelf or SaaS product | Implementation from £10,000, plus licences | Medium |
Rehosting is the cheapest way to get off ageing servers, but it doesn't fix outdated code. Rebuilding fixes everything but costs the most and carries the most delivery risk. Many projects combine approaches, for example rehosting first, then refactoring the most important parts.
Weighing a rebuild against a SaaS product? Our bespoke software vs SaaS guide compares the long-term costs.
2. Legacy Modernisation Cost by System Size
| System | Typical example | Indicative cost | Typical timeline |
|---|---|---|---|
| Small internal tool | A departmental database or reporting tool with a few users | £15,000 – £50,000 | 1 – 3 months |
| Mid-sized business application | A customer portal or operations system with integrations | £50,000 – £150,000 | 3 – 9 months |
| Core enterprise platform | ERP, policy, booking or finance systems used across the business | £150,000 – £500,000+ | 9 months or more, in phases |
Indicative ranges excluding VAT. Your cost depends on the approach, code quality and integrations.
3. What Drives the Cost of Legacy Modernisation?
Code quality and documentation
Well-structured, documented code is cheaper to modernise. Undocumented systems need time to understand before anything can change safely.
Age and technology
Older languages and platforms, such as Classic ASP, VB6, early PHP or old .NET Framework versions, often need more work and scarcer skills.
Integrations
Every connection to finance, CRM, payment or partner systems must be preserved and retested.
Data migration
Large or messy databases need cleaning, mapping and validation, which often takes longer than expected.
Business rules hidden in the code
Years of undocumented logic must be uncovered and kept, so the new system behaves correctly.
Downtime tolerance
Systems that can't go offline need parallel running and careful cutover, which adds cost.
Compliance
Regulated sectors need extra security, audit trails and evidence, such as UK GDPR or FCA requirements.
4. Where the Budget Goes
| Phase | Typical share of budget | What it covers |
|---|---|---|
| Assessment and planning | 5–10% | Code review, architecture, risks and roadmap |
| Design | 5–15% | New architecture and, if needed, new user interfaces |
| Development | 40–55% | Migration, refactoring or rebuilding |
| Data migration | 10–15% | Cleaning, mapping and moving data |
| Testing | 10–20% | Regression, performance and security testing |
| Cutover and training | 5–10% | Go-live, parallel running and user training |
Typical proportions; your project may differ.
5. Worked Example: Modernising a .NET Framework Application
A UK distribution company runs a 12-year-old .NET Framework web application with around 40 screens, a SQL Server database and integrations with its accounts and warehouse systems. It wants to move to modern .NET on Azure.
| Item | Indicative cost |
|---|---|
| Assessment and roadmap | £6,000 – £10,000 |
| Code migration and refactoring | £35,000 – £60,000 |
| Database and data migration | £8,000 – £15,000 |
| Integration updates and testing | £10,000 – £18,000 |
| Cloud set-up, cutover and training | £4,000 – £8,000 |
| Total | £63,000 – £111,000 |
Illustrative only. Delivered in phases over roughly 5 to 8 months.
For .NET-specific advice, see our .NET development services.
6. Hidden Costs to Budget For
- Parallel running: keeping the old system live while the new one is proven.
- Data clean-up: fixing duplicates and inconsistencies before migration.
- Licences: new cloud services, databases or third-party components.
- Training and change: helping staff adopt new screens and workflows.
- Integration partners: fees charged by suppliers to change their side of an integration.
- Cloud running costs: monthly hosting, which replaces, but doesn't always undercut, on-premise costs.
- Contingency: a reserve of 10–20% for surprises found in old code.
If you're also moving infrastructure, see our cloud migration services.
7. The Cost of Doing Nothing
Modernisation is a big investment, but keeping an ageing system has costs too, and they rise each year:
- Security risk: software and servers past their end of support no longer receive security updates.
- Rising support costs: fewer developers know older technologies, so specialist help costs more.
- Extended support fees: paying vendors to keep unsupported platforms patched.
- Slower change: simple updates take longer and break more often.
- Lost opportunities: difficulty adding integrations, mobile access or AI features.
- Compliance gaps: older systems may struggle to meet current security and data protection expectations.
Tell us about your system, its technology and what it connects to. We'll suggest the right approach and send a phased GBP estimate.
Get my free estimate8. Keep Supporting or Modernise?
| Keep supporting the legacy system if… | Modernise if… |
|---|---|
| It's stable, secure and still meets business needs | It runs on unsupported platforms or can't be patched |
| It will be replaced within a year or two anyway | Support costs and incidents keep rising |
| Changes are rare and small | The business needs new features or integrations |
| Budget is needed elsewhere right now | Key knowledge sits with one or two people |
If keeping the system running is the right choice for now, our legacy application support team can maintain and stabilise it while you plan the next step. When you're ready to move forward, see our legacy application modernisation services.
9. How to Reduce Modernisation Costs
- Start with an assessment so the approach and budget are based on facts, not guesses.
- Modernise in phases, starting with the parts that carry the most risk or value.
- Choose the lightest approach that works. Not every system needs a rebuild.
- Retire unused features rather than migrating them.
- Clean data early to avoid delays at cutover.
- Automate testing so each phase can be released safely.
- Check funding options: some modernisation work may qualify for R&D tax relief if it resolves genuine technical uncertainty. Ask your accountant.
For wider programmes, read our digital transformation cost guide.
10. How to Get an Accurate Quote
Prepare these before speaking to developers:
- The technology, age and size of the system
- Access to the code, database and any documentation
- A list of integrations and who maintains them
- Users, peak usage and acceptable downtime
- Problems you need to solve and features you need next
- Your budget range and any deadlines, such as end-of-support dates
Ask for a quote that separates assessment, development, data migration, testing and cutover, so you can compare suppliers fairly. For new-build software prices, see our custom software pricing guide.
11. Frequently Asked Questions
How much does legacy software modernisation cost in the UK?
As a guide, modernising a small internal system typically costs £15,000 to £50,000, a mid-sized business application £50,000 to £150,000, and a core enterprise platform £150,000 to £500,000 or more. An initial assessment usually costs £3,000 to £15,000. Prices exclude VAT, hosting and licences.
What is the cheapest way to modernise a legacy application?
Rehosting, or moving the application to the cloud with minimal code changes, is usually the cheapest option at around £10,000 to £50,000. It reduces infrastructure risk but doesn't fix outdated code, so many businesses follow it with targeted refactoring.
Is it cheaper to rebuild or modernise legacy software?
Modernising through rehosting, replatforming or refactoring is usually cheaper and less risky than a full rebuild. A rebuild makes sense when the code is too fragile to change safely or the business needs have changed significantly.
How long does legacy modernisation take?
A small system can often be modernised in 1 to 3 months, a mid-sized application in 3 to 9 months, and a core enterprise platform in 9 months or more, usually in phases.
What hidden costs come with legacy modernisation?
Common hidden costs include running old and new systems in parallel, cleaning data, new licences, training, changes by integration partners, ongoing cloud costs and a contingency of around 10 to 20 percent.
Should I keep supporting my legacy system instead of modernising it?
If the system is stable, secure and meets your needs, ongoing support can be the right choice for now. If it runs on unsupported platforms, support costs are rising or the business needs new features, modernisation usually pays off.
Can legacy modernisation qualify for R&D tax relief?
Some work may qualify if it resolves genuine scientific or technological uncertainty, but routine migration usually doesn't. Check eligibility with your accountant before relying on it.
Book a free consultation. We'll review your system, outline the options and give you a realistic, phased budget.
Book a free consultation Our modernisation services
Verified
Expert in Software & Web App Engineering


