+1 480 485 7373
Microsoft Teams
What a Business Central data migration checklist protects you from
Most migration problems are not technical. They come from moving records nobody should have kept, loading data in the wrong order, or going live without proving that the new balances match the old ones. So a checklist forces you to answer those questions while there is still time to act.
Business Central gives several ways to bring data in. There are configuration packages built on Excel templates, and assisted migration tools for some sources, such as the cloud migration from Dynamics GP and NAV. There are also APIs for larger or repeated loads. However, the tool matters less than the discipline of a Business Central data migration checklist around it.
Business Central data cleanup to finish before extracting anything
- ✓Merge duplicate customers and vendors, and agree one naming standard
- ✓Retire items with no stock, no sales and no open orders
- ✓Close or write off stale open invoices and credits on both ledgers
- ✓Reconcile bank accounts and clear old uncleared items
- ✓Correct missing tax details, addresses and payment terms on active records
- ✓Confirm inventory quantities with a count or cycle count close to cutover
- ✓Remove inactive users and retire unused general ledger accounts
- ✓Agree the new chart of accounts and dimension values, mapped from the old codes
- ✓Decide an owner for each data area who will sign off the result
Business Central data migration: what moves, how, and who signs it off
The Business Central data migration load sequence
- 1
Setup data
Posting groups, number series, payment terms, tax areas, locations and dimensions go in first, because every later record refers to them.
- 2
Master records
Load customers, vendors, items, bank accounts and fixed assets, then spot-check a sample against the source.
- 3
Open documents
Bring in open receivables and payables through a clearing account, then open sales and purchase orders.
- 4
Inventory
Post opening quantities and values by location through item journals, matching the final count.
- 5
Ledger balances
Post the opening trial balance so the clearing accounts net to zero and every control account agrees.
- 6
Freeze and confirm
Lock the old system for posting, get owner sign-off on each area, and release users into Business Central.
Four data migration checks after every Business Central load
Trial balance match
The opening trial balance in Business Central equals the closing one in the old system, account by mapped account.
Subledger to control
Customer and vendor totals agree with the receivables and payables control accounts, with clearing accounts at zero.
Inventory value
Quantity times cost by location agrees with the inventory account and the final count sheets.
Record counts
Numbers of active customers, vendors, items and open documents match the extract, with exceptions explained.
Deciding what stays behind
Every migration leaves something in the old system. Deciding that on purpose is part of any Business Central data migration checklist. The usual candidates include old closed transactions from prior years and inactive master records. Others are notes and attachments nobody opens, and custom fields that only supported a workaround Business Central does not need.
Before you leave anything behind, ask three questions of it. Will an auditor, tax authority or lender need to see it, and in what form? Will anyone look it up in daily work, and how often? Also, can people reach it another way, such as a read-only copy of the old database, a reporting store or saved PDFs? If the answers are no, rarely and yes, it can stay behind safely.
Write the decision down with the data owner's name against it. Then, months later, when someone asks where a record went, the note answers the question in seconds and shows the choice was deliberate rather than an oversight.
Retiring the old system after a Business Central data migration
Finally, set a date for retiring the old system completely. Keeping it read-only for a defined period is sensible. However, keeping it running indefinitely means paying for hosting, licences and security patches on software you no longer use. Agree the retention period with finance and audit, export anything required for the long term, and switch it off when that period ends.
Business Central data migration checklist questions
How much history should we move into Business Central?
Most companies move open items, balances and sometimes monthly totals, not every past transaction. Detailed history adds mapping, loading and reconciliation work. Yet people rarely look at it once the new system is live. Keeping the old system available read-only, or exporting history to a reporting database, usually covers audit and lookup needs. We help you choose based on what people really use.
How many practice loads should we run?
Run at least two full practice loads, each followed by reconciliation. The first finds mapping errors and data gaps. The second proves the fixes and times the process. Complex migrations with several sources may need more rounds.
Who should clean the data, us or the partner?
Your team should own cleanup, with the partner providing tools, templates and guidance. After all, only your people know which customers are duplicates, which items you have retired and which open invoices are real. A partner can run reports that find likely problems and load the corrected data. Starting cleanup early is the single biggest help to the schedule.
More Business Central data migration questions
What tools does Business Central provide for migration?
Business Central offers configuration packages, assisted migration tools and APIs. Configuration packages use Excel templates for most master data and open items. The cloud migration tool supports some Microsoft sources such as Dynamics GP and NAV. APIs suit large volumes or loads that repeat during a phased rollout.
What are the most common migration mistakes?
Loading data in the wrong order, skipping reconciliation and bringing over dirty master data are the most common. Others include forgetting open purchase orders, mismatched tax setup on customers, and inventory counts taken too early. Each one shows up as a problem in the first month end. A Business Central data migration checklist with named owners catches them before cutover.
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.