Business Central

Business Central Migration Checklist

A safe Business Central migration needs five things verified before cutover: clean master data, a signed-off chart of accounts and dimension design.

Reviewed 2026-08-24 by the Machina IT engineering team.

The short answer

A safe Business Central migration needs five things verified before cutover: clean master data, a signed-off chart of accounts and dimension design, a reconciled sandbox month-end close, rebuilt reporting on live data, and a rehearsed cutover plan with a data freeze and named owners. Skipping any one of them is what turns a scheduled go-live into a recovery project.

Before configuration begins

Written process maps for quote to cash, purchase to pay and production
Decision on which processes change at go-live
Chart of accounts and dimension design signed off by finance
Inventory of every integration and report, marked keep, replace or retire
Agreement on how many historical years migrate

Master data readiness

Items de-duplicated with standardized numbering and units of measure
Customers and vendors de-duplicated with validated tax setup
BOMs and routings validated against actual production
Costing method assigned per item category
Opening inventory quantities physically counted, not assumed

Verification gates

Scripted end-to-end tests using real documents
Sandbox month-end close reconciled to the legacy system
Negative-path testing: returns, scrap, credit holds, partial shipments
Power BI or financial reports rebuilt and matching known numbers
Permission sets tested per role, including approval limits

Cutover mechanics

Period-boundary date with a documented freeze window
Verified opening balances and open document load
Reconciliation sign-off before transacting
Named owner per workstream during the freeze
Rollback criteria defined in advance, in writing

First thirty days

On-floor support at shipping, receiving and production posting
Daily reconciliation of inventory movements for the first two weeks
Ticket triage path for ERP-specific issues
License assignment review once real usage is visible
Backlog review of deferred requests, prioritized against business impact

Common mistakes

What goes wrong most often.

Cutting over mid-period
Loading opening inventory without a physical count
No documented rollback criteria
Reporting rebuilt after go-live rather than before

Common questions

Straight answers, no sales theater.

How much history should we bring?

Balances plus one to two years of transactional detail suits most companies. Keep the legacy system read-only or archive it for older years — migrating everything adds cost and risk with little operational value.

Do we need a parallel run?

A reconciled sandbox month-end close plus scripted end-to-end testing usually substitutes for a full parallel run at mid-market scale, and costs far less in staff time.

What is the biggest cause of overrun?

Master data quality, followed by integration count. Neither is discovered late in projects that inventory both before configuration starts.

Business Central Consulting

Cloud Migration

Manufacturing ERP

Schedule an IT assessment.

We review your network, security posture, cloud tenant and recovery plan, then hand you a plain-language report of what we found and what it means for the business.

Schedule an IT Assessment Talk to an IT Expert · (866) 980-1553