QuickBooks to Business Central migration: what moves, cost, timeline

A QuickBooks to Business Central migration at 20 to 100 people moves a defined set of data: customers, vendors, items, the chart of accounts, beginning balances, open invoices and bills, and on-hand inventory quantities. Closed history stays behind, and a partially paid invoice arrives at its full amount: a USD 500 invoice with USD 300 already paid lands as USD 500, and someone posts the USD 300 by hand afterward. The published part of the bill is the destination license: Business Central Essentials costs USD 80 per user per month in the United States and CAD 108.50 in Canada, as of October 2026. The project price comes from the partner's quote, which makes scope the variable that decides your number: how much history you insist on bringing, and how clean the file is when you start.

This page walks the move the way a project runs: what the Microsoft extension carries over, how QuickBooks Online and Desktop differ, what the pieces cost, the cutover sequence, the cleanup that has to finish first, and the spots where scope surprises live, from Canadian tax to payroll to bank feeds. It assumes the decision to move is made. If you are still weighing the timing, start with when to move from QuickBooks to an ERP and come back here for the mechanics, the sequence and the money.

What moves, what stays behind, and what you rebuild

Business Central's Data Migration assisted setup ships two QuickBooks extensions, one for a QuickBooks Online connection and one for a Desktop file. The Microsoft marketplace listing for the migration covers accounts, customers, vendors, items, general ledger accounts with a beginning balance, open transactions, and inventory on-hand and service items, with Essentials and Premium editions and the United States, Canada and the United Kingdom named as supported. That list is the entire documented scope as of October 2026, and it is worth reading twice, because it defines what your quote should price.

History sits outside that list. Nothing on Microsoft's pages puts a full historical general ledger in the extension's scope, so a buyer who wants line-level history inside Business Central needs a separate method from the partner, carried as its own scope line. Microsoft is explicit about partial payments too: only full amounts on sales and purchase documents migrate. A USD 500 invoice with USD 300 already paid arrives as USD 500, and the USD 300 gets entered manually.

• Customers, vendors, items, chart of accounts (What the documented migration does: Migrated as masters · What you do about it: Merge duplicates and retire dead records before the export)
• Beginning balances (What the documented migration does: Imported as general ledger transactions · What you do about it: Tie them to the QuickBooks trial balance at the cutover date)
• Open sales and purchase documents: invoices, credit memos, payments (What the documented migration does: Migrated at full amounts only · What you do about it: Reconcile the migrated documents against your AR and AP aging)
• Partial payments (What the documented migration does: Stay behind; the invoice arrives at its full amount · What you do about it: List them before the freeze and post each paid portion by hand)
• On-hand inventory quantities (What the documented migration does: Migrated for inventory items · What you do about it: Count the key locations anyway and correct at cutover)
• Closed transaction history (What the documented migration does: Outside the documented extension · What you do about it: Keep QuickBooks read-only, or price a custom history load)
• Attachments, custom fields, budgets, recurring templates (What the documented migration does: Not listed on the Microsoft pages · What you do about it: Treat as out of scope until your partner confirms it in writing)

The last row is where surprise projects come from. Partner pages that promise a complete conversion run ahead of Microsoft's documentation, and the gap turns into your team's evening work in week one. Name the entity list in the quote. Anything beyond it becomes a priced decision, which is the right place for that conversation.

QuickBooks Online or Desktop: does it change the migration?

For a QuickBooks Online company, the QuickBooks Online Data Migration extension runs from the same assisted setup wizard. For a Desktop file, you run Microsoft's Data Exporter Tool inside QuickBooks, it produces a zip file, and the instructions sit inside the Data Migration wizard. The pages list one entity set for both paths, with one wrinkle: Microsoft's migration page presents its QuickBooks Online data under a section headed for desktop, so treat the page list as a starting point and confirm the export against your own file. Run the import once into a test company and read the result line by line before you point it at live books.

The bigger difference is the product clock. In the United States, Intuit stopped selling new subscriptions of QuickBooks Desktop Pro Plus, Premier Plus, Mac Plus and Enhanced Payroll after 30 September 2024, per Intuit's help article, updated 4 August 2026. Existing subscribers can keep renewing, and Intuit still provides security updates, product updates and support. Desktop Enterprise sat outside that stop-sell and remains on sale. Intuit's article names no date when existing Pro or Premier renewals would end.

