Legacy System Modernisation: Replacing the Software Your Business Depends On

Legacy system modernisation means replacing or upgrading the old software your business depends on, such as an ageing database, a bespoke system written years ago or a platform the vendor no longer supports, without disrupting the work it supports every day. For small and mid-sized firms the technology is rarely the hard part. The hard parts are the data, the cut-over and getting people to change how they work.

This guide covers the signs a system is holding you back, the risks of leaving it, the options (replace, rebuild or wrap), data migration, phased cut-over, training and costs, with an example from a migration we have worked on.

Signs a system is holding you back

Legacy does not simply mean old. It means a system that has become harder to live with than to replace. Common signs:

• The software or the server it runs on is no longer supported with security updates.
• One person understands it, and the business worries about what happens if they leave.
• Data is trapped. Reports require manual exports, and nothing connects to your newer tools.
• Workarounds are everywhere. Spreadsheets, re-keying and manual checks fill the gaps.
• Changes are slow or impossible. Simple requests take weeks or cannot be done at all.
• It only works on one machine or one browser.

If several of these sound familiar, it is time to plan legacy system modernisation, even if the replacement is some way off. Our guide to signs you have outgrown spreadsheets covers the most common legacy system of all.

Risks of doing nothing

Leaving a legacy system in place feels safe because it works today. The risks build quietly:

• Security. Software and servers without security updates are easy targets. The NCSC's guidance on obsolete products explains why unsupported technology should be replaced or isolated.
• Key-person dependency. Knowledge that lives in one head is lost when that person leaves or is ill.
• Integration. New tools, suppliers and customers expect data to flow automatically.
• Compliance. Old systems can make it hard to meet UK GDPR duties such as finding, correcting or deleting personal data.
• Hardware failure. Old servers and machines fail, and replacement parts get harder to find.

Replace, rebuild or wrap

There are three broad routes, and the right one depends on how distinctive the system's job is.

Replace with off-the-shelf software when the process is standard. Accounting, HR and basic CRM needs are usually better served by established products.

Rebuild as custom software when the process is distinctive and valuable, and no product fits. The new system is designed around how you work now, not how you worked when the old one was written. Our guide to custom web application development explains how those projects run.

Wrap the old system when it still does its core job but cannot connect to anything. A modern layer, such as an API or a new web interface, sits in front of it. This buys time and can become the first step of a gradual replacement.

Data migration

Data migration is where most legacy projects overrun. Treat it as a project in its own right:

1. Audit what data exists, where it lives and who uses it.
2. Map each old field to its new home, deciding what to do with fields that have no equivalent.
3. Clean duplicates, inconsistent formats and missing values before moving anything.
4. Run test migrations into a copy of the new system and check the results with the people who know the data.
5. Reconcile counts and totals between old and new: customers, orders, balances.
6. Archive what you do not migrate, in a readable format, for as long as you need to keep it.

We worked on a training provider's move from an old online course platform to a new learning system. The technical task sounded simple: move the videos and rebuild the courses. In practice, every course had to be mapped module by module, videos retrieved and checked, and course structures rebuilt to match how the new platform works. Doing it course by course, with checks after each, was slower than a bulk import but avoided missing lessons and broken links for learners.

Phased cut-over

Switching everything over in one weekend is risky. A phased cut-over reduces it:

• Move one module or process at a time, such as enquiries first, then orders, then reporting.
• Run old and new in parallel for a short period on critical processes, comparing results.
• Freeze changes to the old system during the final migration window.
• Have a rollback plan so you can switch back if something serious goes wrong.
• Choose quiet periods for the key switches, never your busiest week.

This approach is sometimes described as strangling the old system: the new one gradually takes over until the old one can be switched off.

Training and adoption

A new system only pays off if people use it properly. Involve the people who use the old system from the start, because they know its quirks and the workarounds it relies on. Train in short sessions close to go-live, provide short written guides and name a go-to person for questions in the first weeks. Expect productivity to dip briefly before it improves, and plan around it.

Costs

Costs vary widely with the size of the system and the state of the data. As a rough guide:

• Assessment and planning: often £2,000 to £5,000 for a small or mid-sized system, producing a recommendation and a scoped plan.
• Wrapping with an API or new interface: typically £8,000 to £25,000.
• Rebuilding as custom software: commonly £15,000 to £100,000 or more, depending on complexity.
• Running costs during transition, such as keeping the old system alive for parallel running.

A clear statement of work matters even more than usual on these projects, because migration and cut-over are where hidden assumptions live. Our guide to software statements of work explains what to check. If the legacy system manages leads, see lead management systems. For systems built around WordPress, custom WordPress plugin development can sometimes replace an old tool without a separate application. You can see our work on our custom web apps, custom CRM systems and custom portals pages.

Frequently asked questions

Plan your replacement

If your business depends on a system nobody wants to touch, talk to us about modernising it. We will start with an assessment and a plan you can act on in phases.