The QuickBooks Migration Checklist That Catches What the Export Tool Won't Tell You
Quick Summary: This guide walks through the full QuickBooks migration process — Desktop to Online, Desktop to Enterprise, Desktop to Intuit Enterprise Suite (IES), or QuickBooks Online Advanced to IES — with a real pre-migration, during-migration, and post-migration checklist. It's built for business owners, controllers, and finance leads who want to know what actually transfers, what commonly breaks, and how long the process really takes before they commit. If you'd rather have someone run this checklist for you, book a free consultation with our QuickBooks migration team.
Migrating QuickBooks feels like it should be simple: click export, pick a destination, wait. And for a narrow set of businesses; clean books, one entity, no custom reports, small file it mostly is. For everyone else, the export button is the easy 10% of the job. The other 90% is the cleanup, the reconciliation, and the "wait, where did our custom price levels go" phone call that happens three weeks later.
This guide is written for U.S.-based business owners, controllers, and finance leaders evaluating a move within the QuickBooks ecosystem in 2026; whether that's QuickBooks Desktop to QuickBooks Online, Desktop to QuickBooks Enterprise, Desktop to Intuit Enterprise Suite, or QuickBooks Online Advanced to IES. It's put together by Certum Solutions, an Elite Intuit Partner and top U.S.A. QuickBooks ProAdvisor firm.
What makes this checklist different from most: it doesn't stop at "click export." It tells you what doesn't transfer, where file-size limits quietly cause data discrepancies, and which situations are not good candidates for a DIY migration, because getting that wrong costs far more than the migration itself.
Why QuickBooks Migrations Go Wrong (Even When the Export "Works")
Most QuickBooks migrations don't fail at the export step. They fail two to six weeks later, when someone notices the Balance Sheet doesn't match, payroll history is missing, or a custom report the CFO relied on every month simply doesn't exist anymore.
That gap happens because Intuit's migration tools are genuinely good at moving data, but they don't redesign anything. Whatever mess existed in your old chart of accounts, your class structure, or your item list gets carried over intact into the new platform. A migration tool will faithfully replicate a broken system. It won't fix it.
What "Migrating QuickBooks" Actually Means
"QuickBooks migration" isn't one process; it's four different processes with different tools, different limits, and different failure points:
QuickBooks Desktop (Pro/Premier/Enterprise) → QuickBooks Online
QuickBooks Desktop → QuickBooks Enterprise (version upgrade or server migration)
QuickBooks Desktop or QuickBooks Online Advanced → Intuit Enterprise Suite (IES)
QuickBooks Online → QuickBooks Online Advanced or a new QBO company
This checklist covers all four, because the "which path am I even on" question is where a lot of business owners get stuck before they've done anything else. If you're specifically comparing QBO Advanced against IES as platforms rather than planning a move, our QuickBooks Online vs. Intuit Enterprise Suite breakdown covers that decision in more depth.
Not sure which migration path fits your business?
Before You Touch Anything: The Pre-Migration Checklist
Every migration path shares the same starting requirements. Do these before you open any export tool.
Update QuickBooks to the latest release (Desktop and Online both push migration-relevant fixes regularly)
Back up your company file in full and store the backup somewhere outside the file you're about to touch
Reconcile every bank and credit card account through your most recent statement
Merge duplicate customers, vendors, and items — duplicates migrate as duplicates
Inactivate unused chart of accounts entries, items, and list entries you don't need going forward
Clear or document unapplied payments, open credits, and unresolved AR/AP
Export and save your key reports as PDFs before you migrate: Balance Sheet, Profit & Loss, AR Aging, AP Aging, and Payroll Summary — these become your verification baseline
Confirm your file size and "targets" (Desktop's internal record count) — check by pressing F2 or Ctrl+1
Gather every login: Intuit account credentials, bank feed connections, payroll service info, and any connected apps (Shopify, Cin7, payment processors, etc.)
Confirm who has Primary Admin access — you need this to run any migration
That last item stops more migrations than anything else on this list. If nobody currently has Primary Admin access confirmed, that's step zero.
Worth knowing before you manually chase every item on this list: the migration tool itself catches some of this automatically. It flags chart-of-accounts entries with no transaction data behind them, and it can mark older vendors and customers that haven't been used in a while as inactive during the conversion. That's a real time-saver; but it's basic housekeeping, not a reconciliation. It won't catch mismapped inventory items or tell you whether a "used" account has the right balance. Treat it as a head start, not a substitute for reviewing your file first.
How to Migrate QuickBooks Desktop to QuickBooks Online
The built-in export path
For QuickBooks Desktop Pro or Premier (2022 or newer), the migration tool lives inside the software: go to the Company menu, select "Migrate this company file to QuickBooks Online," then "Export Your Company File to QuickBooks Online." You'll get a personalized pre-flight checklist inside the tool itself — it walks through tasks like reviewing employee information if you run payroll, then lets you choose between bringing all company data or only lists and balances. QuickBooks
QuickBooks Desktop Enterprise uses a different path entirely: press Ctrl+1 to open Product Information, then Ctrl+B+Q, then OK, then follow the same "bring all data" or "lists and balances only" choice.
The limits nobody mentions until you hit them
Desktop-to-Online migrations are capped by file size and "target" count. Files approaching or exceeding roughly 750,000 targets used to run into data discrepancies, particularly in inventory. "The tool has genuinely gotten better at handling files over 750,000 targets than it used to be," Travis says. "I've also seen hosted environments running versions that were never updated, which brings the old limitations right back. Check your version before you assume the improvements apply to you."
What doesn't come with you
Plan for these gaps in advance rather than discovering them after the fact:
Custom report templates and memorized reports
Price levels
Most payroll history and payroll-specific setup (payroll typically needs to be reconfigured, not migrated)
Some third-party app integrations, which need to be reconnected and reconfigured on the new platform
One more thing that catches DIY migrations off guard: the migration tool moves accrual-basis balances. QuickBooks Desktop and QuickBooks Online calculate cash-basis reporting differently under the hood, so a Balance Sheet that matches perfectly on an accrual basis right after migration can still look different on a cash basis. That's not necessarily an error; but it needs to be understood and reconciled, not assumed away.Our QuickBooks Desktop setup support →
Migrating QuickBooks Desktop to Online yourself?
We'll run the pre-migration cleanup and verify the numbers match before you go live.
How to Migrate QuickBooks Desktop to QuickBooks Enterprise
Version upgrades and server migrations within Desktop Enterprise carry a different risk profile than moving to the cloud; the data usually stays in the same file format, but hardware, multi-user setup, and add-on integrations (barcode scanners, EDI, manufacturing add-ons) are where these migrations go sideways. Before upgrading, confirm every connected add-on is certified for the new Enterprise version, not just "compatible"; those aren't the same thing. Rebuild and verify your data file before the upgrade, not after something breaks. QuickBooks Enterprise setup and support →
How to Migrate to Intuit Enterprise Suite (IES)
From QuickBooks Online Advanced
Intuit's own guidance is that if you're upgrading from QuickBooks Online, your data is automatically migrated to Intuit Enterprise Suite with no additional work required. That's accurate; and it's also the trap. An automatic migration preserves everything, including years of chart-of-accounts cruft, one-off accounts nobody remembers creating, and class structures that were built as a workaround because QBO Advanced couldn't do true dimensional reporting. IES supports real dimensions. Migrating a class-based workaround into a dimension system doesn't fix the underlying problem; it just relocates it into a more powerful platform where it's harder to untangle later.
From QuickBooks Desktop Enterprise
This path has more variables: how much history you want to bring over, whether you're consolidating multiple entity files into one IES account, and how your current chart of accounts needs to be redesigned to take advantage of IES's multi-entity and consolidated reporting features. Migration specialists generally agree that Desktop-to-IES conversions wrap up quickly only when the scope, chart-of-accounts design, and integration priorities are locked down before the migration starts — not decided mid-process. For a full walkthrough specific to this path, see our step-by-step Intuit Enterprise Suite migration guide →
What Actually Transfers (and What You'll Need to Rebuild)
| Usually transfers | Usually needs rebuilding |
|---|---|
| Customers, vendors, chart of accounts | Custom report templates |
| Open invoices and bills | Price levels |
| Items and product/service lists | Payroll setup and history |
| Historical transactions (within file limits) | Some third-party app connections |
| Balances | User permission structures |
Common QuickBooks Migration Mistakes That Create Months of Cleanup
Migrating without a clean baseline — if the old file was already wrong, the new file inherits every error
Skipping the reconciliation step, so bank feed setup starts from an unreconciled position
Not documenting the old chart of accounts before migrating, making it impossible to verify anything mapped correctly
Assuming payroll "comes with" the migration and finding out during a pay run that it didn't
Migrating multiple entities into one file (or vice versa) without a deliberate consolidation plan
Going live without a parallel-run or verification period against the old system
If your books were already messy before you started thinking about migration, cleanup should happen first — not after.
The Post-Migration Checklist: How to Verify It Actually Worked
"When we ran migrations at Intuit, verification typically meant comparing the Profit & Loss and Balance Sheet across all dates, and the file went over as-is; mapping issues included," says Travis Dennison, Certum's QuickBooks Migration Specialist and a former Intuit migration expert. That's not a knock on the tool; it's simply the scope of what an automated migration checks. It confirms the totals moved. It doesn't confirm your inventory mapped to the right items or that payroll is ready for your next run. Whatever process you use, treat "the migration completed" and "the migration is correct" as two separate questions. Don't consider a migration done just because the export finished. Verify it:
Compare Balance Sheet, Profit & Loss, and AR/AP Aging in the new system against the PDFs you saved before migrating
Confirm bank feeds are connected and pulling correctly
Test at least one full transaction cycle: invoice → payment → deposit
Reconnect and test every third-party integration (payments, inventory, e-commerce)
Confirm payroll is fully reconfigured before running your next payroll, not during it
Set user permissions and confirm who has admin access in the new system
Keep the old file/backup accessible for at least one full fiscal year for audit and historical lookup purposes
Who Should NOT Migrate QuickBooks Themselves
Most migration checklists stop at "here's how to do it." Here's when not to.
Skip the DIY route if any of these apply to your business:
Your file is close to or over the 750,000-target threshold, especially with active inventory
You run payroll and can't afford a gap or error in an upcoming pay cycle
You operate multiple entities and are consolidating, splitting, or restructuring as part of the move
Your chart of accounts hasn't been reviewed in years, and you know it's carrying errors
You're migrating to Intuit Enterprise Suite and want to actually use its dimensional reporting, not just relocate your old class structure
You don't currently have someone who can verify a Balance Sheet matches before and after
The migration tool does some of the work for you; it'll clean up empty chart-of-accounts entries and inactivate old vendors and customers on its own. What it won't do is catch a mismapped inventory item, reconcile a cash-basis discrepancy, or tell you your payroll setup is incomplete before your next pay run. If your risk lives in those areas rather than basic list housekeeping, the tool's automation doesn't cover you.
None of this means migration is a bad idea; they mean it's not a same-day, DIY project. This is exactly the gap between "the export finished" and "our books are actually right," and it's the part a migration tool can't do for you. QuickBooks managed support →
Certum Solutions is an Elite Intuit Partner and top 5% QuickBooks ProAdvisor firm. Our migration specialists have years of experience running these exact migrations and know where they break, before they break.
How Long Does a QuickBooks Migration Actually Take?
The honest answer: the data transfer itself is usually fast; the surrounding work is what takes time. Intuit states most QuickBooks Desktop migrations to Intuit Enterprise Suite complete within 72 hours, and QuickBooks Online upgrades to IES happen with effectively zero downtime. But that clock only covers the technical transfer; not the pre-migration cleanup, chart-of-accounts redesign, payroll reconfiguration, or the verification period that determines whether the migration actually holds up. Budget days for the export. Budget weeks for doing it right.
QuickBooks Migration Checklist FAQ
Do I need to hire someone to migrate to QuickBooks, or can I do it myself?
You can migrate QuickBooks yourself if your file is small, clean, and doesn't involve payroll, multiple entities, or heavy inventory. Once any of those factors are present, the risk of a costly reconciliation error goes up significantly, and most businesses save money by having it done correctly the first time.
How long does a QuickBooks Desktop to QuickBooks Online migration take?
The technical export usually completes within a day, but most businesses should budget one to three weeks total once pre-migration cleanup, verification, and payroll reconfiguration are included.
Does payroll history transfer when I migrate to QuickBooks?
No, not automatically. Payroll typically needs to be reconfigured on the new platform, and historical payroll data often needs to be handled separately from the core company file migration.
What happens if my QuickBooks Desktop file is too large to migrate?
Files approaching or exceeding roughly 750,000 targets can experience data discrepancies, particularly in inventory, and may need a phased or professionally managed migration rather than a single-pass export.
Can I migrate from QuickBooks Online directly to Intuit Enterprise Suite?
Yes — Intuit automatically migrates QuickBooks Online data into Intuit Enterprise Suite. The technical move is simple; the strategic work is deciding whether to carry forward your existing chart of accounts and class structure or rebuild them to use IES's dimensional reporting properly.
What doesn't transfer when I migrate QuickBooks Desktop to Online?
Custom report templates, price levels, most payroll history, and some third-party app connections typically don't transfer automatically and need to be rebuilt or reconnected after migration.
Is QuickBooks Desktop still supported in 2026?
Yes, but only if you already have an active subscription. Intuit stopped selling new Desktop subscriptions (Pro, Premier, Mac Plus) in September 2024, so you can no longer buy Desktop as a new customer. If you're already subscribed, you keep getting features, security updates, and support for the length of your current term; QuickBooks Desktop 2023 subscribers lost that on May 31, 2026, as their term ended. Desktop isn't gone yet, but the new-sales freeze is the clearest signal Intuit is phasing it out over time, which is why most Desktop users should have a migration plan in place rather than waiting for support to lapse.
How do I verify a QuickBooks migration actually worked?
Compare your Balance Sheet, Profit & Loss, and AR/AP Aging reports in the new system against the exact same reports pulled from the old system before you migrated. Any variance needs to be explained, not assumed away.
What's the difference between migrating to QuickBooks Enterprise versus Intuit Enterprise Suite?
QuickBooks Enterprise is still a single-entity Desktop product with add-on modules; Intuit Enterprise Suite is a cloud platform built for multi-entity consolidation, dimensional reporting, and automated intercompany transactions. If you're outgrowing Enterprise, IES is usually the more future-proof path rather than another Enterprise upgrade.
Should I clean up my QuickBooks file before or after I migrate?
Before. A migration tool copies your file faithfully, including every error. Cleaning up duplicates, unreconciled accounts, and chart-of-accounts issues before you migrate is significantly cheaper than fixing the same problems inside a new platform. QuickBooks Desktop 2023 service ending →
Run this checklist with a migration specialist instead of alone.