How to Migrate to Business Central from QuickBooks: A Practical Guide
To migrate to Business Central from QuickBooks, clean and map your chart of accounts, export customers, vendors, items and balances, then run Business Central’s built-in Data Migration guide in a test company. Reconcile every balance, rehearse the cutover, and go live at a month-end. Most teams bring in a partner for opening balances and training.
Introduction
I’ve watched plenty of finance teams reach the same point with QuickBooks. The books still balance, but the workarounds keep multiplying. Inventory lives in a spreadsheet, approvals happen in email, and month-end depends on one person who knows which export to trust.
This guide shows you how to migrate to Business Central from QuickBooks while keeping your history, your reporting and your close schedule intact. I’ll cover what the built-in tools move in a QuickBooks to Business Central migration and what they leave behind, a realistic timeline, what it costs, and the mistakes I see most often. I’ll also point out where a Business Central implementation partner earns their fee and where you can safely handle the work yourself.
A QuickBooks to ERP upgrade is a process project with a data project inside it. Treat it like any other legacy system replacement: the software is the easy part. Deciding how your accounts, dimensions and approvals should work is where the weeks go.
Why Are Businesses Switching From QuickBooks to Business Central?
Businesses switch because QuickBooks is built for small-business bookkeeping, while Business Central is a full ERP with inventory control, multi-company accounting, approval workflows and deeper reporting in one system. In my experience, switching from QuickBooks is rarely about one missing feature. Growth stacks small limits on top of each other until the workarounds cost more than the software.
These are the signs I treat as a real trigger:
- You keep a second tool, usually spreadsheets, for inventory, production or project costing.
- You run more than one legal entity and consolidate by hand every month.
- Your chart of accounts keeps growing because accounts are standing in for dimensions.
- Auditors or lenders want controls QuickBooks can’t enforce, like approvals and segregation of duties.
- Closing the month takes more than a week.
Once you add integrations, custom reports or approval workflows, the project grows well past installation. That’s why Business Central implementation services usually cover design, data and training, not just setup.
Some of the triggers are hard limits, not preferences. Intuit publishes QuickBooks Online usage limits by plan. The lower tiers cap the chart of accounts at 250 accounts, Plus allows 40 combined classes and locations, and Advanced tops out at 25 billable users. Business Central has no equivalent account cap, and dimensions replace most of what classes and locations do.
Here’s how the two systems compare on the points that usually drive a move from QuickBooks to Business Central.
| Area | QuickBooks | Business Central |
| Built for | Small-business accounting | Growing businesses that need ERP |
| Inventory | Simple tracking, limited costing | Several costing methods, locations and warehouse control |
| Reporting dimensions | Classes and locations | Dimensions across accounts, items and documents |
| Multiple companies | Separate files or subscriptions | Multi-company setup and consolidation |
| Approvals | Limited workflows | Workflow-based approvals |
None of this makes QuickBooks a bad product. It does the job well for plenty of companies, and if you’re comfortable inside its limits, staying put is a fair answer. A QuickBooks to ERP upgrade makes sense when the workarounds, not the license price, become your biggest cost.
What Data Moves in a QuickBooks to Business Central Migration, and What Doesn’t?
Business Central’s built-in QuickBooks migration extensions move master data: customers, vendors, items and general ledger accounts. Closed historical transactions, attachments, payroll records and custom reports don’t move in detail, so you plan opening balances and archiving separately.
Microsoft ships two extensions inside the Data Migration assisted setup guide, one for QuickBooks Desktop and one for QuickBooks Online. You start them by searching for Assisted Setup in Business Central and choosing Migrate business data. The QuickBooks data migration extension for desktop relies on a Microsoft exporter tool that pulls your data into a zip file, and the documentation I reviewed lists only older desktop versions as supported, so check yours before you build a plan around it. QuickBooks Online connects from inside the wizard with no export tool.
| Data | What to expect | What you still do |
|---|---|---|
| Customers, vendors, items | Migrates | Merge duplicates before the run |
| Chart of accounts | Migrates when every account has a number | Map to your new structure |
| Open invoices and bills | Depends on version and setup | Review as unposted entries before posting |
| Closed history | Does not migrate in detail | Archive it or load summaries |
| Attachments and memos | Do not migrate | Export and store them |
| Payroll | Does not migrate | Keep your provider and connect it |
| Custom and memorized reports | Do not migrate | Rebuild in Business Central or Power BI |
| Bank feeds and reconciliations | Do not migrate | Reconnect and start fresh |
A few details trip people up during a QuickBooks to Business Central migration. Every QuickBooks account needs an account number, because the Business Central general ledger requires one. If your transactions carry sales tax, you need tax jurisdiction accounts in Business Central before anything posts. Migrated transactions arrive unposted so you can review them, and QuickBooks Online doesn’t store a current balance for every account, so expect to correct some beginning balances by hand. Partial payments, markups and discounts also need manual attention. Think of the wizard as the start of your business central data migration, not the finish line.
What Should You Prepare Before You Start? An ERP Migration Checklist
Before you touch the migration tool, lock your scope, clean your lists, number and map your accounts, and name an owner for every data set. This ERP migration checklist covers the part teams rush, and it decides how clean your first month in Business Central feels.
- Pick a cutover date. A month-end works, a quarter-end is better, and the start of a fiscal year is best because one year never gets split across two systems.
- Run baseline reports from QuickBooks: trial balance, aged receivables and payables, and inventory valuation. These are the numbers you reconcile against later.
- Merge duplicate customers, vendors and items, and deactivate anything nobody has touched in two years.
- Number every account and tidy the structure. If you have accounts like “Marketing East” and “Marketing West”, that’s a dimension waiting to happen.
- Decide what replaces classes and locations. In Business Central that’s dimensions, and the design affects every report you build.
- Write down your sales tax setup, including jurisdictions, rates and exemptions, so the tax accounts are ready before posting.
- List every integration: bank feeds, payroll, e-commerce, expense tools and time tracking. Each one needs a plan, not just a mention.
- Agree on an inventory costing method. QuickBooks Online tracks inventory first-in, first-out and QuickBooks Desktop uses average cost, while Business Central lets you choose a costing method per item.
- Define users, roles and permissions, including who approves what.
- Give every data set a named owner and a sign-off, so “who checks the AR aging?” never goes unanswered.
Print this ERP migration checklist, put a date next to every line, and review it weekly.
How Do You Migrate to Business Central from QuickBooks Step by Step?
Migrating from QuickBooks to Business Central runs in eight steps: set scope, clean and map data, build a test company, run the migration, load opening balances, reconcile, train and run in parallel, then cut over. Skipping the test company is the shortcut that costs the most.
Step 1: Set the scope and the cutover date
Decide which areas go live on day one. Finance, sales, purchasing and inventory is a common first wave, with manufacturing, projects or e-commerce syncs added later. A smaller first release finishes faster and gives your team an early win. Get the controller and operations lead to sign off on the scope.
Step 2: Clean the data and map the accounts
Work from your baseline reports. Build a simple mapping sheet with three columns: the QuickBooks account, the Business Central account, and any dimension values. Do the same for customers, vendors and items. That sheet becomes your audit trail when someone asks why a balance looks different in the new system.
Step 3: Build a test company
Set up a sandbox or test company in Business Central with your real chart of accounts, posting groups, number series, currencies and tax setup. Configure it the way production will look. A rehearsal in a half-built environment proves nothing.
Step 4: Run the Business Central data migration
Start the Data Migration assisted setup guide, pick the QuickBooks extension that matches your version, and upload or connect your data. Microsoft’s training module on business central data migration covers the wizard, data templates and Excel imports, and it’s worth an hour from whoever owns the project. Review the unposted entries, fix mapping errors, and run the whole thing again until the results stop surprising you.
Step 5: Load opening balances
Load balances as of the cutover date. Use general journals for the trial balance, open customer and vendor items by invoice, and an item journal for inventory quantities and cost.
Step 6: Reconcile and test
Compare the Business Central trial balance to QuickBooks line by line. Then check AR and AP agings, inventory valuation and a sales tax report. Have real users run real scenarios: post an invoice, receive a purchase order, apply a payment, close a period. Log every defect and retest after each fix.
Step 7: Train users and run in parallel
Train by role, not by feature. AP clerks need the purchase invoice workflow, while sales staff need quotes and orders. If you can afford it, run both systems through one full month-end so you see the differences before they matter.
Step 8: Cut over and close the first month
Freeze QuickBooks entries at the cutover time, take a final backup, load the final balances and go live. Then watch the first close closely. In the first 30 days after you move from QuickBooks to Business Central, I’d review open items weekly, reconcile the bank daily at first, and keep QuickBooks read-only so nobody posts to it out of habit.
How Should You Handle Opening Balances and Historical Data?
In most QuickBooks to Business Central migration projects, companies load opening balances as of the cutover date and keep QuickBooks as a read-only archive for history. Loading full transaction history is possible, but it adds cost, risk and reconciliation work that rarely pays back.
| Approach | What you load | Best for |
|---|---|---|
| Balances only | Trial balance, open AR and AP, inventory on hand | Most small and mid-sized companies |
| Balances plus summaries | The above plus monthly prior-year totals by account | Teams that need year-over-year reporting |
| Full history | Every transaction, with mapping and reconciliation | Audit-heavy situations, ideally with a partner |
If year-over-year comparisons matter, load monthly summary entries by account for the prior year. It keeps your finance team out of two systems for every board report.
Keep the QuickBooks file, or a full export of it, after go-live. The IRS record retention rules generally tie how long you keep records to the period of limitations on your return. That’s three years in the usual case and longer in some situations, such as seven years for bad debt deductions and at least four years for employment tax records. I’m not your accountant, so confirm the right period with your CPA.
How Long Does It Take, and What Does It Cost to Migrate to Business Central from QuickBooks?
A finance-focused move from QuickBooks to Business Central commonly takes about 8 to 12 weeks, while inventory-heavy or multi-entity projects often run four to six months or longer. Those are my planning ranges, not promises, because your data quality and how fast you make decisions move the schedule more than the software does.
Cost has three parts. The first is licensing. Microsoft’s US list prices are currently about $80 per user per month for Essentials and $110 for Premium, with Team Member licenses around $8, all billed annually. Premium adds manufacturing and service order management, so most distribution, services and retail businesses start on Essentials. Prices change, so confirm current figures before you budget.
The second is partner time, which follows scope. The cleaner your data and the fewer your integrations, the less you’ll pay. The third is your own team’s time. Your controller and operations lead will spend real hours on mapping, testing and training, and that cost is easy to forget. I usually advise holding a contingency of 15 to 20 percent. That’s a rule of thumb, not a quote.
Should You Handle the QuickBooks to Business Central Migration Yourself or Hire a Partner?
You can migrate to Business Central from QuickBooks yourself only if you run one entity, carry little or no inventory, keep a clean chart of accounts, and have someone who has configured Business Central before. In every other case, a partner usually pays for themselves by preventing rework.
The risk in any business central data migration isn’t the wizard. It’s everything around it: posting groups, dimensions, tax, opening balances, integrations and training. Those are design decisions, and mistakes there show up months later as reports that don’t reconcile. If you’d rather have specialists own the build, the integrations and the support afterward, look at what Dynamics 365 Business Central consulting covers before you shortlist anyone.
Whoever you talk to, ask for recent QuickBooks migrations, who specifically will lead yours, and how they handle opening balances. If the answer to that last question is vague, keep looking.
What If You’re Moving From Dynamics GP or Sage Instead?
The principles stay the same, but the tooling differs. Dynamics GP has a Microsoft-documented path into Business Central, while a Sage to Business Central migration usually relies on exports, configuration packages or a partner’s migration tool rather than a one-click wizard.
Dynamics GP to Business Central: Plan Around the 2029 Date
GP comes with a deadline. Microsoft has set the end of product support and updates for GP at December 31, 2029, with security patches running to April 30, 2031, and it points GP customers toward Business Central. If you’re planning Dynamics GP to Business Central, Microsoft’s end-of-support announcement is the date to build backward from. GP environments tend to carry more history, customizations and integrations than a typical QuickBooks file, so this kind of legacy system replacement needs a longer runway.
Sage to Business Central Migration: Expect More Mapping
For Sage, run the project the way you’d run a QuickBooks move, but expect more scripting and mapping work. Sage editions differ widely, so ask early which extraction method fits yours. Whatever the source, the habits that matter don’t change: clean master data, a mapping sheet, a test company and a hard reconciliation. A Sage to Business Central migration fails for the same reasons a QuickBooks one does.
What Mistakes Should You Avoid When Switching From QuickBooks?
The costliest mistakes in a QuickBooks to Business Central migration are migrating dirty data, copying the old chart of accounts one for one, skipping a test run and underestimating training. Each one is cheap to avoid early and expensive to fix after go-live.
- Moving everything. Years of dead customers and items follow you into the new system. Clean first, load second.
- Cloning the chart of accounts. Business Central is built around dimensions, so a 400-account chart can often shrink while reporting gets better.
- Skipping the sandbox. A first run on production data is how duplicate balances get posted.
- Ignoring sales tax. Missing tax jurisdiction accounts block posting on cutover day.
- Forgetting the integrations. Bank feeds, payroll and e-commerce syncs fail quietly, and you find out when the numbers drift.
- Treating training as a one-hour demo. Users who don’t trust the new system build spreadsheets around it.
Key Takeaways
- A QuickBooks to Business Central migration moves master data through built-in extensions for QuickBooks Desktop and QuickBooks Online, not full history.
- Clean data and a mapping sheet matter more than any tool in a QuickBooks to ERP upgrade.
- Use an ERP migration checklist to lock scope, clean data and assign owners before you run anything.
- For most companies, opening balances at a month-end or year-start cutover beat loading full history.
- Test in a sandbox, reconcile against baseline reports, and run one parallel close if you can.
- Plan on roughly 8 to 12 weeks when you migrate to Business Central from QuickBooks with a finance-focused scope, and longer when inventory or multiple entities are involved.
- Bring in a partner when posting groups, dimensions, tax or integrations get complicated.
- Dynamics GP to Business Central projects have a December 31, 2029 support date to plan around.
Conclusion
Like any legacy system replacement, moving off QuickBooks is less about the wizard and more about the decisions around it: how your accounts map, how much history you carry, when you cut over and who signs off on the numbers. Get those right before you migrate to Business Central from QuickBooks, rehearse in a test company, and the go-live itself is surprisingly calm.
If you’d like a second pair of eyes on your scope, mapping sheet or cutover plan, the team at Newiz Tech can help through its Microsoft Dynamics 365 Business Central services.
Frequently Asked Questions
Can you migrate from QuickBooks to Business Central directly?
Yes. Business Central includes built-in data migration extensions for QuickBooks Desktop and QuickBooks Online. They bring over customers, vendors, items and general ledger accounts through the Data Migration assisted setup guide. Closed history, attachments, payroll and custom reports need separate handling.
How long does it take to migrate to Business Central from QuickBooks?
A finance-focused QuickBooks to Business Central migration usually takes about 8 to 12 weeks from scoping to go-live. Inventory-heavy, multi-entity or integration-heavy projects often run four to six months or more. Data quality and decision speed matter more than the tool.
How much does it cost to move from QuickBooks to Business Central?
Budget for three things: licenses, partner time and your own staff’s time. Microsoft’s US list prices are currently about $80 per user per month for Essentials and $110 for Premium, billed annually. Partner cost depends on scope, data quality and integrations, so fix the scope before comparing quotes.
Will I lose my QuickBooks history?
Not if you plan for it. Most companies load opening balances at cutover and keep QuickBooks as a read-only archive. If you need year-over-year reports, load monthly prior-year summaries by account. Keep the file or an export as long as tax and audit rules require, and confirm that period with your CPA.
Are QuickBooks Desktop and QuickBooks Online migrated the same way?
Not exactly. Both use extensions inside the Data Migration assisted setup guide, but desktop data comes through a Microsoft exporter tool that creates a zip file, while QuickBooks Online connects from inside the wizard. Supported versions differ, so check which ones Microsoft currently lists before you set your timeline.
Do I need a partner to migrate from QuickBooks to Business Central?
Not always. A single-entity company with no inventory and a clean chart of accounts can often run the wizard in-house. Once you add inventory, multiple entities, custom reports or integrations, a partner helps prevent rework in posting setup, dimensions and opening balances.
When is the best time to cut over?
At a month-end, ideally a quarter-end or the start of a fiscal year. A clean boundary means you reconcile one set of balances and avoid splitting a reporting period across two systems. Avoid year-end close, peak season and audit weeks.
Should I keep QuickBooks after going live?
Keep it read-only for history, at least through your first full close and for as long as your retention needs require. Cancel the subscription only after you’ve reconciled, archived an export, and confirmed nobody still relies on it for reports, payroll or tax filing.
How do QuickBooks classes and locations map to Business Central?
They map to dimensions. In Business Central you attach dimension values such as department, location or project to accounts, items and documents, then report on any combination. Design your dimensions before migrating, because they shape your chart of accounts and every report you build afterward.
Is switching from QuickBooks to Business Central worth it for a small business?
It depends on complexity. If QuickBooks still covers your inventory, entities and reporting without workarounds, staying put is a fair choice. If you’re juggling spreadsheets, hitting plan limits or needing approvals and multi-company reporting, Business Central usually justifies the higher cost.
