QuickBooks to Business Central Migration: 2026 Guide

Last updated: October 27, 2026

By ZapAI Team

TL;DR: A QuickBooks to Business Central migration moves your customers, vendors, items, chart of accounts, opening balances, and open invoices with Microsoft’s built-in tool. It doesn’t move sales orders, purchase orders, partial payments, or your transaction history. Desktop users have an extra wrinkle, since Microsoft’s exporter is documented only for QuickBooks 2017 and 2018. Plan the history decision, payroll, and sales tax before you touch the wizard.

Most companies don’t leave QuickBooks because it broke. They leave because the workarounds piled up. Three spreadsheets to close the month. A separate inventory app. A consolidation file only one person understands. At some point the cheap system gets expensive, and Microsoft Dynamics 365 Business Central is where a lot of US companies land next, partly because it already sits beside the Outlook, Teams, and Excel files their finance people have open all day anyway. Makes sense.

Here’s the catch. The migration looks easier on paper than it is. Microsoft ships a QuickBooks migration tool inside Business Central, and partner blogs describe it as if it carries everything across. It doesn’t. This guide covers what the tool really moves, what it skips, the Desktop version problem almost nobody mentions, and how to decide what to do with ten years of history. Facts about the tool come from Microsoft Learn and Intuit’s own pages, checked on October 27, 2026. Anything that’s our practice judgment is labeled that way.

Have You Actually Outgrown QuickBooks?

You’ve outgrown QuickBooks when you hit its hard limits on users, accounts, or classes, or when your close depends on spreadsheets, multiple entities, or a separate inventory system. Single-entity companies with simple books usually don’t need to move yet.

Some of these limits are printed in black and white. Intuit’s QuickBooks Online usage limits page (updated August 5, 2026) caps billable users at 1, 3, 5, and 25 across Simple Start, Essentials, Plus, and Advanced. The chart of accounts tops out at 250 accounts below Advanced. Plus allows 40 classes and locations combined. Desktop Enterprise stops at 30 users on Gold and Platinum and 40 on Diamond, according to Intuit’s Enterprise pricing page.

The softer signs matter more, honestly. We hear them on almost every discovery call.

• Month-end close runs past 10 business days, and nobody trusts a report until it’s been through Excel.
• Two or three legal entities, consolidated by hand.
• Inventory lives somewhere else, or you need bins, multiple warehouses, assembly, or light manufacturing.
• You want department, project, and region on every transaction, and classes plus locations can’t stretch that far.
• Approvals happen in email. Auditors ask for a trail, and you rebuild one after the fact.
• Your subscription bill includes four add-ons that exist only to patch gaps an ERP covers natively.
• Still on QuickBooks Desktop 2023? Intuit’s discontinuation policy says it was discontinued after May 31, 2026, which ends payroll, bank feeds, and security updates on that version.

Two or three of those? Start planning. Just one, and it’s the user count? You might be fine on QuickBooks Online Advanced for a while. We’d rather tell you that now than sell you an ERP you’ll resent.

Is Business Central the Right Next System?

Business Central fits companies that already run on Microsoft 365, need inventory or light manufacturing, and want published per-user pricing. Intuit Enterprise Suite, NetSuite, and Sage Intacct are real alternatives with different strengths.

Intuit calls Enterprise Suite a direct alternative to traditional mid-market ERPs, and its spring 2026 release added transaction-level intercompany eliminations. Fair enough. If your team loves the QuickBooks interface and your problem is just entities, look at it. If your problem is inventory, operations, or living inside Microsoft tools, Business Central is the stronger pick. We compared it head to head in Business Central vs NetSuite if NetSuite is on your shortlist too.

What Does Microsoft’s QuickBooks Migration Tool Actually Move?

The built-in extensions move customers, vendors, items, the chart of accounts, a beginning balance in the general ledger, on-hand inventory quantities, and open invoices, credit memos, and payments. Orders, partial payments, and history stay behind.

There are two extensions, one for QuickBooks Online and one for QuickBooks Desktop. Both start from the Data Migration assisted setup, and Microsoft’s overview of moving from QuickBooks says they come installed and ready. No extra license. No marketplace app. Good start.

The details sit on the QuickBooks Online data migration page, and they’re more restrictive than most guides admit.

