Mon – Sat: 9:00 AM – 7:00 PM IST
Implementation

What is data migration in ERP?

Moving master and transactional data into a new system — the phase that delays more go-lives than any other.

In short

Data migration is the extraction, cleansing, mapping, loading and reconciliation of data from legacy systems into the new ERP. Master data — customers, suppliers, items, accounts — moves first; balances and open transactions follow at cutover. Historical transactions are a decision, not an obligation.

Why It Matters

Why this matters in practice

Migration delays go-lives more than configuration does, for a reason that is structural: the cleansing is the client's work and cannot be outsourced. Only your people know whether two similar customer records are the same company. That work competes with their day jobs, which is why it has to start in the first month rather than the last.

Master data first, balances and open items at cutover
Cleansing is the client's work and the long pole
Multiple rehearsals, not one attempt
Reconciliation proves the load, completion does not
How It Works

How it works in practice

1

Profile the source

What exists, how much of it, how dirty it is. Duplicate rates and missing mandatory fields are the useful measures.

2

Decide scope

What migrates and what does not. Carrying ten years of transactions is expensive and rarely used — decide deliberately.

3

Map fields

Legacy to target, with transformation rules written down. Ambiguities surface here and are cheap to resolve.

4

Cleanse and rehearse

Load into a test environment, read the errors, fix at source, repeat. Three or more full rehearsals is normal.

5

Reconcile

Record counts and control totals against source. A load that completed is not a load that is correct.

Worked example

A worked example: what to bring and what to leave

A business with eleven years of history in its legacy system assumes it must migrate all of it. That assumption, unexamined, is often the single largest cost in the project.

A more useful division is by what the new system actually needs to operate. Open items are mandatory: outstanding receivables and payables, open orders, current stock, active master data. Reference history is usually worth one to two years of closed transactions, so users can look up a recent invoice without leaving the system. Everything older is archive — needed for statutory retention and occasional lookup, but not needed inside the new ERP.

Keeping the legacy system available read-only for a defined period, or extracting the archive to a queryable store, satisfies retention at a fraction of the cost of migrating and reconciling eleven years of transactions into a different data model. The conversation to have early is which of the three buckets each data set falls into, because 'migrate everything' is a decision that nobody actually made — it is what happens when the decision is deferred.

Key terms

The vocabulary, briefly

Term What it means
Extract Pulling data from the legacy system, in a repeatable scripted way rather than by hand.
Transform Mapping and cleansing to fit the target structure.
Load Importing into the new system, usually through a supported bulk mechanism.
Reconciliation Proving what loaded matches what was extracted, by count and by value.
Cut-off The point at which legacy data is frozen for the final extract.
What Goes Wrong

Common mistakes worth avoiding

Starting cleansing late

It is the single most reliable predictor of a delayed go-live.

Migrating everything by default

History has a cost and usually little use. Archive it accessibly instead of loading it.

No reconciliation

Opening balances that do not tie to the legacy system make the first close impossible to sign off.

One rehearsal

Each pass surfaces problems the previous one masked. Plan for several.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Records extracted vs loaded vs reconciled The three-way check. Gaps between any pair mean something was lost silently.
Duplicate master records Measured before migration. The number that justifies cleansing effort.
Rehearsal elapsed time The input to the cutover plan, knowable only by rehearsing fully.
Post-load reconciliation variance Control totals against source. The only real proof it worked.
FAQ

Questions we are asked about this

Usually open items and balances, plus enough closed history for comparison — often one to two years. Keep the rest accessible in an archive rather than loading it.
Your team, with tooling and reports from the implementer. Only the business knows which duplicate is the real customer, and that judgement cannot be delegated.
Your people, because they are the only ones who know whether two similar customer records are the same organisation or which of three addresses is current. Implementers can supply tooling, duplicate detection and structure, but the judgement is yours. This is the single most common planning failure: a project assumes cleansing is part of the implementer's scope, and the implementer assumes it is the client's. Name the owner explicitly in the plan.
At least two full ones, three if the cutover window is tight or the volume is large. A rehearsal means the complete sequence end to end — extract, transform, load, reconcile — in a realistic environment, timed. Partial rehearsals of individual objects hide the dependency and sequencing problems that cause real cutovers to overrun, which are exactly the problems rehearsal exists to find.
They need an explicit rule each: partially received purchase orders, partially shipped sales orders, works orders mid-production, partially paid invoices. Decide whether each is closed in the legacy system and re-created, or migrated in its partial state. There is no universally right answer — it depends on volume and on how your new system models the partial state — but there is a universally wrong one, which is deciding during cutover.
Reconcile on both count and value, by object, against control totals agreed with finance before the load. Then have business users verify a sample of real records end to end — this customer, this order, this stock balance — rather than only checking totals. Totals can match while individual records are wrong in offsetting ways, and the first person to find that should not be a customer.
Related

Where to read next

ERP implementation phases

Read more

FBDI and HDL data loading

Read more

What is UAT?

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.