// quickbooks → business central

QuickBooks to Business Central migration. A clear plan for Online, Desktop and Enterprise.

Move finance and operations to Microsoft Dynamics 365 Business Central with a defined scope for your data, inventory and integrations. Start with a free discovery call, then a paid migration assessment when a deeper review is needed to produce a written implementation proposal.

// the facts

Start with your QuickBooks edition and business needs

Online, Desktop Pro or Premier, and Enterprise have different capabilities and service policies. These US Desktop notices are context for planning, not a reason every QuickBooks business must migrate.

QuickBooks Online

Move for operational fit

An Online migration is an ERP decision: assess entity reporting, inventory, purchasing and integrations against the cost of changing systems. A Desktop service notice does not apply to QuickBooks Online.

US Desktop subscriptions

New sales and renewals differ

Intuit ended new US Pro Plus and Premier Plus subscriptions on September 30, 2024. Its notice allows existing subscribers to renew and excludes Enterprise. This is not a blanket end date for Desktop.

Intuit's US subscription notice
Desktop 2023

Check your exact version

Intuit's Desktop 2023 policy ended support and connected services after May 31, 2026, including payroll and online banking. Check your version and subscription before choosing an upgrade or migration path.

Intuit's Desktop 2023 policy
// beyond bookkeeping

What to evaluate before moving to Business Central

Compare the processes you need with the QuickBooks edition and apps you already use. A successful migration establishes a working operating model, not just a new place to store your ledger.

Multi-entity and consolidation

Assess intercompany transactions and consolidation, then define company structures, account mapping and elimination responsibilities. Separate legal entities still need separate accounting controls.

Dimensions-based reporting

Map departments, projects and locations to dimensions. Agree the management reports and default values before importing balances so the first close answers the right questions.

Inventory and warehousing

Review locations, bins, units of measure, costing, lot or serial tracking and landed cost. Compare your current QuickBooks edition and add-ons against the warehouse processes you actually need.

Approval workflows

Design purchasing approvals around who can request, approve, receive and post. Demonstrate exceptions, amount limits and delegated approvals during testing.

Financial controls

Configure posting permissions, allowed posting dates and change logging alongside your close process. Define how corrections are approved and how finance reviews the supporting evidence.

Connected operations

Scope storefront, payment, payroll, CRM and reporting connections individually. Decide which application owns each record and how failures, refunds and reconciliation will be handled.

// how it works

How the migration works

The assessment, implementation and ongoing support are distinct commitments. Review the published pricing bands, then agree the scope, acceptance criteria and fixed fee before delivery begins.

  1. 01

    Migration Readiness Assessment: paid, scoped in writing

    A senior team reviews your source version, data quality, processes and integrations. The assessment establishes what migrates, what archives, and what gets rebuilt, with a written migration plan and implementation scope. Agree the assessment fee before work starts.

  2. 02

    Fixed-scope implementation: 8 to 16 weeks typical

    Configuration, scoped customization, and role-based training, delivered by the same team that ran the assessment, on the fixed price from the proposal, with anything new arriving only through a written change order.

  3. 03

    Validated data cutover

    Your finance lead signs off the trial balance, receivables and payables aging, bank balances and inventory quantity and value. Together we rehearse the freeze, final export, validation and go/no-go decision. History depth is separately scoped.

  4. 04

    30-day hypercare, then hour-anchored support

    The go-live team stays on for 30 days of hypercare. After that, support runs as an hour-anchored retainer with a real customer portal: tickets, approvals, and invoices in one place.

What moves, what needs review, and who signs off

Records, balances and open transactions

Agree the chart of accounts, dimensions, customers, vendors, items, open invoices and credits, unapplied payments and opening balances. Reconcile partial payments explicitly so migrated documents do not overstate the amounts still owed.

Inventory is a separate workstream

Validate quantities and values by item and location, costing methods, units, tracking requirements and in-transit stock. Decide how open receipts, shipments and orders will be finished or recreated. Importing an item list does not establish a reconciled inventory ledger.

History and connected services

Decide which closed transactions, attachments and reports need migration or an accessible archive. Payroll, payment gateways, bank connections and third-party apps need their own transition plans. Confirm archive access and subscription requirements before canceling QuickBooks.

Your responsibilities and ours

Bitta Apps owns mapping, configuration, trial loads and documented exceptions within scope. Your team supplies exports, cleans source records, makes accounting-policy decisions and approves reconciliation and user testing. Name a finance approver and an operations owner at kickoff.

Microsoft documents limits in its QuickBooks migration extension, including supported Desktop versions, order exclusions and partial-payment handling. Other scoped imports can use Business Central configuration packages. A trial migration and reconciliation establish what works for your source.

Plan the scope and budget

// two in the room

Every engagement runs with a named project manager and senior developers, at least two of us in every meeting, from discovery to go-live. The team that scopes your migration is the team that delivers it.

// faq

Honest answers, before the call

Can you migrate QuickBooks Online as well as Desktop and Enterprise?+

Yes. We assess Online, Desktop and Enterprise sources separately, including edition, country, custom fields and connected apps. The migration method is selected after sample exports and a trial load, rather than assuming the same importer supports every version.

Does Microsoft's QuickBooks migration tool move everything?+

No. Microsoft's documentation limits the Desktop exporter to QuickBooks 2017 and 2018, excludes sales and purchase orders, and warns that partially paid documents require adjustment. We verify applicability to your source and scope other exports or import methods where needed.

Can we keep our QuickBooks history?+

Yes, through an agreed migration or archive plan. We define what moves into Business Central and how your team will retrieve the rest. Do not assume a canceled QuickBooks subscription provides permanent read-only access; verify retention, exports and access with Intuit before canceling.

What does a QuickBooks-to-Business Central migration cost?+

Published implementation bands are Standard from $28,500, Extended $45,000 to $90,000, and Complex from $90,000. The Migration Readiness Assessment is $7,500, with larger scopes quoted up to $12,500. Entity count, data quality, inventory, integrations and history determine your written fixed-price scope. Licenses, third-party subscriptions and ongoing support are separate. Current offers and terms are on our pricing page.

How long does the migration take?+

A typical implementation takes 8 to 16 weeks. That is a planning range, not a deadline for every project. Data cleanup, multiple entities, inventory complexity, integrations and availability of your approvers can extend it. The assessment establishes a schedule and cutover dependencies.

We rely on Enterprise features and add-ons: advanced inventory, job costing, field tools. Do we lose those?+

We run a fit-gap review using your real workflows. Each requirement is mapped to Business Central configuration, an appropriate third-party app, or a scoped extension. Warehouse devices, field tools, payroll and specialist costing must be tested separately; they are not assumed to transfer with the accounting data.

When should we stay on QuickBooks?+

If your current edition supports your controls, reporting and operations at an acceptable cost, an ERP migration may not be justified. Start with specific process gaps, the cost of workarounds and the team's capacity for change. A free discovery call can establish whether a paid assessment is appropriate.

What happens after go-live?+

The team that built your implementation stays on it. Thirty days of hypercare are part of the scope, and ongoing support runs as an hour-anchored retainer with a customer portal: tickets, approvals, and invoices in one place, handled by the people who know your tenant.

// migration assessment

Request a migration assessment

Tell us where you are today: entity count, user count, and what's bolted onto QuickBooks. We'll come back with the assessment scope and a fixed fee, quoted in writing, before any work begins.

A senior team member replies within one business day.

+ Add project details
// next step

Plan your QuickBooks migration with scope, costs and reconciliation in writing.