Native BC migration tools move masters and summary opening balances from QuickBooks — not historical transactions. Full migration requires custom scripting, COA restructuring, and posting group configuration.
Microsoft provides native QuickBooks migration extensions for both Desktop and Online, but these tools only transfer master data (customers, vendors, items, GL accounts), open invoices at full amounts, and summarized opening balances — not line-by-line historical transactions, purchase orders, sales orders, or partial payment applications. The fundamental data model challenge is that QuickBooks uses a flat, optionally-numbered account list while Business Central requires numbered GL accounts driven by posting groups, dimensions, and a General Posting Setup matrix, making the migration a structural translation rather than a 1:1 transfer. Custom scripting, API-based extraction, or Configuration Package workflows with manual posting are required to preserve detailed transaction history, and the native Desktop exporter only supports QuickBooks 2017–2018, leaving users on newer versions without an automated path.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
If your plan is to run the wizard and bring everything over, stop here
The official migration extensions import opening balances and open documents, not detailed closed history. For QuickBooks Desktop, Microsoft's exporter only works with QuickBooks 2017 and 2018.
Configuration Packages are intended for initial company setup — not for production data loads
If your BC environment is already live, use XMLport or the BC API for data imports.
If you reconnect an existing Sales integration through Dataverse, Microsoft warns that
If you reconnect an existing Sales integration through Dataverse, Microsoft warns that default synchronization settings are applied again and can overwrite your prior configuration. Plan that change like a real integration cutover, not a checkbox click. (learn.microsoft.com)
Do not wait until UAT to discover that your QuickBooks classes should have been
Do not wait until UAT to discover that your QuickBooks classes should have been dimensions, or that your partially paid invoices now exist in Business Central at full face value. Those are pre-migration problems, not post-go-live bugs.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Scope the ledger, the subledgers and the audit obligations.
Objective Agreed scope across master data, open transactions and historical balances, with finance and audit signed up.
Keep these open
-
Inventory master data and transaction volumes in QuickBooks
Count GL accounts, customers, vendors, items, fixed assets, open AR and AP, and transaction lines by year. Transaction line volume, not header count, is what determines your load time.
Data Profiler Get real record counts instead of estimating from memory -
Decide the history strategy with finance and audit
Choose between opening balances only, open items plus balances, or full transactional history. This is the single biggest scope decision in an ERP migration: full history multiplies effort many times over, and most organisations land on balances plus open items plus a read-only archive.
Full transactional history is rarely worth the cost. Confirm what your auditor actually requires before assuming you need it.
Vendor Evaluator Score Dynamics 365 Business Central against alternatives on weighted criteria -
Consult the external auditor early
The auditor has views on cut-over timing, audit-trail retention and how you evidence that balances carried across correctly. Finding this out after go-live can mean a qualified opinion, so get it in writing now.
-
Review the chart of accounts and decide whether to redesign
A migration is the natural moment to restructure the COA, and also the riskiest one. If you redesign, you need a mapping from old to new for every historical balance, plus a plan to restate comparatives.
Redesigning the chart of accounts mid-migration doubles the reconciliation burden. Treat it as a separate, sequenced project if you can.
-
Catalogue integrations and statutory reporting
List banking feeds, payment gateways, tax filing, payroll, CRM, e-commerce, warehouse and BI. Then list every statutory and tax filing obligation with its deadline — those deadlines constrain your window absolutely.
-
Pick a period-aligned go-live date
ERP cutovers align to a period boundary — ideally the start of a fiscal year, otherwise the start of a clean month. Mid-period cutover means split-period reporting for the rest of the year.
QuickBooks → Dynamics 365 Business Central specifics
- Sales invoices and purchase invoices
- but only full, unpaid amounts. Partially paid documents are imported at their full original amount; partial payment application is lost.
- Opening balances
- summarized, not transactional. QuickBooks does not store the current balance for all accounts, so beginning balances may need manual correction after import.
- Purchase orders and sales orders
- Microsoft's documentation for the QBO extension excludes these explicitly.
- Line-by-line historical transactions
- closed and reconciled transactions arrive as summary opening balance entries, not as individual GL lines.
- Markup and discount amounts
- these must be manually added to migrated transactions in BC before posting.
Don't move on until
- Chart of accounts and master-data counts confirmed
- History strategy agreed: balances, open items, or full transactional detail
- External auditor consulted on the migration approach
02 Data Audit Reconcile the source before you migrate it — you cannot fix a ledger later.
Objective A source ledger that balances, with master data cleansed and every open item agreed.
Keep these open
-
Produce and sign off a source trial balance
Run the trial balance in QuickBooks and have the controller sign it. This is your migration baseline: without a signed pre-migration position you have nothing to reconcile the target against, and any later discrepancy is unarguable.
Without a signed, dated source trial balance you cannot prove the migration preserved the ledger. Do this before anything else.
-
Reconcile subledgers to the general ledger
Confirm AR, AP, inventory and fixed-asset subledgers tie to their GL control accounts. Pre-existing breaks must be resolved in QuickBooks: migrating an out-of-balance ledger makes the break permanently unattributable.
Data Profiler Profile the QuickBooks export for nulls, outliers and type drift -
Clean and deduplicate master data
Deduplicate customers, vendors and items, and identify records that should not carry forward. Duplicate vendors are also a fraud-control weakness, so this has value beyond the migration.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Agree open AR and AP item by item
Every open invoice, credit note and payment on account needs an owner and an agreed amount, including partially-paid items and foreign-currency balances. Open items are what customers and vendors will dispute in week one.
-
Validate export structure, encoding and precision
Check numeric precision and rounding on the export, and confirm dates and currency codes are unambiguous. Precision loss on amounts is silent, cumulative and produces penny differences that take days to trace.
Amounts exported at reduced precision will not re-total. Verify decimal places before you accept the export.
CSV Validator Catch broken headers and ragged rows in the raw export -
Scan for regulated data and produce masked test data
ERP data holds bank details, tax IDs and payroll information. Scan it, restrict who can see it, and generate a masked copy for the sandbox and for any implementation partner.
PII & Compliance Scanner Find regulated fields before they land in a new system
Don't move on until
- Trial balance in QuickBooks balances and is signed by the controller
- AR and AP subledgers reconcile to the GL control accounts
- Master data deduplicated and inactive records identified
03 Field Mapping Map the COA, the dimensions and the subledger structures.
Objective A signed mapping covering the chart of accounts, dimensions, tax codes and currency handling.
Keep these open
-
Map the chart of accounts account by account
Every source account maps to exactly one target account, or to a documented split with agreed proportions. The controller reviews and signs this line by line — an unreviewed COA map is how a balance sheet stops balancing.
Schema Mapper Opens pre-loaded with the QuickBooks → Dynamics 365 Business Central field pair -
Map dimensions, cost centres and analysis codes
ERPs differ structurally here: segments, dimensions, tracking categories and classes are not interchangeable. Confirm how Dynamics 365 Business Central models analysis and whether your existing reporting hierarchy survives the translation.
-
Map tax codes, rates and jurisdictions
Map every tax code with its rate, jurisdiction and reporting treatment, then verify the mapping reproduces your last filed return. Tax errors are statutory exposure, not reporting inconvenience.
A tax-code mapping that has not been tested against a previously filed return is untested. Reproduce a real filing before sign-off.
-
Decide multi-currency and exchange-rate handling
Confirm functional and reporting currencies, and how historical rates are stored. Revaluing historical transactions at current rates rewrites reported results and will not tie to filed accounts.
Historical transactions must retain their original transaction-date rates, or your comparatives will not match filed statements.
-
Map master data and subledger structures
Map customer and vendor records with their payment terms, credit limits and tax registrations, and item records with units of measure and costing method. Costing-method differences change inventory valuation, which changes the balance sheet.
-
Set load order and freeze the spec
COA, then dimensions, then master data, then opening balances, then open items, then any historical detail. Version and sign off the spec with the controller before the pilot.
QuickBooks → Dynamics 365 Business Central specifics
- Custom fields and QuickBooks-specific configurations
- no path exists for these in the native tooling.
- Table 15 (G/L Account)
- your restructured, numbered Chart of Accounts with categories and dimension defaults.
- Table 18 (Customer) & Table 23 (Vendor)
- master records with correct posting group assignments.
- Table 81 (Gen. Journal Line)
- the staging table for historical financial entries.
- Tables 36/37 (Sales Header / Sales Line)
- for historical invoices that need to flow through the sales posting engine.
Don't move on until
- Account-by-account COA mapping reviewed by the controller
- Tax codes and jurisdictions mapped and verified against filings
- Multi-currency and rate handling agreed with finance
04 Test Migration Prove the ledger balances in the target before you trust it.
Objective A sandbox load whose trial balance matches the signed source position to the penny.
Keep these open
-
Configure the Dynamics 365 Business Central sandbox with the agreed structures
Build the COA, dimensions, tax codes, currencies, fiscal calendar and posting rules before loading anything. Every one of these affects how a posted transaction lands, so an unconfigured sandbox produces meaningless results.
-
Load master data and validate it
Load customers, vendors and items first and verify counts, payment terms, tax registrations and costing methods. Transactions cannot post correctly against wrong master data, so this gate comes before any balance work.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Load opening balances and prove the trial balance ties
Load opening balances and run a trial balance in Dynamics 365 Business Central, comparing to the signed source position. It must match exactly — a rounding difference here is a mapping defect, not a rounding difference.
Any variance at all between source and target trial balance must be explained line by line. "Close enough" is never acceptable in a ledger.
-
Load open items and reconcile the subledgers
Load open AR and AP with their ageing intact, then confirm subledger totals tie to GL control accounts and that ageing buckets match. Ageing that shifts means transaction dates mapped wrongly.
-
Run a full period-end close in the sandbox
Execute the whole close: revaluation, accruals, depreciation, tax calculation, and financial statement generation. Compare every statement to QuickBooks for the same period. The close is where structural mapping errors finally become visible.
-
Test transactions end to end and reproduce a tax filing
Post a sales order to cash and a purchase order to payment, then generate the tax return for a previously filed period and compare it to what you filed. If both reconcile, the configuration is sound.
Don't move on until
- Target trial balance matches the signed source trial balance exactly
- Subledgers reconcile to control accounts in the target
- A full period-end close has been run in the sandbox
05 Cutover Switch the ledger on a period boundary, with balances proven.
Objective Balances and open items live in Dynamics 365 Business Central, transacting resumed, and a signed post-load trial balance.
Keep these open
-
Close the final period in QuickBooks and freeze posting
Complete the period-end close, then lock posting entirely. An ERP freeze is absolute: a single journal posted to the old system after the final export leaves the two ledgers permanently divergent.
One journal posted in the old ERP after the final export breaks the reconciliation permanently. Lock posting at the system level, not by asking people nicely.
-
Publish the cutover runbook with the abort point
A timed, owner-named sequence for load, balance verification, integration switch and go/no-go, with an explicit abort criterion. The trial-balance check is the gate — nothing proceeds until it ties.
-
Load balances and open items into production
Load the final opening balances and open AR/AP into Dynamics 365 Business Central production, following the pilot-proven sequence. Do not improvise the order under time pressure.
-
Reconcile and sign the post-load trial balance
Run the trial balance in Dynamics 365 Business Central and reconcile it to the signed source position, then have the controller sign the result. This signature is your evidence for the auditor and your go/no-go gate.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint banking, payment and tax integrations
Switch bank feeds, payment gateways, tax filing connections, payroll and BI, then process one real low-value payment and one bank reconciliation end to end. Banking errors move real money, so verify with live traffic.
Payment integrations left connected to the old ERP can duplicate real payments. Disable them before switching, not after.
-
Go/no-go, then open for transacting with daily reconciliation
Call the decision on the signed trial balance, open Dynamics 365 Business Central for posting, and reconcile daily for the first two weeks with finance support on hand. Keep QuickBooks read-only for statutory retention — this is an audit requirement, not a preference.
Don't move on until
- Post-load trial balance signed by the controller
- Banking, tax and payment integrations verified live
- Users transacting and the first daily reconciliation clean
06 Validation Prove the statements, the tax position and the audit trail.
Objective Financial statements reproducing the source position, a clean tax filing, and auditor acceptance.
Keep these open
-
Reconcile the full ledger and all subledgers
Reconcile trial balance, AR, AP, inventory, fixed assets and bank against the signed source position. Produce a single reconciliation pack that goes to the auditor.
Migration Validation Tool Reconcile QuickBooks and Dynamics 365 Business Central record-for-record -
Reproduce the financial statements
Generate balance sheet, P&L and cash flow in Dynamics 365 Business Central and compare to the pre-migration statements. Every variance needs a documented explanation traced to a specific mapping decision.
-
Complete and review the first period-end close
Run the first real close in Dynamics 365 Business Central with extra review at every step. Compare its duration and outcome to your historical close, and treat anything unexpected as a live finding.
Data Profiler Prove field completeness held up through the load -
Verify the tax position and file
Generate and review the first tax filing from Dynamics 365 Business Central, reconciling it to the underlying transactions before submission. Have the tax lead review it independently.
The first statutory filing out of a new ERP should be reconciled manually to source transactions before submission.
-
Confirm controls, segregation of duties and audit trail
Verify user permissions, approval limits, segregation of duties and audit logging in Dynamics 365 Business Central. Controls do not migrate, and a control gap found by an auditor is far more expensive than one you find yourself.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Obtain auditor acceptance and retain the archive
Walk the auditor through the reconciliation pack, get written acceptance, and retain QuickBooks read-only for the full statutory retention period. Diarise the retention expiry rather than the contract renewal.
Don't move on until
- Financial statements match the pre-migration position
- First period-end close completed and reviewed in Dynamics 365 Business Central
- Auditor satisfied and archive retained for the statutory period
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Customers | low | Customer master data transfers cleanly through the native migration extensions with minimal transformation required. |
| Vendors | low | Vendor master data is fully supported by the native migration wizard and imports without significant issues. |
| Items | low | Item master data and on-hand inventory quantities are included in the native migration, though inventory valuation details may need verification. |
| Chart of Accounts | high | QuickBooks' flat, optionally-numbered account structure must be completely redesigned into Business Central's numbered accounts with posting groups and dimensions, and files without account numbers will fail the first validation step. |
| Historical GL Transactions | high | Closed and reconciled transactions arrive only as summary opening balance entries; preserving line-by-line detail requires custom scripting and posting through journal entries with full reconciliation. |
| Sales Orders and Purchase Orders | high | Neither sales orders nor purchase orders are transferred by the native migration extensions, requiring manual recreation or custom import workflows. |
| Partial Payments and Applications | high | Partially paid documents are imported at their full original amount with payment application history lost, requiring manual correction before posting in Business Central. |
| Classes and Custom Fields | medium | QuickBooks classes must be manually mapped to Business Central dimensions, and custom fields have no native migration path, requiring custom extraction and transformation. |
| Tax Configuration | medium | QuickBooks sales tax items must be manually translated into Business Central's tax accounts and posting setup before any migrated transactions can be posted. |
| Markups and Discounts | medium | Markup and discount amounts are not carried over by the migration extensions and must be manually added to migrated transactions in Business Central before posting. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Chart of Accounts Restructuring
QuickBooks uses a flat, optionally-numbered account hierarchy that must be translated into Business Central's numbered GL accounts with posting groups and dimensions, requiring a full structural redesign rather than a direct account mapping.
Historical Transaction Loss
Native migration extensions import only summarized opening balances and open documents, meaning closed and reconciled line-by-line transaction history is not carried over and requires custom scripting to preserve.
Desktop Version Incompatibility
Microsoft's Data Exporter Tool only supports QuickBooks Desktop 2017 and 2018, forcing companies on 2019 or later versions to fall back on manual CSV exports and Configuration Package imports.
Partial Payment Data Loss
The migration extensions import partially paid invoices at their full original amount, discarding the partial payment application history and requiring manual correction in Business Central.
Configuration Package Performance Locks
Large data imports via Configuration Packages lock target tables during validation, blocking all users from Business Central and causing full-batch failures if a single row contains a formatting or validation error.
Dimension Strategy Lock-In
Business Central's two global dimensions must be chosen correctly before the first data load because changing them later locks multiple tables, degrades performance, and can block other users until the operation completes.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Does the QuickBooks Data Migration Extension transfer historical transactions to Business Central?
No. The native extension transfers master data (customers, vendors, items, GL accounts) and opening balances as summary entries. Line-by-line historical transactions are not migrated. If you need transaction-level history inside BC, you need custom scripts or a migration partner.
What versions of QuickBooks Desktop does the Microsoft Data Exporter Tool support?
The Microsoft Data Exporter Tool only works with QuickBooks Desktop 2017 and 2018. If you are running QuickBooks Desktop 2019 or later, the tool is not compatible and you must export data manually via Excel/CSV or use the Business Central API.
Can I use Business Central Configuration Packages to import QuickBooks historical data?
Not directly into posted ledger entry tables. Microsoft says Configuration Packages cannot import data into tables with posted entries such as customer, vendor, and item ledger entries. You must import into pre-posting tables and then post inside BC. Large imports can also lock all users out of the system during processing.
How do I map QuickBooks accounts to Business Central's Chart of Accounts?
Business Central requires every GL account to have an account number — QuickBooks often does not. You also need to translate QuickBooks sub-accounts and classes into BC dimensions and configure posting groups that map customers, vendors, and items to the correct GL accounts. This is a structural design exercise, not a 1:1 copy.
Do I need Dataverse for a QuickBooks to Business Central migration?
Not for the QuickBooks import itself. Dataverse matters after migration if you need Business Central to sync with Dynamics 365 Sales or Power Platform apps. That sync is scheduled via job queues rather than guaranteed real-time.