Skip to main content

Data Migration

Data migration services for UK businesses leaving an old system or CRM. Trial imports, record-level checks and a rollback point agreed before go-live.

Data migration is moving your records and their history from one system into another without losing anything that matters. We provide data migration services for UK businesses replacing a CRM, a practice or case management system, an Access database or an in-house platform, and we start every job by looking at the real data before quoting.

Why This Is the Riskiest Part of Any Replacement

Data that has built up over years is never as clean as anyone expects. That isn’t a criticism of the business. It’s what happens to records kept by many people over a long period.

Duplicates that a permissive system tolerated will break a strict one. Fields get used for something other than their label, dates turn up in three formats, and notes carry information that never had a field of its own. Some records point at other records deleted years ago.

None of that is visible from outside, so a migration estimate made without looking at the data is a guess. The most reliable predictor of a difficult migration is that nobody has run a trial import yet.

What We Migrate

Most jobs are part of a system replacement. A firm moving from an old CRM to a new one, or from a case management system the vendor has stopped developing, needs the clients, matters, contacts and history to arrive intact and still linked to each other. Others are consolidations, where two systems that each held half the picture become one.

Access databases and spreadsheets that grew into the business’s main record are a common starting point too. Our page on Access database migration covers the particular problems those bring. If what you need is two systems kept in step every day rather than a one-off move, that’s a sync, not a migration, and data sync vs data migration explains the difference.

The Part Everyone Forgets

Attachments, documents and free-text notes.

Structured records move cleanly because they map field to field. The eight years of context living in uploaded files and typed notes often has nowhere obvious to go, so it tends to be dealt with last, under time pressure, once the budget is spent.

If that material matters to how the business runs, and it usually does, scope it at the start. It’s often the reason a business feels it can’t leave a system at all.

Migrating Regulated Data

For law firms, financial services firms and anyone else with record-keeping duties, a migration has extra requirements. Retention periods still apply to records in the new system, so the move can’t drop history the regulator expects you to keep. If an audit trail recorded who changed what and when, that trail needs to come across or stay readable. And personal data is being copied, so it falls under UK GDPR: agree in writing beforehand who can see the extracts, where they sit during the move and when the copies get deleted.

None of that changes the method. It adds checks to it, and it means the person signing off the result has to understand the compliance side as well as the data.

What a Safe Migration Looks Like

Profile before planning. Look at the real data and find the problems early.

Trial run into a copy of the target system, checked by people who know what the data should look like, not only by developers.

Reconcile both sides. How many records went in, how many arrived, and a reason for every one that didn’t. Then open a sample of real records and compare them field by field.

Run it again. The first attempt always surfaces something, and successful migrations have usually been rehearsed two or three times.

Keep the old system readable for a period afterwards. It’s cheap, and it’s the difference between an awkward week and a crisis.

The data migration planning guide walks through these stages if you’re running one in-house. There’s also a one-minute video on planning a data migration.

A Migration We’ve Run

When we rebuilt Legmark’s platform in 2026, the hard part was the data. We wrote an importer for that one job, which moved around 1.6 million records across more than 40 kinds of data into a new structure while customers kept using the old system. The database’s integrity checks stayed switched on, so a bad record was rejected as it came in rather than discovered in a customer’s account later. Any run could be stopped and restarted safely, which is what let us rehearse it until the final run was routine. The Legmark case study has the full story.

What You Get

  • A profile of your current data, with the problems listed before a price is agreed
  • A field-by-field mapping document you can check
  • At least one full trial migration into a copy of the new system
  • A reconciliation report covering counts and sampled records
  • A rollback point and an abandon decision agreed in advance
  • The final migration, timed around your working hours
  • Read access to the old data for an agreed period afterwards

What Moves the Price

Data quality comes first, and nobody knows it until somebody looks. After that, whether attachments and notes are in scope, and how different the two data models are. Two systems with the same shape are quick. Reconciling two that disagree about what a customer is takes design work.

Downtime matters too. A migration with a weekend window is a different job from one that has to run alongside live use. So does history: keeping everything is expensive and often unnecessary, and how far back to go is a decision worth making on purpose.

Where Migrations Go Wrong

Most overruns trace back to a price agreed before anyone ran a trial. The next most common failure is verification by record count alone. Matching counts prove nothing about whether the contents are right, and somebody who knows the business has to look at real records.

Then there’s the missing rollback point. There has to be a moment where you decide to abandon and go back, and it should be a decision made in advance, not a surprise on the night. And watch for silent truncation, where fields longer than the destination allows get cut short and nobody notices until a customer does, months later.

Questions to Ask Whoever Quotes for This

  • Have you run a trial import, and what did it find?
  • How will we check the data is right, beyond counting records?
  • What’s the rollback plan, and how long do we have to use it?
  • What are you deliberately not migrating?
  • How long does the old system stay readable?
  • What happens to attachments and notes?

A Brief You Can Send Anyone

  • The system you’re leaving and the one you’re moving to, with versions
  • Roughly how many records, and how far back they go
  • What you already know is messy: duplicates, gaps, inconsistent formats
  • How many attachments and notes there are, and whether they matter
  • How much downtime you can tolerate, in hours, or none
  • The name of the person who can say whether the data looks right
  • What you’re happy to leave behind
  • The deadline, and who set it

How We Run Them

Profile, trial, verify with your people, rehearse, then run with a defined abandon point. The old system stays readable afterwards.

Where the migration is part of moving off an ageing platform rather than a straight system swap, legacy modernisation covers the wider decision, including whether you can get your data out cleanly in the first place.

Get in touch and the first thing we’ll ask for is a sample of the data.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.