Migrating from QuickBooks to Business Central
Moving from QuickBooks to Business Central — the data migration wizard, scope decisions, parallel running, and the gotchas that catch people out.
QuickBooks-to-Business-Central is one of the most common Dynamics 365 migration paths — typical of SMBs that have outgrown QuickBooks Online or QuickBooks Desktop and need real ERP capability. Microsoft ships a first-party data migration wizard for the QuickBooks Online source specifically, which lowers the technical bar substantially.
Why customers move. Common triggers: multi-entity needs (QB struggles past a handful), inventory complexity beyond QB's modest inventory module, multi-currency at scale, integration burden between QB and other systems, advanced reporting that QB can't deliver, and the desire to consolidate to Microsoft 365 + ERP under one vendor.
The migration wizard. From Business Central, the Data Migration assisted setup includes a QuickBooks Online connector that:
- Reads QuickBooks data via the Intuit API.
- Maps the chart of accounts (with manual review for the inevitable mismatches).
- Migrates customers, vendors, items, employees, and bank accounts.
- Brings opening balances at a chosen cut-off date.
- Optionally brings transactional history (open invoices, open bills, open POs).
The wizard handles the mechanical translation; the customer handles the strategic decisions.
Scope decisions.
- Cut-off date. Most projects pick a fiscal period boundary (month-end, quarter-end, year-end). Year-end gives the cleanest start; mid-year is feasible but requires more reconciliation.
- Historical detail. Trial balance only? Open transactions? Full historical detail? The wizard can pull full detail but the labour to validate and reconcile rises sharply with depth. Most projects migrate balances + open transactions, leaving full detail in QuickBooks (read-only) for reference.
- Chart of accounts. Business Central's chart of accounts is more structured than QuickBooks' and supports dimensions. Use the migration as an opportunity to clean up — but don't conflate cleanup and migration; cleanse in QuickBooks first, then migrate the clean version.
Inventory caveat. QuickBooks inventory is famously light; many customers carry inventory inaccuracies for years. Don't migrate the inventory state until it's been physically counted and reconciled. Going live with wrong inventory is a one-way ticket to chaos.
Parallel running vs hard cut. SMB customers typically do a hard cut at month-end — stop QuickBooks postings, run the migration, start Business Central. Parallel running (both systems live simultaneously) is rarely practical at SMB scale; the team can't absorb double the work.
Time to live. A focused QB→BC migration runs 8 to 16 weeks for a small SMB, including configuration, testing, and training. Bigger or more complex businesses run longer.
After migration. QuickBooks stays available read-only for at least a year for historical inquiries, audit, and tax filing. Eventually it can be decommissioned with the data archived.
The pitfall to avoid. Don't treat this as a like-for-like swap. Business Central's strengths (dimensions, multi-entity, real inventory, posting controls) are different from QuickBooks's strengths. Configure to take advantage of BC, not to mimic QuickBooks.
Related guides
- Migrating from NetSuite to Business CentralMoving from NetSuite to Business Central — the data and customisation challenges, the cost angle, and what to expect from the project.
- Migrating from SAP Business One to Business CentralMoving from SAP Business One to Business Central — the practical mapping, data migration approach, and the choices that decide the project's complexity.
- Business Central vs Dynamics NAVWhat changed in the move from Dynamics NAV to Business Central, and what that means for organisations still running NAV.
- Growing from Business Central to Finance and SCMWhen and how to move from Business Central up to Dynamics 365 Finance and Supply Chain Management — signals, scope, and the migration path.
- Migrating from NAV on-premise to Business Central SaaSMoving from Dynamics NAV on-premise to Business Central SaaS — the cloud migration tool, AL code rebuild, and the operational changes that come with it.