Canada has moved further. Per Intuit Canada's discontinuation policy, updated 5 August 2026, QuickBooks Desktop 2023 was discontinued after 31 May 2026, covering Pro Plus 2023, Premier Plus 2023, Enterprise 23.0 and the accountant editions. From 1 June 2026, that generation lost live support, Desktop Payroll, Desktop Payments, Online Backup, online banking and bank feeds, and critical security updates. Existing Plus and Enterprise subscribers are entitled to version 2024 as part of the annual subscription at no additional cost. If you still run a Canadian Desktop 2023 file, you have been working without its payroll, payments and bank feeds since June 2026, which puts the ERP decision on a shorter clock.

One Desktop footnote: a claim circulates that the Data Exporter works only with QuickBooks Desktop 2017 and 2018. Let your own file settle it: run the export during evaluation, before the cutover plan depends on it.

What a QuickBooks to Business Central migration costs

Microsoft publishes the destination licenses and leaves the project unpriced. Licenses, per user per month, paid yearly, as of October 2026, per Microsoft's US pricing page:

• Business Central Essentials (United States (USD): 80 · Canada (CAD): 108.50)
• Business Central Premium (United States (USD): 110 · Canada (CAD): 149.20)
• Team Member (United States (USD): 8 · Canada (CAD): 10.90)

The Canadian list adds tax to each figure. Full licenses cover the people who post transactions; Team Member seats cover occasional users at a small fraction of the cost.

Assume a 25-person company where 12 people need a full Essentials license and 13 work in Team Member seats. On US pricing that is 12 times 80 plus 13 times 8, which comes to 1,064 per month, or 12,768 per year. On Canadian pricing the same mix is 12 times 108.50 plus 13 times 10.90, about 1,443.70 per month plus tax, roughly 17,324 per year. Write that down as the recurring cost, separate from the project, because it repeats every year no matter how the migration goes.

The project itself is the number with no published figure: as of October 2026, the project price was not published for a QuickBooks file, so the quote you sign is the source. Each bidder has to price the same lines separately: the entity list from the table above, the cleanup, the tax configuration, cutover support and training. A one-line total hides exactly the work this page describes, and it pushes the surprises back onto you.

What moves a quote from low to high, in rough order:

• History scope. Open items plus a trial balance travel the documented path; line-level history is custom development.
• Cleanup volume. Thousands of dormant customers, duplicate items and an overgrown chart of accounts all bill hours before the export runs.
• Tax configuration. The Canada localization covers GST/HST reporting, sales tax, use tax, purchase tax, deposits, electronic payments and GIFI codes, and every tax code your company uses, provincial or US state, is still a line to map from QuickBooks and test before you file.
• Payroll and bank-feed replacements, which sit outside the migration entirely.
• Training and parallel-run support, which some quotes leave out of the base number.

Our ERP implementation services page describes how we phase discovery, migration, configuration, testing and training, and the same split helps you judge any partner's number.

One decision belongs before the quotes: the platform itself. From a QuickBooks base, Business Central is the shorter road when finance leads the move. The documented migration path, the published license pricing and the Canadian tax localization all come from one vendor, and our Business Central implementation page shows how we phase the project. Odoo earns its place in these evaluations when the company wants a wider operational footprint around finance; our Odoo implementation page describes what that rollout covers, and the cleanup and cutover work in this page applies either way. If the pairing is still contested internally, Business Central compared with QuickBooks covers the comparison most QuickBooks companies run first.

The cutover plan: date, freeze, load, parallel run

Most migration risk lives in the two weeks around the cutover date, so the plan is a sequence and each step has an owner:

1. Pick a fiscal boundary. Month end is the practical minimum; quarter end is better, because the beginning balance then ties to a trial balance someone has already reviewed.
2. Finish cleanup before the freeze. Cleanup done after the freeze means doing the work twice under deadline.
3. Freeze QuickBooks at the boundary. Last invoices, last bills, final payroll, final bank reconciliation. From that hour, QuickBooks is read-only and every new transaction happens in Business Central.
4. Run the migration. Assisted setup with the Online extension, or the Data Exporter zip from Desktop, loading masters, beginning balances, open documents and on-hand quantities.
5. Verify before anyone posts: the Business Central trial balance against the QuickBooks one, AR and AP aging totals against the migrated open documents, and on-hand quantities against a fresh count of your main locations.
6. Post the partial payments by hand, from the list you built before the freeze.
7. Run one close in parallel. Produce the same bank reconciliation, aging and financial statements in both systems, compare them, and set exit criteria in advance: tie the trial balance, tie the aging, tie the stock, then retire QuickBooks to a read-only archive.

The parallel run doubles the work for one closing cycle, and it remains the cheapest place to discover that a tax code maps wrong or an aging total comes up short. A controller owns the date, the freeze and the verification. The implementation partner owns the load and the configuration around it. Your bookkeeper owns the freeze reconciliation and the partial-payment list. Put those names on the plan before the date goes on the calendar.

