Should You Migrate from QuickBooks to Business Central?

Should you migrate from QuickBooks to Business Central? Yes, if you run more than one legal entity or face auditor or lender questions about approvals and change history. Lot or serial tracking is a reason to assess, and a reason to move when your edition cannot provide it. Stay if none apply and your edition is supported. A Desktop support date is a reason to plan, not to switch.

This article is for owners, controllers and finance leaders at US companies on QuickBooks Online, Desktop or Enterprise who need to decide whether to move to Microsoft Dynamics 365 Business Central, and when. It covers the yes/no test, a decision table, the QuickBooks Desktop dates Intuit has published, what Microsoft's migration tools move, and the timeline and cost bands Bitta Apps publishes. Every date and product fact was rechecked on 2026-11-04.

Running on QuickBooks today? Book a free discovery call and leave with a written plan for the next step, or use the short form on the QuickBooks to Business Central page. Prefer to talk now: (626) 766-9732.

Should I migrate from QuickBooks to Business Central? The yes/no test

Run the test on how the business operates today. Bitta Apps treats the first three signs as structural, because they describe how the business runs rather than a missing report.

Signs that mean yes:

• More than one entity. You consolidate two or more companies in Excel, while Business Central consolidation transfers each subsidiary's ledger entries into a consolidated company.

• Inventory tracking your edition cannot provide. You need serial, lot or package numbers, warehouse picks or barcode scanning, and your current QuickBooks edition cannot meet the requirement. QuickBooks Desktop Enterprise tracks serial or lot numbers through Advanced Inventory, which Intuit includes in the Platinum and Diamond subscriptions only, so the need on its own is a reason to assess, not proof you have outgrown QuickBooks.

• Someone is asking about controls. An auditor, a lender or a large customer wants approvals and a record of changes, which Business Central covers with approval workflows and a field-level change log.

• Reporting is rebuilt by hand. Profit by department, project, location or product line is assembled in Excel every month, where Business Central dimensions would tag each entry in the ledger.

• Integrations run on rekeying. E-commerce orders, EDI documents or shipping data are typed in again or moved by CSV export.

Signs that mean stay:

• One legal entity, straightforward invoicing and a simple item list.

• Standard QuickBooks reports answer the owners' questions.

• No audit, lender or customer requirement for workflow approvals or a field-level change history.

• Your QuickBooks edition is current and supported.

The rule Bitta Apps sets out: any one of the first three signs (entities, inventory, controls) is enough on its own to justify a migration assessment. The reporting and integration signs count when they appear together. Zero signs means stay where you are and revisit in a year. For the check behind each sign and the Business Central features that answer it, read the seven signs a business has outgrown QuickBooks. The QuickBooks and Business Central operational comparison explains why operational complexity matters more than employee count.

Decision table: stay on QuickBooks or move to Business Central

When to switch from QuickBooks to Business Central: the Desktop dates

For QuickBooks Desktop users, Intuit's published dates set the pressure. They do not decide the destination.

On a discontinued release, Intuit's notice lists what stops, including live technical support, critical security updates, payroll services, in-product payment processing and online banking. Keeping financial records on software without security updates is a risk decision, not a software preference. Intuit's own notice points those users to Desktop Plus 2024 or Enterprise 24.0, so a discontinued version forces a decision, not necessarily an ERP project.

These notices cover QuickBooks Desktop only. For Pro Plus 2024, Premier Plus 2024, Enterprise 24.0 and QuickBooks Online users, the decision rests on fit, which is what the test above measures.

What Business Central costs

Microsoft's published US list prices are $80 per user per month for Essentials, $110 for Premium and $8 for Team Members, paid yearly. The Dynamics 365 Licensing Guide (November 2026 edition) states that Premium adds Service Order Management and Manufacturing to Essentials. Team Members can read data, update existing records, approve workflow tasks and create quotes, which fits approvers and read-mostly users. Bitta Apps bills Microsoft licenses at those list prices with no markup, as stated on its pricing page. Tier choice is covered in Business Central Essentials vs Premium vs Team Members, and total cost in Business Central pricing for 2026.

