Data & intelligence

Data migration

Source profiling, mapping, reconciliation and cutover planning.

Capability in business terms

Why this capability matters

A migration is finished when the destination reconciles and the business can operate — not when the data has moved.

What we typically scope

Source profiling, mapping, transformation, reconciliation, cutover planning and rollback.

How we approach the work

Agree the acceptance test and the rollback before moving a single record.

Work we take on

Example engagement — illustrative. Typical scopes of work, not named client case studies.

Legacy ERP to a new platform

Why it happens
Twelve years of master and transactional data must move, and finance will not sign off on approximations.
How we work it
Profile sources for completeness and duplication, agree what will not migrate and why, build reconciliation as a first-class deliverable, run repeatable mock cutovers, define the rollback trigger and window.
What you end up with
Reconciliation reports finance signs, a rehearsed cutover, and a rollback path that has been tested rather than assumed.

Merging two companies' customer data

Why it happens
Post-acquisition, two CRMs hold overlapping customers with conflicting truth.
How we work it
Define matching rules with the business, not just fuzzy logic; establish survivorship rules field by field; retain both source records with lineage; stage the merge with a review queue for ambiguous matches.
What you end up with
A merged master with documented survivorship, full lineage back to both sources, and a human review path for the cases the rules can't decide.

Getting off a database that is going end of life

Why it happens
A database version reaches end of support in nine months and the applications on it are poorly documented.
How we work it
Instrument access to discover real consumers, catalogue stored procedures and jobs, test compatibility, sequence the migration by dependency, run parallel where the risk justifies it.
What you end up with
A dependency-ordered migration plan with a dated critical path, and consumers discovered by observation rather than by outage.

Archiving what should not be migrated

Why it happens
The migration scope has grown because nobody will authorise deleting anything.
How we work it
Map retention obligations by data category, define an accessible archive rather than a live migration, get written sign-off on the archive-versus-migrate split, reduce the migration scope accordingly.
What you end up with
A defensible retention position, a smaller and cheaper migration, and archived data that is still retrievable when asked for.

A migration that failed and has to be restarted

Why it happens
A previous attempt was abandoned mid-flight, leaving partial data in the target and low confidence everywhere.
How we work it
Reconcile target against source to find what actually landed, assess whether to clean forward or reset, document what went wrong and why, rebuild the plan with acceptance criteria the business defines.
What you end up with
A written statement of actual current state, a recommendation with reasoning, and acceptance criteria agreed before restart.

Related business solutions

Ways to engage

How we approach the work

Understand the estate

Map dependencies, constraints, decision owners and the current operating model.

Make the decision explicit

Record options, risks, costs and acceptance criteria before implementation.

Make the handover usable

Document changes, operating instructions and the remaining risks.

Delivery is subject to specialist fit and availability.

Start with clarity.

What would make your business easier to run?

Tell us the operational challenge. We will discuss whether a short conversation, a scoped assessment or a delivery engagement is the right next step.