ERP data migration playbook

The hardest part of switching ERPs isn't the new system, it's the data. Most of the work happens before anything is moved.

ERP data migration playbook

Data migration sounds like a technical task: export, transform, import. In practice most of the effort goes into decisions. What stays, what gets archived, which of three customer records is the real one, how old accounts map to new ones. Projects that budget migration as "a couple of scripts at the end" are the ones that run late.

ERP data migration playbook
Migration funnel — most work happens before the actual move.

Before migration: decide and clean

  • Customer and supplier deduplication. "ACME Corp", "Acme Inc." and "ACME LLC": one company or three? Resolve by tax ID or registration number where you have it, manually where you don't.
  • Item normalization. Trailing spaces, mixed case, several units of measure for the same item, discontinued SKUs still marked active. Clean before the move, not after.
  • Cutover strategy. Don't migrate years of closed transactions. The usual approach is opening balances at the cutover date plus open documents, and current-period activity if reporting needs it.
  • Chart of accounts mapping. The old and new charts of accounts never map one to one. Build an explicit translation table and have the accountant sign it off.
  • Hidden references. Custom fields, attached files, audit trails, notes on records. Find them and decide what happens to each before you start, not when someone asks for them in production.

Decide what not to migrate

The new system doesn't need your whole history. Typically you move master data that's still in use, opening balances, open documents (unpaid invoices, open sales and purchase orders) and whatever the current period's reporting requires. Closed historical transactions, inactive items and old contacts stay behind.

"Stay behind" doesn't mean "disappear". Keep the old system available read-only, or export its data into a simple reporting database, so auditors and accountants can still look things up. That's usually far cheaper than forcing ten years of history into a new data model.

How to run the migration

  1. Write a mapping spec. A table with source field, target field, transformation rule and owner. It becomes the contract between the business and whoever writes the scripts.
  2. Script everything. The migration must be repeatable from scratch. No manual fixes in the target system: fix the source data or the script, then run again.
  3. Do several trial loads. Load into a test environment, let business users check their own data, collect issues, repeat.
  4. Reconcile totals. Receivables, payables, stock quantities and value, account balances. They must match to the cent, or every difference must be explained in writing.
  5. Rehearse the cutover. Freeze window, final extract, load, reconciliation, sign-off. Time the rehearsal so you know how long the real weekend will take.
  6. Run in parallel. Keep both systems running through at least one full closing period and compare outputs. Even a well-tested migration surfaces issues that trial loads didn't show.

What breaks migrations in production

  • Implicit logic in the old system (database triggers, custom code, validations) that nobody documented, so the new system silently behaves differently.
  • Decimal precision differences: the old system rounds to four places, the new one to two, and the pennies pile up across thousands of lines.
  • Exchange rates at the migration date. Even small differences move balances in foreign-currency accounts.
  • Documents such as purchase orders and invoices arriving without their original PDF attachments.
  • Encodings and special characters in names and addresses that get mangled on export.
  • Dates and time zones, especially for documents created around midnight or at period end.

Checklist

  • Deduplication rules agreed and applied to customers, suppliers and items.
  • Cutover date and scope defined: what moves, what is archived.
  • Mapping spec complete, with an owner for each entity.
  • Migration scripts repeatable end to end.
  • Reconciliation report template ready before the first trial load.
  • Read-only access to the old data planned for after go-live.

Migration is one of the phases that decides whether an ERP timeline holds; see also ERP implementation in 90 days. When the target isn't an off-the-shelf ERP but a custom system, the same playbook applies, and it's part of how we approach custom web application projects that replace legacy tools.

Planning a migration and want someone to review the plan? Message us on Telegram or MAX.

Custom CRM development
Related service — let's discuss your project.

Got a project on this topic? Tell us the task — we'll come back with an estimate and a schedule.

Message on Telegram → Message on MAX