Implementation is the larger number. Bitta Apps quotes it as a fixed price within published bands, in a written proposal within five business days of the scoping call. When detailed analysis is needed, a paid assessment is agreed first:

Where that paid step is needed, the Migration Readiness Assessment is $7,500, quoted up to $12,500 for multi-entity or integration-heavy scopes, and is delivered seven business days after access. Microsoft licenses and third-party app licenses are not included in the bands.

One point on incentives: Microsoft's AIM migration program serves qualified on-premises business applications customers, and its Bridge to the Cloud 2 promotional offer in CSP covers perpetual Dynamics on-premises products. The AIM page does not mention QuickBooks. If a partner offers a Microsoft-funded QuickBooks switcher discount, ask which published offer it comes from.

What a QuickBooks to Business Central migration moves

Microsoft still documents two QuickBooks extensions inside the Data Migration assisted setup guide in Business Central: the QuickBooks Data Migration extension for Desktop and the QuickBooks Online Data Migration extension. Neither appears on Microsoft's deprecated features lists as of 2026-11-04. Both import:

• customers, vendors, items and the chart of accounts

• beginning balance transactions in the general ledger

• on-hand quantities for inventory items

• open customer and vendor documents, such as invoices, credit memos and payments

The documented limits shape the plan:

• No orders. Microsoft states that purchase orders and sales orders are not migrated.

• Full amounts only. A partially paid invoice migrates at its full amount, so partial payments are updated by hand before or after the migration.

• Account numbers first. General ledger accounts must have account numbers in QuickBooks, and tax accounts must exist in Business Central before taxed transactions post.

• Review before posting. Migrated transactions arrive with the status Unposted. Markups and discounts are added manually, and beginning balances must be verified because QuickBooks does not store the current balance for all accounts.

• Desktop exporter versions. The Microsoft Data Exporter Tool for Desktop currently works only with QuickBooks 2017 and 2018. Both are older than the 2023 release Intuit discontinued after 2026-05-31.

Microsoft does not document an exporter for current Desktop releases, so for those the practical route is likely the default configuration package. It imports master data and some transactional data, can be prepared in Excel and is validated before it is applied. The migration scope Bitta Apps agrees includes the chart of accounts, dimensions, customers, vendors, items, open documents, unapplied payments and opening balances as of the cutover date. How much closed history moves is scoped separately: either an agreed migration or an accessible archive. Do not assume a canceled QuickBooks subscription keeps permanent read-only access. Historical migration is listed in the Complex band on the pricing page, so it is a scoping decision with a cost. Treat inventory as a separate step: quantities and values both have to agree with QuickBooks at cutover.

How long the migration takes and how to time it

Bitta Apps publishes a typical implementation range of 8 to 16 weeks on its Business Central implementation page as a planning range, not a promise. The published sequence:

1. Discovery and scoping, with a written fixed-price proposal within five business days of the scoping call. When detailed analysis is needed, a paid assessment is agreed first.

2. Configuration and build, weeks 1 to 8.

3. Data migration and training, weeks 6 to 12.

4. Go-live, then 30 days of hypercare, weeks 8 to 16.

Each engagement has a named engagement lead, a project manager and QA. New requirements go through a written change order.

A fiscal year start is the simplest cutover point, because opening balances and year comparisons line up, and a quarter start is the next best option. Count back from that date: scoping, a paid assessment where one is needed, and 8 to 16 weeks of implementation mean starting four to five months ahead. If you are on a discontinued Desktop release and a go-live is months away, compare that gap against the interim upgrade Intuit offers. Running unsupported software for a full project is the option to avoid.

Next step. If the test returned one or more structural signs, the next step is a written scope, not a software demo. Book a free discovery call and leave with a written plan for the next step. Where detailed analysis is needed, that next step is a paid migration assessment, which maps what migrates and what stays in the archive. To request one, use the short form on the QuickBooks to Business Central page: a Business Central consultant replies within one business day. If the test returned none, stay on a supported QuickBooks edition and run it again in a year. Prefer the phone: (626) 766-9732.