That full-amount rule bites. Hard. Microsoft’s own example is a $500 invoice with $300 already paid, which arrives in Business Central as a $500 open invoice. Fifty of those and your receivables aging is fiction. Migrated transactions land unposted, so there’s a review step before anything hits the ledger, and that’s where we tie out AR and AP aging against QuickBooks line by line.

One more trap from the field. The wizard expects an empty company. An Intuit Community user hit a stop error because test customers already existed in Business Central, and the fix was to delete them and restart. Run your trial migrations in a fresh company or sandbox every time.

What If You’re Still on QuickBooks Desktop?

Microsoft’s Desktop exporter is documented only for QuickBooks 2017 and 2018. Most Desktop users today run 2023 or 2024, so the realistic paths are converting to QuickBooks Online first, using Excel configuration packages, or using partner tooling.

This is the part competitors skip. The QuickBooks Desktop migration page says, plainly, that the data exporter tool currently works only with QuickBooks 2017 and 2018. That page was last updated in August 2025. Meanwhile Intuit discontinued Desktop 2023 after May 31, 2026 and moved subscribers to 2024. Do the math. The documented Desktop path doesn’t line up with the versions people actually run.

So what works? Three routes.

• Convert the Desktop file to QuickBooks Online, clean it there, then use the Online extension. Extra step, but you end up on Microsoft’s supported path. Intuit’s conversion tool has its own limits on file size and history, so test it on a copy first.
• Export lists and balances to Excel and load them through Business Central configuration packages. Microsoft’s default package covers 27 tables, including general journal lines. Microsoft also calls this advanced functionality and points you to a partner, which tells you something.
• A third-party migration tool or a partner’s own scripts. Fastest for big Desktop Enterprise files with inventory. Costs money, obviously.

For Desktop Enterprise companies with more than a few thousand items, we usually skip the QuickBooks Online detour and go straight to configuration packages. Less double handling. For a small Desktop Pro or Premier file, converting to Online first is perfectly sensible and keeps the cost down.

Should You Bring Your Transaction History or Just Opening Balances?

Bring opening balances and open items at a clean period start, add two or three years of monthly summarized history if your team needs year-over-year reports, and keep QuickBooks read-only as the detailed archive.

Everyone asks for full history at first. Ten years, every invoice. Then they see the cost. Ouch. Detailed history means mapping old customers, retired items, and closed accounts, then reconciling each period, and it can double a project’s data work without changing a single day-to-day process. Here are the three options we lay out for clients.

Our default is the middle row. It gives your controller comparisons and budgets in Power BI without the bill for detail nobody opens. Keep a QuickBooks Online subscription on its cheapest plan, or a read-only Desktop copy, for a year or two so anyone can pull an old invoice. Cheap insurance.

What Happens to Payroll, Sales Tax, and Inventory Costing?

Business Central has no built-in US payroll, so you’ll pick a payroll provider and import its journal entries. Sales tax jurisdictions must be set up before posting, and inventory costing needs a deliberate choice.

Payroll first, because it surprises people. QuickBooks Payroll doesn’t come with you, and Business Central doesn’t replace it for US companies. Most of our clients use ADP, Paychex, Gusto, or a PEO and post a summarized payroll journal into Business Central each pay period. Decide this early. Payroll providers need weeks to onboard, and switching mid-quarter means extra tax filings.

Sales tax is next. Microsoft’s migration page says that if your transactions include tax, you must set up a tax account for your jurisdictions in Business Central before posting, which sounds like a footnote until you realize every migrated open invoice with tax on it is waiting on that setup before it can post. In practice that means tax areas, jurisdictions, and groups for every state where you collect. Selling into a dozen states? Look at a tax engine like Avalara rather than maintaining rates by hand.

Then inventory. QuickBooks Desktop Enterprise uses average cost, with FIFO available on its Advanced Inventory add-on. Business Central offers FIFO, LIFO, average, standard, and specific costing per item. Pick deliberately. Then reconcile the inventory value at cutover to the penny, because a costing method that quietly changes from average to FIFO on the day you go live will move your cost of goods sold and your margins in ways that nobody on the finance team can explain at the first board meeting. It’s the number auditors check first.

How Long Does a QuickBooks to Business Central Migration Take?

Four to eight weeks for a single QuickBooks Online company moving balances and open items. Eight to fourteen weeks with inventory, integrations, and summarized history. Multi-entity Desktop Enterprise projects with manufacturing can run five months or more.

Those are our practice estimates, not a published benchmark, and nobody has independent data here. Partner-published ranges we reviewed land in the same neighborhood, from a few weeks for simple files to four months or more for complex ones.

