A Practical Guide to Business Central Migration

A Business Central migration looks simple on a slide and gets complicated the moment you open your actual data. The difference between a smooth go-live and a painful one is usually the preparation, not the software.

This guide walks through what a migration involves, in the order you will meet it, so you can plan yours with your eyes open.

Key PointPlan data cleansing and integrations from the first week, alongside configuration, not after it.

When is it time to migrate?

The move usually starts when the current system has become the bottleneck. Common signals:

• month-end depends on spreadsheets bolted onto the accounts package;
• you have outgrown an entry-level system such as QuickBooks or Sage 50;
• stock, projects and finance do not share data;
• you are on an old version of Dynamics NAV.

Know your route

Microsoft's guide to migrating data to Business Central online sets the path by starting point. From Dynamics NAV, you upgrade to Business Central on-premises first and then switch online. For QuickBooks, Microsoft provides migration apps.

For other sources, Business Central includes templates and configuration packages for importing accounts, customers, vendors and items. Our Sage 50 migration guide covers that route.

Four workstreams, not one

A migration is really four pieces of work running in parallel:

• Data. Master data and a chosen amount of history. Consider bringing open items and balances rather than every closed transaction.
• Configuration. Number series, posting groups, dimensions, VAT setup, approvals and permissions, designed around how you work.
• Extensions and integrations. Payroll, e-commerce, CRM, bank feeds and reporting tools. Each one is a small project with its own testing.
• People. Role-based training, a cutover plan and a named person to answer questions in the first weeks.

Pro TipClean duplicate customers, suppliers and items in the old system before you move them.

How much history to bring

Bringing every closed transaction multiplies reconciliation work. One option is to migrate balances and open items, and keep the old system available for look-ups.

Whatever you decide, plan how older records stay available. GOV.UK says a company must keep records for 6 years from the end of the last financial year they relate to. Our data migration process guide goes through each data type.

The phases

• Discovery: map processes, data and integrations, and agree scope.
• Design and configure: build the environment around how you work.
• Migrate and test: load data into a sandbox environment and reconcile it against the old system.
• User acceptance testing: your team runs real transactions end to end and signs them off.
• Cutover and go-live: a final load and a clean switch-over date, usually a period end.
• Support after go-live: a set window to catch edge cases quickly.

Watch OutReconcile the migrated balances against the old system before go-live, not after.

Common pitfalls

• Too much history. Take balances and open items; archive the rest.
• Treating it as an IT project. Finance and operations own the outcome.
• Skipping proper testing. A demo is not the same as your team running a real payment run.
• Going live mid-period. Cut over at a period end so opening figures are clean.
• Leaving integrations to the end. Start them early.

How long and what it costs

Time and cost depend on your data, integrations and how many bespoke processes you need. With BC Fast-Start, Amplio takes a business live on Business Central in twelve weeks for £4,500 fixed, for a standard scope.

If Sage is your starting point, read our guide to moving from Sage to Business Central. For independent guidance, see the ICAEW technology resources, or talk to our Business Central team.