+1 480 485 7373
Microsoft Teams
Each old system leaves a different mess when you migrate to Business Central
A company coming off Dynamics NAV usually has years of clean, structured data. It also has a layer of custom code written in C/AL. The data can travel, but much of the code should not. Current Business Central often covers what those changes set out to do. Dynamics GP and SL bring their own account segment structures. You translate these into a chart of accounts and dimensions, not copy them field for field.
QuickBooks, Sage and Xero customers face a different problem. Their data is simpler, but people often entered it with less discipline. Think duplicate vendors, items that are really services, and customers stored under three spellings. Spreadsheet businesses have the least to move and the most to design. Business Central will ask about posting groups and costing methods that nobody has had to answer before.
Separate pages for each source system are on the way. The principles below apply to all of them.
What normally comes across to Business Central and what stays behind
Opening balances in Business Central versus bringing the history
Balances only
The fastest and cleanest option. We load the trial balance at cutover, open receivables and payables, and stock on hand. Everything older stays in the old system or an export. Auditors are generally comfortable with this when the old data remains readable.
Summarized history
We post net change per account per month for the current and previous fiscal year. So year-over-year reports work inside Business Central from day one, without the weight of every transaction.
Full transaction history
Possible from some sources, especially GP and NAV through Microsoft's cloud migration tool, which can bring historical detail across. It increases testing effort, and the value falls off quickly for anything older than a couple of years.
Read-only archive
Whatever does not move still needs a home. It can be the old system on a reduced license, a reporting database, or searchable structured exports. When you migrate to Business Central, we settle this before the cutover date, not after.
From the old books to the first live posting in Business Central
- 1
Inventory the data
Count what exists in the source: record volumes, open items, custom fields and integrations. This is where surprises such as a second, forgotten company or a payroll feed usually appear.
- 2
Clean before moving
Merge duplicates, mark dead records inactive and standardize codes, either in the old system or in the staging workbook. Cleaning after go-live costs more and confuses users.
- 3
Map and load into a Business Central sandbox
We map fields to Business Central tables and load them with configuration packages, the cloud migration tool or both. A sandbox takes the first loads so mistakes cost nothing.
- 4
Reconcile trial loads
We compare balances, aged receivables, aged payables and inventory valuation line by line against the source. Nobody signs off until the numbers tie.
- 5
Parallel run where it matters
For payroll-linked or high-volume processes, we run a period in both systems and compare the results. For simpler businesses a careful dress rehearsal of the cutover is often enough.
- 6
Cutover
We freeze the old system and load final balances and open documents. Then the first transactions post in Business Central, and the archive plan takes effect.
Traps that slow a move to Business Central
- ✓Treating the migration as a copy job instead of a chance to fix the chart of accounts.
- ✓Leaving vendor bank details and tax IDs unverified until the first payment run.
- ✓Loading inventory without agreeing the costing method first, which is hard to change once items have posted entries.
- ✓Forgetting integrations such as ecommerce, EDI, payroll or banking that quietly read from the old system.
- ✓Choosing a cutover date in the middle of a quarter-end close or a peak sales week.
- ✓Skipping a trial migration, so data errors surface for the first time on the cutover weekend.
Questions from companies planning to migrate to Business Central
Can we migrate to Business Central in the middle of our fiscal year?
Yes. Many companies go live at a month end rather than a year end. The trial balance at that month end becomes the opening position. You can also post summarized net change for earlier months, so year-to-date reports still work. Year end is tidier, but you do not have to wait for it.
Does Microsoft provide tools for moving our data?
Yes. Microsoft includes a cloud migration tool in Business Central online for Dynamics GP and on-premises Business Central databases. It has also added routes for older products over recent releases. For NAV, the path depends on the version you run. For QuickBooks, Sage, Xero and spreadsheets, configuration packages and Excel templates are the usual method.
What happens to our NAV customizations?
We review each one. Current standard features often cover a good share of them, so you simply drop those. We rebuild the rest as AL extensions, the only way to customize Business Central online. Those extensions then survive Microsoft updates.
How much history should we bring across?
Usually less than people expect. Open items and balances are essential; one or two years of summarized history covers most comparative reporting. Keep detailed older transactions in a searchable archive instead. That keeps the new system fast and the testing effort reasonable.
Who does the data cleanup?
It is shared. We provide the templates, the rules and the checks that find duplicates and gaps. Your team decides which customer record is the right one and which items you still sell. Nobody outside your business can make those calls reliably.
Migration guides by the system you are leaving
Migrations by system →
Every Business Central migration path on one page, grouped into accounting packages and ERP systems, with guides for GP, NAV and data cleanup.
Dynamics GP migration →
Dynamics GP to Business Central using Microsoft's cloud migration, plus the posting groups, reports and ISV products it leaves to you.
QuickBooks migration →
Move from QuickBooks Online or Desktop to Business Central with clean master data, open items and balances that tie out.
Dynamics NAV migration →
Dynamics NAV to Business Central by technical upgrade or fresh start, with C/AL modifications sorted into keep, replace and retire.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.