QuickBooks to Business Central Migration: A Practical Checklist

Most companies start looking at Microsoft Dynamics 365 Business Central when QuickBooks stops keeping up: inventory lives in spreadsheets, month-end takes too long, multiple entities are consolidated by hand, or the auditors keep asking for things the system cannot produce. Business Central solves those problems, but only if the move is planned as a redesign rather than a file transfer.

Below is the checklist we use on QuickBooks migrations. It applies whether you are on QuickBooks Online or QuickBooks Desktop.

1. Decide what you are migrating, and what you are not

The first decision is scope. A migration that tries to bring every historical transaction across is slow, expensive and usually unnecessary. A common approach is:

• Master data: customers, vendors, items, and fixed assets, cleaned and de-duplicated.
• Open items: open customer invoices, open vendor bills, open purchase and sales orders, and current inventory quantities and values.
• Balances: general ledger balances at cutover, plus monthly net-change history for the current and prior fiscal year so you can run comparative reports.
• Archive: the QuickBooks file itself, kept read-only for detailed historical lookups.

Write this down and get the controller or CFO to sign it. It prevents scope creep in the middle of the project.

2. Redesign the chart of accounts and dimensions

QuickBooks charts of accounts tend to grow sideways: separate accounts for each location, department or product line. Business Central handles that with dimensions, so the ledger can stay lean while reporting gets richer.

• Map every QuickBooks account to a new Business Central G/L account.
• Move departments, classes and locations into global and shortcut dimensions.
• Agree on default dimension rules for customers, vendors and items so the right values flow onto every posting automatically.
• Set up posting groups (general business, general product, customer, vendor, inventory) before any data is loaded, because they drive where every transaction lands in the ledger.

3. Clean the data before you move it

Data cleanup is the part everyone underestimates. Typical issues in a QuickBooks file include duplicate customers, inactive vendors with open balances, items with no cost, and inconsistent units of measure. Export each list to Excel, clean it there with the business owners, and only then load it.

We load master data with RapidStart configuration packages, which validate each field against Business Central's rules and let you reload as many times as needed during testing. Load order matters: setup tables and posting groups first, then customers and vendors, then items, then open documents and balances.

4. Design the processes, not just the data

Business Central does things QuickBooks never did, such as purchase approvals, warehouse picks, item tracking, landed cost, and multi-entity consolidation. Decide which of those you need on day one and design them properly. If you are a distributor, that means warehouse setup. If you manufacture, it means bills of materials and routings. If you run projects, it means the Projects (Jobs) module and how time and expenses flow to invoices.

5. Plan the cutover

• Pick a cutover date, ideally the first day of a month or fiscal period.
• Freeze master data changes in QuickBooks a few days before.
• Close the last period in QuickBooks and reconcile it.
• Load opening balances and open documents into Business Central and reconcile them to QuickBooks: trial balance, AR aging, AP aging and inventory valuation should all tie out to the penny.
• Run at least one full mock cutover in a sandbox environment before go-live.

6. Test with real transactions

User acceptance testing should follow real scenarios end to end: quote to cash, procure to pay, inventory receipts and adjustments, bank reconciliation and a month-end close. Have the people who will do the work run the tests, not the consultants.

7. Train, go live, and support the first close

Train by role, using your own data in a sandbox. Then plan for hands-on support through the first month-end close, which is where most remaining issues appear. Reconcile the first close in detail and fix setup issues while they are still small.

Common mistakes to avoid

• Copying the QuickBooks chart of accounts one-for-one instead of using dimensions.
• Bringing over years of transaction detail that nobody will use.
• Skipping the mock cutover.
• Treating inventory as an afterthought, when it usually drives most of the setup decisions.

Need help with your migration?

ERPLO has moved companies from QuickBooks, Dynamics GP, Dynamics NAV and other legacy systems to Business Central. Read more about our QuickBooks and legacy ERP migration service, or talk to an architect about your situation.