Migrating from QuickBooks to Microsoft Dynamics 365 Business Central
QuickBooks is genuinely good software for what it's built for — a small business keeping clean books. It was never built to run inventory across three warehouses, cost a manufacturing job properly, or consolidate two trading entities into one set of numbers. When a business hits that wall, this is the move that gets made.
Book a QuickBooks Migration Assessment
Where QuickBooks stops being enough
QuickBooks was designed around a single small business with relatively simple stock and no real manufacturing complexity. It has no native multi-entity consolidation, its inventory tracking is basic even in the higher tiers, and there's no genuine job costing beyond tagging transactions to a class or category. Once a business needs any of that properly, QuickBooks becomes the thing everyone works around rather than the system everyone works in.
The pattern we see most often: a business that started as a simple trading or services company on QuickBooks Online, grew into holding physical stock, and now runs a separate spreadsheet just to track what's actually on the shelf because QuickBooks' inventory module can't handle serial numbers, multiple locations, or proper valuation methods. Add a second trading entity or the need for real job costing, and QuickBooks is holding the business back rather than supporting it.
What's different once you move to Business Central
| Area | QuickBooks | Business Central |
|---|---|---|
| Inventory | Basic FIFO tracking, no serial/lot tracking, single location in most tiers | Multi-location, serial/lot tracking, multiple valuation methods |
| Job costing | Classes and categories used as a workaround | Native project and job costing tied directly to the G/L |
| Multi-entity | Separate company files, no native consolidation | Multiple companies in one environment, real consolidation |
| Manufacturing | Not supported natively | Native BOMs, production orders and routings on Premium |
| User scale | Becomes unwieldy much beyond 20–25 users | Built to scale from 10 to several hundred users |
What migrates from QuickBooks, and what doesn't
What we migrate
Chart of accounts, customer and vendor lists, item lists, open invoices and bills, and current account balances — pulled via QuickBooks Online's API or exported from the desktop file, then remapped to BC's structure.
What usually stays archived
Full historical transaction detail rarely carries across cleanly, since QuickBooks and BC structure detail differently. We keep it accessible in an archive rather than forcing a messy line-by-line import.
What we check for before touching your data
Classes and categories used as a substitute for job costing
If your team has been tagging transactions with classes to fake proper job costing, that logic needs rebuilding properly in BC's project module — not copied across as-is.
Multiple QuickBooks files pretending to be one business
If you're running two or three separate QuickBooks company files for what's really one operation, this is the point to consolidate properly rather than replicate the same fragmentation in BC.
Bank feed rules that don't translate directly
QuickBooks' automatic bank rules and categorisation logic need to be rebuilt as BC's own reconciliation setup, not assumed to carry over automatically.
A realistic QuickBooks-to-BC timeline
Discovery & Data Review
1–2 weeks understanding your current QuickBooks setup and what's genuinely worth migrating.
Build & Migration
3–5 weeks configuring BC and migrating master data and open transactions.
UAT, Training & Go-Live
2 weeks of testing, role-based training, and a planned cutover.
What changes on the licensing side
QuickBooks pricing scales by tier and feature set, but stays relatively flat per business regardless of user count on lower plans. Business Central licenses per named user, per month. For businesses moving from QuickBooks with more than 8–10 users needing system access, the cost comparison usually favours BC once you factor in what QuickBooks Advanced or a third-party inventory add-on was already costing.
The businesses that outgrow QuickBooks fastest
Product businesses
Companies that started as services and now hold physical stock QuickBooks can't properly track.
Growing teams
Businesses pushing past 20–25 users who need proper permissions and workflow, not a shared login.
Multi-entity groups
Businesses running two or more QuickBooks files that really need one consolidated view.
Project-based businesses
Teams that need real job costing instead of tagging transactions with a class.
The integrations that come along for the ride
QuickBooks businesses often have a handful of connected apps — a payment processor, an e-commerce platform, a payroll tool. Each of these needs a BC-side equivalent, and we map them out during discovery rather than discovering them mid-project.
E-commerce
Shopify and WooCommerce connections get rebuilt against BC's native sales order structure.
Payments
Payment processor integrations are reconfigured to post directly into BC's cash and bank accounts.
Payroll
Most payroll tools that connected to QuickBooks have an equivalent BC or Microsoft 365 integration path.
What QuickBooks-to-BC migrations typically deliver
Aggregate results from recent NetMonkeys Business Central implementations.
Faster order processing once stock and sales share one database.
Less duplicated data entry between sales, stock and finance.
Reporting ROI versus manual QuickBooks report-building.
Real stock visibility across every location, not just one.
Why migrate from QuickBooks with NetMonkeys
100+ BC Projects
A decade of BC and NAV implementations across UK SMEs, including QuickBooks migrations.
Microsoft Solutions Partner
Certified across Business Applications, re-verified annually.
UK Consultants
Every consultant and project manager is UK-employed.
Realistic Scoping
We'll tell you honestly if you're not ready to leave QuickBooks yet.
QuickBooks to Business Central: common questions
Can you migrate from both QuickBooks Online and Desktop?
Yes. QuickBooks Online migrations typically pull data via its API; Desktop migrations work from an exported company file. Both end up in the same place.
Is Business Central overkill for a small business on QuickBooks?
For some, yes. If you're a small services business with simple books and no stock, QuickBooks may still be the right fit. This move tends to make sense once inventory, job costing or multi-entity reporting become a genuine problem.
How long does a QuickBooks migration usually take?
Most run 6–9 weeks from discovery to go-live, shorter than a typical Sage or NAV migration since QuickBooks setups are usually less customised.
Will our connected apps like Shopify still work?
The connection gets rebuilt against Business Central rather than carried over directly, but yes — e-commerce and payment integrations are part of a standard migration scope.
What happens to our historical QuickBooks data?
It stays accessible in an archive for reference and audit purposes. We migrate open transactions and current balances live rather than importing years of settled detail.
Outgrowing QuickBooks?
A free 45-minute assessment of your current setup, with a straight answer on whether Business Central is actually the right next step.