Data cleanup to finish before the freeze

Cleanup decides whether cutover weekend is a weekend of loading or a month of excuses, so start early and assign owners.

Chart of accounts first. Merge dormant accounts, collapse near-duplicates and retire the odd accumulation of years. Business Central can post through grouping setups, which means the account list you bring only needs one account per distinct posting behavior. A shorter chart also makes every report after go-live faster to build.

Customers and vendors come next: deactivate one-time records, merge duplicates, and confirm payment terms and tax codes on the survivors. Items are the long pole in a distribution file. Drop discontinued SKUs, fix units of measure, and decide item by item whether the on-hand quantity migrates or the item starts from a physical count. Count the valuable stock regardless, because the migrated quantity is only as good as the QuickBooks record underneath it.

Open documents deserve their own afternoon. Export the AR and AP aging at a test date, mark every partially paid invoice, and total both lists so you know the manual workload before you commit to a date. Make the history decision at the same time: closed detail either stays in a read-only QuickBooks file you keep for audits, or it becomes a custom load with its own price. Either way, export year-end reports and statements while the subscription is still active.

Canada and US specifics: tax, payroll, bank feeds, currency

Canadian operations get the friendliest documented support. Business Central's Canada functionality includes GST/HST reporting, sales tax, use tax and purchase tax, deposits, electronic payments and GIFI codes, per Microsoft's localization page as of October 2026. Build the tax code mapping during configuration and test it on live invoices during the parallel run, because a wrong GST code in month one becomes a correction exercise at filing time.

Payroll is the sharp edge. The Canada localization page does not list payroll, so a company leaving QuickBooks payroll needs a separate payroll product. On the US side, Enhanced Payroll stopped being sold to new subscribers after 30 September 2024 as part of the Desktop stop-sell. Arrange the replacement before the freeze, run the final payrolls, and carry year-to-date figures into the new product with care.

Bank feeds and multi-currency finish the checklist. The documented migration list covers neither, so put both on the scoping list and get written answers before you sign: how each feed reconnects after cutover, and how open invoices in a second currency convert. If you invoice in both US and Canadian dollars, set the currencies up in Business Central first and test a handful of open documents in both directions before the parallel run starts.

Mistakes that delay a QuickBooks migration

• Cutting over mid-period. A beginning balance that fails to tie to a reviewed trial balance turns week one into archaeology.
• Assuming history comes along. The documented extension carries balances and open documents; closed detail is custom scope, and the decision belongs before the signature.
• Skipping the partial-payment list. Every partially paid invoice arrives at its full amount, and the first dunning run after cutover is where the surprise surfaces.
• Cleaning after the freeze. Cleanup done under deadline gets shortcuts, and shortcuts live in the ledger for years.
• Treating tax, payroll and bank feeds as details. Canadian Desktop 2023 already lost its payroll, payments and feeds, and Business Central needs a separate payroll product. None of that migrates by default.
• Accepting a one-line quote. Push until the quote names the entities: masters, beginning balances, open documents, on-hand quantities, and everything beyond that priced separately.
• Planning around the exporter rumor. The claim that the exporter handles only 2017 and 2018 files circulates in partner material. Run the export from your live file during evaluation and let the result settle it.

Done well, the move is a clean boundary: one system for everything after a date you chose, a trial balance that ties, and a QuickBooks file that becomes an archive you open only for old detail. Flectic runs this sequence in phases under the Flectic Accelerated Delivery Framework, with the target for a first usable phase at 8 to 12 weeks. If the fitcheck put you in the middle or top band, book from its result: your answers travel with you into the contact form. If the cutover questions are piling up faster than the answers, take the booking card above and put a date on the call.

How Flectic can help

Flectic implements Business Central on Dynamics 365 for companies of 20 to 100 people in the US and Canada that move off QuickBooks and need reconciled opening balances before go-live. The finance foundation covers general ledger, accounts payable and receivable, dimensions and bank reconciliation. Flectic sends a written proposal with a fixed price for each phase before work starts. Book a free discovery call with Flectic to scope the Dynamics 365 implementation around your data.

Sources

• Migrate data from QuickBooks, Microsoft Learn, October 2026
• Switch from QuickBooks to Business Central, Microsoft Learn, October 2026
• US QuickBooks Desktop subscriptions sold after July 2024, Intuit, October 2026
• QuickBooks Desktop service discontinuation policy, Intuit Canada, October 2026
• Canada local functionality, Microsoft Learn, October 2026
• Dynamics 365 Business Central pricing, Microsoft, October 2026
• Dynamics 365 Business Central pricing, Canada, Microsoft, October 2026