Reconciliation-First Data Migration Into Business Central
A reconciliation-first guide to Business Central data migration: set the cutover date, carry balances and open items, prove each account before go-live.

AI-generated header image for: Reconciliation-First Data Migration Into Business Central
Moving from NAV to Business Central is not a version upgrade with a bigger database. A legacy NAV environment often carries years of financial history, modified posting routines, custom tables, reports, add-ons, and integrations, so data migration becomes a reconciliation exercise, not a copy-and-paste job. If your measure of success is the number of records loaded, you can still go live with an opening balance sheet that no accountant or auditor will trust. The real test is simpler and stricter: your first post-go-live close must match your last pre-go-live close, account by account.
This how-to guide walks intermediate Business Central practitioners through a reconciliation-first data migration. You will start with the prerequisites, then define the cutover point before mapping fields, map legacy fields without losing meaning, carry forward balances and open items instead of closed years, land every open item line by line, and run parallel controls until each account reconciles. We also cover what auditors look for in migrated opening balances, when to sign off and retire the legacy system, how to choose a migration tool category, and the pitfalls that break opening balances after go-live. The takeaway is clear: reconcile first, switch off second.
Why Record Count Is the Wrong Success Metric for ERP System Migration
A data migration succeeds when your first post-go-live month-end close reproduces the last pre-go-live close, account by account. Not when the row count leaving the legacy system matches the row count arriving in Business Central. Those are two different tests, and only one of them is the one finance signs.
The trap is quiet. A migration moves hundreds of thousands of rows, the load log reports success, and the balances tie out to nothing. What you have then is a new set of books with no audit trail behind it. The cost does not appear on go-live day; it appears weeks later, at the first close, when someone must explain why the receivables control account is off by an amount nobody can trace to a document. In practice, most legacy ERP migrations fail before go-live, when data debt goes unmapped, not at the switch itself.
Technical scope is real, but it is not the criterion. A NAV to Business Central move carries custom tables, modified posting routines, C/AL-era logic, add-ons and integrations, all of which widen field mapping and testing effort. None of that is what the controller, the auditor or the finance workstream lead accepts at sign-off. They accept balances that reconcile.
Ownership sits with finance as much as with IT. Accountants, financial controllers, auditors and the ERP project lead on the finance workstream define the reconciliation target. The technical team executes against it.
Reconciliation-first also reorders the project. Fix the cutover point, the reconciliation target and the sign-off criteria first. Only then evaluate which data migration tools to use, because a loader that moves rows quickly still produces no reconciliation on its own.
Prerequisites: What Must Be True Before You Move a Single Record
Before any extract runs, five conditions must hold. Treat them as gates, not recommendations.
A frozen, balanced legacy trial balance. Freeze the legacy ledger at the cutover point and produce a trial balance the controller reviews and signs, rather than an export assumed correct. The audit benchmark here is explicit: ISA 510 requires sufficient appropriate evidence that opening balances do not contain misstatements that materially affect the current period. Your migrated opening position is that same brought-forward baseline, so it needs the same review discipline.
Mapping decisions in writing. Chart of accounts, dimensions and posting groups must be agreed and documented before load: segment, cost center, department and project mappings, plus every account consolidation or split, each with a bridge rule that explains the difference.
Confirmed fiscal period and posting date setup. Business Central fiscal periods, posting date ranges and allowed posting windows must be configured first, including entities running different closing calendars across Lebanon and KSA operations. The Business Central implementation FAQ covers how this setup is typically scoped.
Open-item registers as at the cutover point. Extract document number, date, currency, remaining amount and aging for every open receivable, payable, bank and inventory item. Without this, the load has no reconcilable target, only a total.
Ownership, freeze and rollback. Name an owner per reconciliation account, publish the migration freeze window to finance and the implementation team, and define the rollback point that triggers if opening balances fail validation.
With these in place, the cutover point becomes a signed decision instead of an assumption.
Step 1: Fix the Cutover Point Before You Map Anything
With the trial balance frozen and mapping decisions signed, the next decision is not which fields to map. It is the date the legacy system stops accepting postings.
Define the Cutover Point as a Signed Date
The cutover point is the last day of a closed legacy period. After it, no journals, corrections, or subledger postings are accepted in the old system. Every downstream choice, the reconciliation target, the opening balances, the subledger extracts, is measured from this date, so it must be signed by the controller, not suggested by the project team. Choose a month end: the legacy system has already closed that period under its own posting controls, so the trial balance you reconcile is one its own users could not alter.
Resolve Transactions In Flight
Document what is mid-process at the boundary: goods received not invoiced, unposted journals, unapplied payments, unapproved purchase orders, and part-completed projects. For each, state whether it closes in the legacy system, carries into Business Central, or is reversed and re-entered. Undocumented in-flight items are the most common source of day-one differences.
Choose the Cutover Shape for Multi-Entity Groups
Entities cut over together or in waves. Staggered cutovers require intercompany balances to tie at every boundary, not only the final one, multiplying reconciliation work but limiting blast radius. A single simultaneous cutover simplifies intercompany matching and concentrates risk into one window.
Publish the Decision to Both Teams
Issue the freeze start date, cutover date, named owner, and fallback date to finance and the ERP implementation team. The fallback matters: if reconciliation is not ready, the team needs an agreed second window, not an improvised delay. Framing that decision as a cost question rather than a technical one is covered in When Your Legacy ERP Costs More to Keep Than to Replace.
Step 2: Map Legacy Fields to Business Central Without Losing Meaning
With the cutover date signed, mapping is the next control point. Legacy field mapping runs on three levels at once: general ledger account to account, legacy dimension or analysis codes to Business Central dimensions and dimension values, and legacy subledger document types to their Business Central equivalents. Mapping only the GL leaves subledger detail stranded.
Resolve the Chart of Accounts First
Settle the new chart of accounts before loading a single balance. A consolidation from 400 legacy accounts to 180 is a design decision, and every merge needs a written bridge rule: which legacy accounts feed which target, on what logic. Without it, the reconciliation cannot explain the difference.
Test for Silent Breakage Before Load Day
Three failure modes rarely surface until the load errors out or, worse, posts wrong:
Legacy account numbers stored as text may exceed Business Central field lengths or lose leading zeros.
Currency decimal handling differs between systems; verify rounding and amount field precision.
Date formats must parse correctly, or items land in the wrong period.
Validate each against field length and posting group requirements first.
Map Posting Groups Deliberately
General business, customer and vendor posting groups decide where the entry lands. Balances loaded into the wrong group can tie at the trial balance total while failing at the subledger level, surfacing later as an unreconcilable control account. Treat posting group assignment as a mapping column, not an afterthought. If the team is still framing what Business Central is, the difference between Microsoft 365 and Dynamics 365 Business Central covers the ground.
Keep the Mapping Workbook Auditable
Record legacy value, target value, rule, owner and status for every row. This workbook is an audit artefact, and typically the first document auditors request.
Step 3: Carry Forward Balances and Open Items, Not Closed Years
With the mapping workbook signed off, the next decision is what actually crosses the line.
Adopt the rule: migrate the opening balance, archive the history. Closed years belong in the legacy system as a read-only reference, never reloaded into Business Central. Reloading history buys no reconciliation benefit and inflates the data migration effort.
Move only what is still live at the cutover date: general ledger balances as at cutover, open customer and vendor items, open bank reconciliation items, inventory quantities and values, fixed asset net book values, and accrued or deferred balances.
Do not reload fully applied historic entries, closed-period journals, or years of audit trail. Beyond the volume, it creates duplicate posting risk: the same invoice can land twice, once from the load and once from a late legacy posting nobody caught before the freeze.
Decide how comparatives will be produced. Comparative information for the prior period is required for amounts shown in the financial statements and the notes, so choose deliberately between reporting from the archive or posting a controlled comparative journal, and document that choice before go-live. Multi-entity groups with different closing calendars should treat this as a design decision, not an afterthought. Entities operating in the KSA carry added compliance and Vision 2030 digital transformation pressures, as covered in تحديات متاجر السعودية وكيف يحلها ERP الحديث, and may want that method reviewed twice.
Set a written materiality threshold. For genuinely immaterial balances such as petty cash or small accruals, state the threshold and list what was excluded and why. Quiet omissions surface at the first audit, usually without a supporting document.
Next, every open item crosses the line as an individual, applicable line.
Step 4: Land Every Open Item Line by Line
Open items are where the migration either reconciles or quietly does not. Work subledger by subledger, and treat each one as a mini-project with its own sign-off.
Receivables and Payables
Extract every unpaid customer invoice with number, date, due date, currency, and remaining amount. Load them through Business Central's opening balance and document application mechanics so the aged debtors report reproduces the legacy ageing rather than a fresh approximation. Payables follow the same discipline: payments on account, credit notes, and prepayments must be applied against the invoice they relate to, not left as floating balances that inflate both sides of the subledger at once.
Bank, Cash, Inventory, and Work in Progress
Carry uncashed checks, deposits in transit, and charges not yet posted, so the first bank reconciliation in Business Central starts from the legacy statement position instead of a forced plug. For inventory and work in progress, migrate quantities and unit costs, not values alone. The first valuation report must tie to the legacy stock report, and margin calculations need unit costs that can survive scrutiny.
Foreign Currency Items
Keep each open item in its original currency and apply the agreed rate once at load. Combined Lebanon and KSA operations often carry multi-currency balances, and translating twice pushes the difference straight into profit and loss. Currency and tax configuration belongs to the same setup exercise; what Business Central does for tax and invoicing compliance explains how that structure is built.
Signed Subledger Reconciliation
For each subledger, produce a signed reconciliation showing three figures: the legacy subledger total, the migrated open items, and the general ledger control account balance at cutover. All three must agree. Where they do not, the explanation belongs in a supporting document, not a comment cell.
With every open item landed and tied, the next step is proving the system keeps processing correctly after go-live.
Step 5: Parallel Run Controls and Account-by-Account Reconciliation
With every subledger signed, you have a static position. The next layer tests behavior.
Layer 1: Static Reconciliation
Agree each general ledger account between the legacy trial balance and the Business Central opening trial balance at the cutover date. Penny-perfect tie-outs, not record counts. Every difference needs a supporting document: a mapping bridge rule, a reclassification journal, an FX retranslation calculation. Never a comment typed into a spreadsheet cell, because that comment is not evidence an auditor can test.
Layer 2: Parallel Run
Process one or two periods in both systems across a defined cycle set: sales invoicing, purchasing, bank, and relevant payroll. Compare outputs line by line. Keep the scope narrow and named; running everything doubles the finance team's data entry burden and adds its own control risk. Time-box the run, typically two to four weeks, with a fixed end date.
Set acceptable difference thresholds before the run starts. Agree on amounts and account types up front so the outcome is not negotiated after the numbers appear. Any threshold change after results are in requires written approval.
The Sign-Off Sheet
Record every account in a single reconciliation sign-off sheet: account, legacy balance, migrated balance, difference, cause, owner, status, signer. This artifact, not the loader log, is what carries an ERP implementation through an audit. The same discipline applies beyond finance: disconnected inventory systems create an identical tie-out gap in retail.
The sign-off sheet answers whether the balance is right. The next question is what an auditor actually tests.
What Auditors Look For in Migrated Opening Balances
Once your reconciliation sign-off sheet is complete, assume an auditor will test it. Under ISA 510, opening balances are defined as prior-period closing balances, so the audit question is always whether your legacy close was correctly brought forward into Business Central.
Completeness and accuracy
Point the auditor to the last closed or audited legacy position, then show a documented bridge for every difference. An unexplained variance, or one explained only in a spreadsheet comment, fails. The evidence expected scales with materiality, account risk, and whether the prior period was audited or carried a modified report.
Authorisation evidence
Produce signed records showing who approved the cutover point, the chart of accounts and dimension mapping decisions, and the final opening trial balance. Names and dates, not email threads. Mapping rules that consolidated 400 legacy accounts into 180 need that approval attached to each merge.
Cut-off integrity
Prove the legacy system was genuinely frozen after the cutover date. Auditors look specifically for postings in the old system that never reached Business Central, so keep a read-only query trail and a dated freeze confirmation from the system owner.
Traceability
Expect a sample test: take a migrated opening item, vouch it back to a legacy document number, then forward to the first post-go-live posting. Run that test internally before the auditor does. The same readiness discipline applies to platform changes covered in Business Central 2026 Release Wave 2: What's Changing and What US Businesses Must Do Before Go-Live.
Jurisdiction
ISA 510 is the common reference point, but adoption dates, statutory and tax filing requirements, and documentation expectations vary by entity and country. Confirm what your own auditor requires rather than assuming a single regional standard.
Step 6: Sign Off and Retire the Legacy System in the Right Order
With the audit evidence assembled, the next move is procedural, not technical: reconcile, sign, then retire, in that order. Skipping a step here is what turns a clean migration into a contested one.
Retire the legacy system only after the first full close in Business Central ties to the last close before cutover. Until that close is signed, the old system stays frozen and queryable with posting access revoked. Even after retirement, retire means stop posting, not delete. Keep the archive accessible for the retention period your auditor and local rules require.
Hand over a migration pack containing the mapping workbook, reconciliation sign-off sheets, the cutover decision record, open-item extracts, and archive access instructions. This is the file that answers an auditor's questions two years from now.
Assign post-go-live ownership in writing: who monitors the first close, who clears unmatched items during the parallel run, and the review date set before archive access is revoked.
With the legacy system correctly retired, the remaining question is which category of data migration tooling gets you there.
Data Migration Tools: Choose the Category, Not the Logo
With sign-off and legacy retirement behind you, the tool decision still deserves a straight answer. The category you choose determines what reconciliation you can actually produce.
Three categories cover almost every move:
Built-in Business Central migration and configuration packages for master data and standard opening balances.
Partner-led scripts and staging tables for complex or multi-entity loads, where mapping logic lives in code you control and can inspect.
Specialized third-party tools for repeatable, tool-driven migrations across several entities or staggered cutover waves.
Judge every option against three tests: does it handle your chart of accounts, dimensions and subledger detail at the depth you need; does it produce reconciliation output you can hand to an auditor; and can it be rerun cleanly after a failed load without duplicating postings?
Be clear about the limit. A loader that moves rows quickly does not create reconciliation. Reconciliation is a design and control decision, not a feature of the tool. A fast load into an unmapped chart of accounts just produces wrong balances faster.
For a NAV to Business Central move, expect to combine pathways: standard mechanisms for master data, purpose-built handling for opening balances and open items. No single mechanism covers both well, and configuration packages alone rarely carry the subledger depth that open receivables and payables demand.
Whichever category you pick, the controls around it decide whether those opening balances survive go-live.
Pitfalls That Break Opening Balances After Go-Live
Choosing the right loading mechanism is only half the equation. The failures that break opening balances are control failures, and they follow a predictable pattern.
Backdated postings into closed periods. Loading an opening balance after go-live with a posting date before the cutover reopens a period already reported on. Close it in the legacy system and post the load on or after the cutover date Business Central expects. If a late adjustment is unavoidable, route it through the current period with a documented bridge, not a reopened prior month.
Trial balance without open items. A GL-only load balances at the control account and fails at the subledger. The mismatch surfaces at the first aged debtors review or customer statement, when the open-item total does not equal the receivable control. Load documents, not just totals.
FX open items at the wrong rate, or twice. Monetary items are retranslated at the closing rate at each reporting date, and exchange differences go to profit or loss. Load each open item in original currency at the agreed cutover rate once. Re-translating an already-loaded item pushes a purely mechanical difference into P&L.
Freezing the chart of accounts map too early. Sign off the ERP implementation design first. A late account merge or split invalidates every balance already loaded and reconciled against the old map, forcing a reload.
Treating go-live as the finish line. The first close is the test. Keep migration staff engaged, keep the reconciliation workbook open, and hold sign-off until it ties.
Every pitfall traces back to one design decision: whether reconciliation drives the cutover or follows it.
Conclusion: Reconcile First, Switch Off Second
Avoiding those pitfalls comes down to sequence and discipline. Fix and sign the cutover point at a closed period boundary before anyone maps a single field, then freeze the legacy system on that date. A signed date, not an agreed intention, is what keeps every downstream step stable.
From there, migrate opening balances and open items only. Archive closed years as a read-only reference instead of reloading them into Business Central, because every extra historical row adds migration effort without adding reconciliation value. On day one, each subledger should tie to its control account: receivables, payables, bank, inventory, and fixed assets.
Reconcile account by account. Explain every difference with a supporting document rather than a spreadsheet comment, and time-box a parallel run for the cycles carrying the most financial risk, typically sales invoicing, purchasing, and bank. Set difference thresholds before the run starts so the outcome is not negotiated after the numbers appear.
Keep the legacy system read-only until the first post-go-live close matches the last pre-go-live close, line for line. Only then sign off and retire it, handing over a complete migration pack: the mapping workbook, reconciliation sign-off sheets, the cutover decision record, open-item extracts, and archive access instructions.
Judge the ERP system migration by that close-to-close match, not by record counts. Reconcile first; switch off second.