Configuration is almost never the slow part. Cleanup is. A vendor list with three versions of the same supplier, items nobody has sold since 2019, accounts named Misc 2. That’s where the weeks go. Every time.

What Does Business Central Cost Compared With Staying on QuickBooks?

Business Central costs more per user than QuickBooks. Essentials lists at $80 per user per month against QuickBooks Online Advanced at $340 per month for up to 25 users, but light users can run on $8 Team Members licenses.

Microsoft’s Business Central pricing page lists Essentials at $80, Premium at $110, and Team Members at $8 per user per month, paid yearly. Intuit’s QuickBooks Online pricing showed Advanced at $340 a month on the day we checked. Here’s how that plays out for a 25-person company, our arithmetic at list price.

Yes, it’s more. Noticeably. The honest comparison isn’t license to license, though. It’s license plus the add-ons, the spreadsheet hours, and the inventory app you’d retire. Who needs a full license and who can work on Team Members is the biggest lever, and our Business Central pricing breakdown walks through that. For implementation budgets, see our guide to Dynamics 365 implementation cost, which includes a worked 40-user Business Central example.

What’s the Step-by-Step Cutover Plan?

Clean and number your QuickBooks data, run at least two trial migrations into an empty sandbox, reconcile everything, then cut over at a period end and run one parallel close before archiving QuickBooks.

This is the sequence we follow. It’s not glamorous. It works.

• Pick the cutover date. Month end at minimum, quarter or fiscal year start if you can wait.
• Clean QuickBooks. Merge duplicate customers and vendors, inactivate dead items, apply open credits and partial payments.
• Number the chart of accounts in QuickBooks and map it to your new Business Central structure, including dimensions for department or location.
• Set up tax jurisdictions, posting groups, and payment terms in Business Central.
• Trial migration number one into a fresh sandbox company. Expect it to fail somewhere. That’s what it’s for.
• Reconcile. Trial balance, AR aging, AP aging, inventory value, each tied to QuickBooks at the same date.
• Trial number two with the fixes, signed off by your controller.
• Final migration after the cutover period closes in QuickBooks. Post, reconcile again.
• Run one month-end close in Business Central while QuickBooks stays available read-only, then lock it.

Teams that have done a Dynamics GP to Business Central migration will recognize the rhythm. Same idea, smaller data.

What Mistakes Cause QuickBooks Migrations to Go Wrong?

Most failures trace back to six things. A non-empty target company, partial payments migrated at full value, unnumbered accounts, posting before balances are verified, forgotten discounts, and a payroll decision made too late.

The first four come straight from Microsoft’s documentation, and we still see them. Number five is quieter. Markups and discounts on open documents don’t carry over, so an invoice that showed a 10% discount in QuickBooks lands at full price unless someone fixes it before posting. Customers notice that one fast.

Payroll is the expensive mistake. A company goes live in Business Central in March, realizes QuickBooks Payroll is still running, and ends up with two systems and a mid-quarter provider switch. Settle payroll in week one of the project, not week ten.

And the one that isn’t technical at all? Skipping training on posting groups and dimensions. A bookkeeper who was fast in QuickBooks feels slow for the first month in Business Central. That’s normal. Budget time for it rather than declaring the project a failure in week three.

Wrapping Up

Microsoft’s QuickBooks migration tool is free and useful, but it moves master data and open balances, not your past. Desktop users need a workaround because the exporter is documented only for 2017 and 2018. And payroll, sales tax, and history decisions shape the timeline far more than the software does.

ZapAI is a Microsoft Dynamics 365, Power Platform, Fabric, and AI consulting firm based in Irving, Texas, working with US businesses. Our Business Central implementation team handles QuickBooks migrations end to end, from data cleanup and the history decision through payroll integration and the parallel close. If you’re weighing the move, a short QuickBooks migration scoping call will tell you which path fits your file and what it’ll realistically take. Texas-based companies can also see how we work with Dallas-area Dynamics 365 clients.

What QuickBooks Users Ask Before Switching

Can Business Central import data from QuickBooks Online and Desktop?

Will I lose my QuickBooks transaction history?

Are open sales orders and purchase orders migrated?

Does Business Central include payroll?

Is Business Central harder to learn than QuickBooks?

How much more does Business Central cost than QuickBooks Online Advanced?

Can we keep QuickBooks after going live?