Business Central Data Migration Process Guide

The data migration is the part of a Business Central move that finance teams worry about most, and rightly so. Getting master data, open transactions and balances in accurately is what lets you trust your first reports.

This guide walks through the process step by step, in the order we recommend.

Key PointExtract, cleanse, map, load, reconcile - then do it all again for go-live.

What the process involves

At its heart the process is extract, cleanse, map, load and reconcile. You pull data from your current system, tidy it, map it to Business Central, load it into a test environment and check every balance.

Then you repeat the run for go-live. Each stage has its own pitfalls, and the cleanse is the one most worth not rushing.

Step 1: extract and profile your data

Export your customers, suppliers, items, chart of accounts and open entries. Then profile them for duplicates, blank fields, inconsistent codes and dormant records.

Decide what not to migrate as carefully as what to keep. Inactive customers and obsolete items add noise without adding value.

Step 2: cleanse and standardise

Fix what profiling reveals before you go near Business Central. Standardise names, complete fields such as VAT registration numbers and payment terms, and agree one format for codes.

Clean data loads faster, validates more easily and gives your team a system it can rely on from day one.

Pro TipFix the data in the old system, where people know it, rather than in Business Central after go-live.

Step 3: map to Business Central

Map each source field to its Business Central equivalent, with most care on the chart of accounts, posting groups and dimensions.

Dimensions deserve thought. Microsoft explains that, instead of setting up separate general ledger accounts for each department and project, you can use dimensions as the basis for analysis, so a long segmented chart of accounts often gets shorter.

Step 4: load into a test environment

Business Central includes templates for accounts, customers, vendors and inventory items that you can apply when you import data from Excel. For larger work, configuration packages handle the rest.

Load into a sandbox environment before you touch production, so mapping errors are caught safely. Plan at least two full rehearsals.

If you are moving from Dynamics NAV, GP or another SQL system, Microsoft's cloud migration guide sets out the route for each. Coming from Sage 50? Our Sage 50 migration guide covers that route.

Step 5: reconcile and sign off

Compare trial balances, aged debtors and creditors, stock valuations and VAT figures against the old system. Nothing goes live until finance signs off that the numbers match.

Check VAT across the change too. GOV.UK says all VAT-registered businesses should now be signed up for Making Tax Digital for VAT, so plan your first return from Business Central before go-live.

Watch OutNothing goes live until finance has signed off that the balances match the old system.

Get the sequence right

Load master data first, then opening balances, then open transactions. Keep live history to what you need, and keep the rest where you can still reach it.

GOV.UK says a limited company must keep its company and accounting records for 6 years from the end of the last financial year they relate to, so plan where older history will live. The ICAEW technology resources are a useful independent reference.

For the bigger picture, read our Business Central migration strategy guide and our practical guide to Business Central migration. If your business already holds Business Central licences but has not gone live, our BC Fast-Start includes data migration in a twelve-week, £4,500 fixed-price route to go-live.