A migration checklist for Business Central, from first extract to cutover

Start the migration checklist with scope

Write down what moves and what stays behind. Master data such as customers, vendors, items and the chart of accounts nearly always moves. Open transactions move as open items. Closed history is a choice. Many companies bring balances and summary figures, and keep the old system available to read.

Agree the cutover date, who owns each data set and how people will reach the old system afterwards. Find out how long records must be kept for tax and audit in your situation. Then make sure the archive plan covers it. These decisions shape everything that follows on the list.

Clean data first on the Business Central migration checklist

Migration moves whatever you give it, including the mess. Before extracting anything, merge duplicate customers and vendors. Block or drop records that nobody uses. Correct addresses and tax identifiers. Settle old unapplied payments and credits, so open items are truly open.

Inventory needs the same attention. Look for obsolete items, wrong units of measure, negative stock and costs that nobody trusts. A physical count close to cutover gives quantities you can stand behind. Cleanup belongs to your team, not the consultant. Only the people who use the data know which record is right.

Mapping on the Business Central migration checklist

Old and new rarely match field for field. Decide the new chart of accounts and dimensions first. Long segmented account numbers usually become a shorter account plus dimension values. Then map payment terms, posting groups, units of measure, tax setup and item categories from old codes to new.

Choose the tool for each source. Dynamics GP and older NAV or on-premises Business Central databases can use the cloud migration tool, set up from inside Business Central online. QuickBooks has its own assisted migration for core lists. Everything else typically goes through configuration packages and journals prepared in Excel.

Trial loads on the Business Central migration checklist

Run the full migration into a sandbox more than once. The first trial finds structural problems, such as rejected records, missing codes and wrong mappings. Later trials time the process and confirm the fixes. Keep a log of every error and its resolution. Then the final run holds no surprises.

After each trial, reconcile. Record counts should match the source. The trial balance, aged receivables, aged payables and inventory value should agree with the old system at the same date. Let key users open records they know well. People spot a wrong credit limit or price faster than any report.

Cutover and the first checks on the migration checklist

On cutover, stop entry in the old system and take the final extracts. Run the loads in the rehearsed order and reconcile before anyone is let in. Get written sign-off on the balances from finance. Set the old system to read-only, so nobody keeps working in it out of habit.

The first days deserve their own short list. Post a sales invoice and a purchase invoice, run a payment, import a bank statement and ship an order. Confirm each integration and print the documents customers see. Problems found then are small. Found at the first month-end, they are larger and harder to unpick.

Questions about the Business Central migration checklist

Can transaction history be migrated in full?

Sometimes, depending on the source. The cloud migration tool can bring historical data from Dynamics GP and NAV. Other systems usually bring balances and open items only. More history means more cleanup and testing. So decide what people will really look up, and migrate that. Everything else can stay in the archive of the old system.

How many trial migrations are enough?

Enough that the last one runs with no new errors and reconciles without adjustment. For a simple company that may be two rounds. With several entities, large item lists or complicated open transactions, plan further rounds. Do not shortcut the reconciliation. It is the part of the Business Central migration checklist that protects your books. Keep a short log beside the Business Central migration checklist.

Do we have to change our chart of accounts?

No, but migration is the natural moment to simplify it. Segmented account numbers from older systems translate well into a lean chart with dimensions for department, location or project. That makes reporting in Business Central far more flexible. So check the chart first, and migrate the new structure, not the old one.

What happens to our old system after the move?

Keep it in read-only form for as long as your record-keeping obligations and your auditors require. Some companies keep a single license or a database backup with a reporting tool. Decide this before cutover, so access does not lapse by accident. Write the plan into the checklist, with an owner for it.

Who signs off the migrated data?

The business signs, not the consultant. Finance signs the trial balance and open items, operations signs stock, and each process owner signs their master data. We prepare the reconciliation reports and explain differences. Ownership of the figures stays with you. So name each signer before the first trial load runs.

Related pages for your Business Central migration checklist

The Business Central migration checklist is the short form. These pages go deeper into migration services by source system and the longer migration guide. They also cover the opening balance and package tools used along the way. Read the migration guide next. Then match each stage here to a task, an owner and a date in your own project plan. For the product detail, see Migrate on-premises data to Business Central online, on Microsoft Learn.