# Legacy software modernisation for UK businesses, one working stage at a time

Canonical: https://appagentix.co.uk/services/software-modernisation/

For legacy software modernisation, we take over ageing business software, make it safe, then replace it in slices while your staff keep working. The code and hosting sit in your name.

- Assessment in 2 weeks, ending in a fixed quote
- First working stage in 8 to 14 weeks
- Old and new systems run side by side until you approve the switch

## What does legacy software modernisation cost, and how long does it take?

A first modernisation stage with AppAgentix costs £15,000 to £40,000 excluding VAT and takes 8 to 14 weeks. A larger system, done in several stages, takes 4 to 8 months. A two-week assessment comes first and ends in a fixed quote. After switchover, a monthly support plan starts and hosting is billed to your own account. For a small clinic’s five-module system, three years of modernising come to £68,150, less than keeping the old one running. Price your own version with the calculator on this page.

- Assessment: 2 weeks, ending in a fixed quote
- First stage: 8 to 14 weeks
- Larger system, several stages: 4 to 8 months

## What we check in week 1

An estimated 28% of systems in central government departments were legacy in 2024, up from 26% in 2023 (State of digital government review, January 2025).

### A timed change

We make one small change on a copy and time it from request to release.

The time one change takes, beside the cost of each route.

### Support dates

We list each server, database and library with its vendor’s end-of-support date. Microsoft’s last paid updates for Windows Server 2012 R2 ended in October 2026, while Windows 10 still had 13.8% of UK Windows desktop browsing in October 2026 (StatCounter, October 2026).

Each date beside the route it points to.

### Hand-copied figures

We count the figures two or three daily users copy between systems in a normal day.

Each connection priced as its own quote line.

### The cost of keeping it

We add up servers, licences and contractor fixes from your last twelve months of invoices.

The three-year cost of keeping it, beside each route.

## Old system to new, without a big switch-off

The old system keeps running while each part moves across in turn.

1. Audit
2. Wrap with an API
3. Move one part
4. Run side by side
5. Retire the old part

## Legacy system replacement or modernisation: wrap, slice or rebuild?

Route names follow the common R words.

Which route?

- If The software works and the risk is one person or missing backups, choose **Retain and stabilise**. The code stays; we add backups, tests and documents, then a monthly support plan.
- If The server, database or runtime is out of support, choose **Rehost or replatform**. Rehosting moves it unchanged; replatforming also swaps the database or runtime. Priced as a first stage.
- If Users or partners need a new front on a sound core, choose **Wrap with an API**. A modern interface sits in front while the old core keeps calculating.
- If You cannot stop trading and the system has clear modules, choose **Replace in slices**. Modules are rewritten in the worksheet’s order, with a parallel run before every switch.
- If The data model is wrong, so each fix breaks something else, choose **Rebuild**. One project replaces the whole system, once the old data is mapped.
- If A product on sale does the job, or nobody uses the module, choose **Repurchase a product, or retire**. Buying costs less than building, and switching off costs least.

## Legacy software modernisation on live systems

A few examples from the many systems we have built to replace tools that no longer fitted the way people work. Our longest client relationship is seven years and counting.

### MyUTHealth: a patient app on an existing records system

Healthcare

We built MyUTHealth, a patient portal app for a health provider, for Android on its existing records platform through HL7 FHIR APIs. Patients can ask for appointments, check test results and send secure messages to their care team.

Downloaded 50,000+ times from Google Play and rated 4.4 stars across 750+ reviews

