How to migrate data to Business Central without downtime

Data migration is where quiet problems become loud. You can configure a system perfectly, but if dirty balances and duplicate customers drive into it, the team's trust in the new ERP disappears in the first week. The good news: migration can be made predictable.

The main principle: move less than you want to

The temptation to “bring 10 years of history” is almost always a mistake. Historical transactions are rarely needed in day-to-day work — keeping them in an archive is enough. Mostly open balances and master data enter the new system, not your entire past ledger.

What to migrate

• Master data: customers, vendors, items, chart of accounts.
• Open documents: unclosed orders, invoices, debts.
• Balances: inventory, cash, settlements as of the switch date.
• As much history as you truly need for reporting — no more.

Four migration stages

1. Audit and cleanup

First we look at what's actually in the old system. Duplicates, empty fields, incorrect codes — all fixed before the transfer. Cleaning data in the new system is far more expensive.

2. Mapping

Every field in the old system gets a counterpart in Business Central. This is where you decide how old codes, units of measure and categories map onto the new structure.

3. Test load

Data is loaded into a test environment and the team reconciles: do balances match, are debts correct, is everything in place. This step repeats until the numbers agree.

4. Final load

Done over a weekend or a low-activity period. By go-live the real data has already been validated on the test, so there are no surprises.

The most common mistake

Underestimating data cleanup. Teams often assume “the data is fine” until they see it laid out in a structured form. Reserve dedicated time for audit and cleanup in the plan — it's the cheapest insurance against post go-live chaos.