Your legacy system has probably carried the business for years. It knows your processes, holds your history and quietly runs the jobs everyone depends on. Moving it to a modern platform is a chance to keep everything that works and unlock what comes next: mobile access, connected systems, live reporting and AI.
The difference between a smooth migration and a stressful one is almost always planning. Here's the checklist we use with clients, plus the advice we give leaders before they start.
Start with the outcomes, not the technology
Before anyone mentions frameworks or cloud providers, agree what the business should gain. Pick three outcomes you can measure, for example:
- quotes produced in minutes
- staff working from a phone or tablet on site
- one live dashboard the whole leadership team uses
These outcomes guide every decision that follows, from what to migrate first to what to leave behind. They also give your board a simple way to see the value as each stage lands.
Choose the right path for each part
Most systems don't need one approach for everything. Look at each module or function on its own and pick the path that suits it.
| Path | What it means | Best when |
|---|---|---|
| Rehost | Move the system as it is to modern hosting, such as the cloud | The software works well and you mainly want better hosting, reliability or running costs |
| Replatform | Move to a modern platform with modest changes, such as a newer database or framework | The core logic is sound and the platform underneath is due for renewal |
| Rebuild | Re-create the system in modern technology, module by module | The system is central to how you compete and needs to grow with you |
| Replace | Switch to an off-the-shelf product and bring your data across | The function is standard, such as accounting or payroll |
| Retire | Switch it off and archive its data | Another system already covers it, or it has served its purpose |
Step by step beats big bang
The smoothest migrations move one piece at a time. The new system grows around the old one and takes over a module at a time, while the legacy system keeps running everything else. You may hear engineers call this the strangler fig pattern.
For leaders, the benefits are simple: value arrives early, every step is small enough to test properly, and the business keeps running the whole way through.
The migration checklist
Work through these six phases in order. Each one sets up the next.
1. Discover
- List every feature, report, integration and scheduled job, including the quiet ones like overnight exports and the spreadsheet that reads straight from the database.
- Spend time with the people who use the system daily. Note their favourite features and any workarounds.
- Map your data: what's stored, how much, who owns it, and which records hold personal or regulated information.
- Capture what your long-serving experts know about how the system really works.
- Note contract, licence and hosting renewal dates, as they often set a natural timeline.
2. Plan
- Confirm your three outcomes and how you'll measure them.
- Choose a path for each module: rehost, replatform, rebuild, replace or retire.
- Start with a slice that's low risk and highly visible, so the team sees an early win.
- Name an internal product owner with the authority to make decisions quickly.
- Include time and budget for parallel running, training and a sensible contingency.
- Plan how you'll keep staff and customers informed at each stage.
3. Prepare the data
- Tidy up before you move: merge duplicates and archive what you no longer need.
- Match each old field to its new home, and decide how much history to bring across.
- Rehearse the migration several times using copies of real data.
- Check every rehearsal by reconciling record counts and key totals.
- Keep the old data available in read-only form for reference and compliance.
4. Build and test
- Build in slices, with a working demo every fortnight.
- Test with real users doing real tasks, against clear acceptance criteria for each slice.
- Reconnect integrations and test them end to end.
- Set up user roles, access and security in the new system from day one.
5. Go live
- Choose a calm window, away from peak trading or the end of the financial year.
- Run old and new side by side for a short period and compare the results.
- Prepare a simple fallback plan, which gives everyone confidence.
- Have extra support on hand, with a champion in each team to help colleagues.
6. After go-live
- Measure against your three outcomes and share the wins.
- Gather feedback and make quick improvements while the project has momentum.
- Retire the old system properly: archive the data, cancel licences and shut down servers securely.
- Celebrate with the team. They've earned it.
Advice for leaders
- Treat it as a business change, not an IT project. The technology is the easy part. Success comes from involving the people who use the system and keeping your outcomes front and centre.
- Keep the good bones. Your existing system holds years of hard-won business rules. Bring that knowledge across before redesigning around it.
- Make time for your experts. The people who know the old system best are your most valuable asset during a migration. Free up some of their week to help.
- Celebrate small wins. Every module that goes live is progress the whole business can see, and momentum is contagious.
- Budget for the finishing touches. Parallel running, training and the final clean-up all take time. Plan for them up front and the finish line arrives on schedule.
How James Anthony Consulting can help
James Anthony Consulting helps organisations move from legacy systems to modern platforms, one confident step at a time. We can keep your current system running smoothly while we build what comes next, migrate your data with care, and pick up systems built by other teams.
A short discovery phase is a great first step. In a few weeks you'll have a clear map of your system, a recommended path for each part and a firm quote. If you're planning a migration, or just starting to think about one, get in touch for a chat.