[Read the MyUTHealth case study](https://appagentix.co.uk/our-work/myuthealth/)

### Clinic records system: separate tools brought together

Healthcare

With the clinic records system we built, registration, the medical record, consultation notes, the diary and billing sit in one system rather than in separate tools and paper files. Laboratory results come in over HL7 instead of being typed again, and the system runs on React and Java with SQL storage, hosted on AWS.

[Read the Clinic records system case study](https://appagentix.co.uk/our-work/clinic-records-system/)

### Coding school platform: replacing an old website

Education

This coding school’s old website made its courses hard to follow, and learners moved between separate tools for prep work, live lessons and campus days. We built a React and Next.js web platform, with a React Native app, that joins those stages in one learning hub and tracks admissions automatically, with Node.js and PostgreSQL behind it.

[Read the E-learning and admissions platform for a coding school case study](https://appagentix.co.uk/our-work/coding-school-platform/)

## Which module goes first: the slice order worksheet

In week 2 we score each module on three counts, then set the build order. Filled in for an illustrative example, not a client: a small physiotherapy clinic’s five-module system on an out-of-support server.

**Slice order worksheet, clinic system**

| Module | Change requests last year | If it fails for a day | Tables it shares | Build order |
| --- | --- | --- | --- | --- |
| Reminders | 14 | Texts go out late; staff can phone | 2 | 1st: changes most, fails safest |
| Reporting | 9 | Month-end figures wait a day | 5, read only | 2nd: reads data, never writes it |
| Bookings | 6 | The front desk cannot book | 4 | 3rd: once two modules prove the method |
| Invoicing | 3 | No bills go out and cash stops | 6 | 4th: costliest error, so built on tested code |
| Patient records | 1 | Clinicians lose treatment notes | 9 | 5th: moved with the final data copy |

Our rule: build first what changes most and breaks least, and move last whatever every other module reads. Modernise when the old system costs more to keep over three years than the new one costs to build and run.

## The parallel-run difference report you read before switchover

Every difference from two weeks of side-by-side running, for the same clinic.

**Parallel-run difference report, weeks 11 to 12**

| Check | Old system | New system | Result | Notes |
| --- | --- | --- | --- | --- |
| Bookings made | 612 | 612 | Pass | Same patients, times and clinicians |
| Takings, 10 working days | Matched | Matched, was 2p short | Pass after fix | New code split each six-session package into six sessions, losing 2p; the last session now carries it |
| Card payments matched to bookings | 548 | 548 | Pass | Checked against the card terminal’s daily report |
| Patient balances | 238 accounts | 238 accounts | Pass | Credit notes included |
| Overdue payment reminders | 57 | 61 | Open | New system counts day 30 as overdue, old one day 31; your practice manager picks the rule |

Switchover is booked only when no row is open, or you accept an open row in writing.

## Legacy application modernisation, week by week

More than 95% of our projects are delivered on or before the agreed date. Around 15% of survey respondents in the DSIT review could not even estimate the size of their legacy estate, so the assessment starts by counting yours.

### Assessment (Weeks 1 to 2)

We review the code, database and hosting, interview two or three daily users, score each module and price each route.

You receive: A report with the risks ranked, the build order, the three-year cost and a fixed quote.

### Make it safe (Weeks 3 to 4)

The code moves into a repository in your name, one backup is restored as a test, and tests go around key behaviour.

You receive: A restore log, a test suite and a runbook.

### Build the first slice (Weeks 5 to 10)

Modules are wrapped or rebuilt in two-week sprints, each ending with a demo on a copy of your data.

### Run in parallel (Weeks 11 to 12)

Both systems handle the same work for two weeks; the difference report lists every mismatch.

### Switch over (Weeks 13 to 14)

You approve the date and we run the final data copy, then the old system stays read-only for a month.

You receive: Migration counts you check yourself, and a handover session.

## What we would say no to

Each refusal protects your data or your budget. 74% of UK businesses back up data securely via a cloud service (DSIT Cyber Security Breaches Survey 2025/2026). A backup counts once it has been restored.

- **Code changes before a restore test.** Nothing changes until one backup has been restored on a test machine.
- **Switching with an open row.** Switchover waits until every difference row is settled or you accept it in writing.
- **AI on a rule nobody can write down.** An AI feature cannot be tested against an unwritten rule, so we write the rule first.
- **Taking over without access.** We need admin access to the database and hosting before the quote is fixed.
- **Rebuilding a quiet module.** A module with no change requests in a year, on supported software, is left alone or wrapped.
- **A whole-system price on day one.** The fixed figure follows the assessment, because the state of the data sets the cost.

## Legacy software modernisation services, line by line

### First call

A written view on scope and price within two working days. 30 minutes, free.

### Assessment

Risks ranked, module scores, three-year costs and a fixed quote, credited if you continue. 2 weeks.

### First legacy modernisation stage

Making it safe, one slice or a whole small system like the clinic’s, a parallel run and its data migration. 8 to 14 weeks.

### Full legacy system replacement

A system too big for one stage: several stages or a full rebuild, each repeating weeks 5 to 14. 4 to 8 months.

### AI feature on one workflow

Tested on your cases, with the running cost on the quote. 6 to 10 weeks.

### Support and running

Billed monthly: fixes, security updates and a monthly report. Minimum 3 months, then 30 days’ notice.

## Estimate your first modernisation stage in a minute

Pick what the stage replaces.

Assessment, making it safe, one module wrapped, parallel run, migration: £15,000 to £17,500, 8 to 9 weeks.

### Route

- Wrap with an API: included
- Rebuild in new code: £3,000 to £6,000

### Data

- Current records: included
- History or extra source: £2,000 to £3,500

### Links

- None: included
- One system, documented API: £2,500 to £4,000
- Older or several systems: £6,000 to £10,000

### Screens

- None: included
- View and search, read-only: £3,000 to £6,000
- Working screens, roles, audit: £9,000 to £15,000

### Also replaced

- One hosted dashboard: £1,500 to £3,000
- Cloud hosting you own: £2,000 to £3,000
- Supported database version: £1,500 to £2,500
- Automated release pipeline: £1,500 to £2,500
- Staff training: £1,000 to £1,500
- AI on your documents: £15,000 to £25,000

An estimate excluding VAT; the assessment fixes the price.

## A sample scope: the build and what runs after it

Every line for the clinic example, and who bills it.

**Scope lines, clinic system**

| Line | One-off | Each month | Billed by |
| --- | --- | --- | --- |
| First stage, five modules | One fixed figure | None | AppAgentix, assessment included |
| Fixes for 3 months after switchover | Included | None | AppAgentix |
| Support plan, after those 3 months | None | Monthly plan | AppAgentix, 30 days’ notice |
| Hosting in your account | None | Cloud bill | Your cloud provider |
| Licences and exit fees | None here | None | Each vendor, listed when they apply |

An AI feature adds its own running-cost line here.

## What our software modernisation services include and exclude

Ask every supplier for the second half.

- **Documents.** Included: a system map, a data dictionary for the tables we touch, and a runbook.
- **Tests.** Included: automated tests for the behaviour we change, plus the difference report.
- **Data migration.** Included: one migration, rehearsed on a copy before switchover.
- **Ownership.** Included: the repository, hosting account and domain sit under your organisation from the first commit, with us as a user you can remove.
- **Dirty data.** Not included: we report duplicated or missing records and quote the clean-up separately.
- **Vendor fees.** Not included: licences, API charges and the old supplier’s exit fees, listed on the quote.
- **Staff time.** Not included: a named contact of yours for about two hours a week.

## How a UK rule changes the project

Project guidance, not legal advice.

| Rule or date | What changes in the project |
| --- | --- |
| UK GDPR security principle | A backup is restored on a test machine before any code changes. The ICO asks for measures that can restore personal data after an incident. |
| UK GDPR Article 35, impact assessments | The assessment report says whether the change needs an impact assessment |
| UK GDPR storage limitation | Records past your retention period are left out of the migration |
| Vendor end-of-support dates | Unsupported components are replaced or isolated in weeks 3 to 4. Per the NCSC, only retiring an obsolete product removes its risk in full. |
| Cyber Essentials control on security updates | A dated list of each component and its update status, ready for a customer’s questionnaire |

## Legacy software modernisation questions, answered

### What is legacy modernisation?

It is making old business software safe, supported and easier to change, without losing its data or rules. The work ranges from new hosting, through a new interface, to a module-by-module rebuild.

### How to modernize legacy systems?

Assess, make the system safe, then change one part at a time. With us: a two-week review, a restored backup and automated tests, modules rebuilt in the worksheet’s order, and a parallel run before each switch.

### Why do companies still use legacy systems?

Because it still does its job, and replacing it carries cost and risk. Its code holds years of unwritten business rules, and a failed switch puts invoicing or bookings at risk.

### Why do companies not replace all of their legacy systems?

Because some parts do not earn a rebuild. In our week 2 scoring, a module with no change requests in a year, supported software and few shared tables is left alone or wrapped.

### What are the 5 R's of modernization?

Lists differ, so there is no single set of five, while AWS lists seven: retire, retain, rehost, relocate, repurchase, replatform and refactor. Refactor rewrites the code, repurchase buys a product, and retire switches it off.

### How much does it cost to maintain software?

Add up hosting, licences, fixes and the staff time lost to workarounds. Our support plan starts at £750 a month excluding VAT, and the assessment totals your current system’s three-year cost.

### Can you give me an example of legacy modernization?

Take the clinic above, where reminders are rebuilt first and patient records move last. Both versions handle the same bookings and takings for two weeks, and the new one takes over once every difference is settled.

### How do you fix outdated software?

Find which part is out of date: the operating system, the database or the code. Replace unsupported parts first, add backups and tests, then change the code in small steps.

## Related services

- [Web app development company](https://appagentix.co.uk/services/web-app-development-company/)
- [Custom CRM and ERP development](https://appagentix.co.uk/services/custom-crm-erp-development/)
- [App maintenance and support](https://appagentix.co.uk/services/maintenance-support/)
- [MVP development](https://appagentix.co.uk/services/mvp-development/)
- [DevOps and CI/CD implementation](https://appagentix.co.uk/services/devops-cicd-implementation/)
- [Product engineering](https://appagentix.co.uk/services/product-engineering/)
- [App development cost in the UK](https://appagentix.co.uk/app-development-cost/)
- [Healthcare software development](https://appagentix.co.uk/industries/healthcare-software-development/)
- [Insurance software development](https://appagentix.co.uk/industries/insurance-software-development/)

By [Megha Sharma](https://www.linkedin.com/in/meghanify/), Chief Marketing Officer, AppAgentix. Reviewed November 2026.

[Book a call](https://appagentix.co.uk/requestaquote/)
