How to Migrate from QuickBooks Desktop to Online in 2026 (Step-by-Step)

Here's a number that should make you pause: roughly 35% of QuickBooks Desktop users are still running versions Intuit no longer supports. No security patches. No payroll tax table updates. No payment processing on older releases. And yet they keep chugging along, quarter after quarter, because migrating feels like open-heart surgery on your accounting system.

I get it. I've walked three small businesses through this migration in the past year. One took a weekend. One took three weeks. One took two months and needed a cleanup from a ProAdvisor. The difference wasn't luck — it was preparation.

Intuit stopped selling QuickBooks Desktop to new US subscribers after September 30, 2024, and Desktop 2022 hit end-of-support in May 2025. The writing is on the wall. But before you click the Intuit "Move to Online" button, you need to know what actually transfers, what silently breaks, and whether QuickBooks Online is even the right landing spot for your books.

Let's walk through it.

Before You Migrate: Is QuickBooks Online Actually Right for You?

Don't skip this section. I've seen businesses migrate, hate the result, and pay an accountant to migrate them back out. That's a $3,000 lesson you don't need.

QuickBooks Online (QBO) is not QuickBooks Desktop with a web skin. They're genuinely different products. Some Desktop features don't exist in QBO at all. A few examples that surprise people:

• No true job costing on Simple Start or Essentials plans. You need Plus ($99/month) or Advanced ($235/month) for project profitability tracking.
• No Sales Orders. Desktop Premier and Enterprise have them; QBO doesn't. You'll work around it with estimates or invoices.
• Limited inventory. QBO uses FIFO only. If you ran average cost or LIFO on Desktop, your numbers will shift after migration.
• Batch invoicing is weaker. Power users who issue 100+ invoices a day often find QBO's batch features clunky compared to Desktop.
• User limits are hard caps. QBO Plus caps at 5 billable users. Desktop Enterprise supported 40. If your team is bigger, you need Advanced or a different platform.

On the other hand, QBO absolutely wins on: working from multiple locations, automatic bank feeds that actually keep up, app ecosystem (750+ integrations vs. Desktop's handful), and never again running backups to a USB drive.

Consider these alternatives before committing. Xero handles inventory and multi-currency better than QBO. FreshBooks is friendlier for service-based freelancers. Wave is genuinely free for businesses under $50K/year in revenue. If your Desktop pain is the desktop part — not the QuickBooks part — one of these may fit better than QBO.

Still set on QBO? Good. Keep reading.

Pre-Migration Checklist

Preparation is 70% of a smooth migration. Rush this and you'll pay for it in reconciliations. Do these in order — don't skip steps.

1. Update QuickBooks Desktop to the latest release. Open Help > Update QuickBooks Desktop. Migration tools only work on the current version and the two versions before it. Running 2019? You need to update or upgrade first.
2. Run the Verify and Rebuild utility. File > Utilities > Verify Data. If it finds issues, run Rebuild. Do this until Verify returns clean. Migrating a corrupted file is how books break silently.
3. Check your target file size. Intuit's online migration tool has a practical limit around 750,000 targets (transactions plus list items). File > Utilities > Condense Data shows your count. Over the limit? You'll need to condense historical data or split the company into multiple QBO files.
4. Reconcile every bank and credit card account. Any unreconciled transaction becomes a forensic exercise after migration. If a 2019 reconciliation is still open, close it now.
5. Print or export key reports. Profit & Loss, Balance Sheet, Trial Balance, A/R Aging, A/P Aging, and Sales Tax Liability — all as of your cutover date. You'll use these to verify the migration worked.
6. Back up the company file twice. One local, one offsite. Label them clearly: "PRE-MIGRATION MASTER — DO NOT MODIFY." You will thank yourself.
7. Record your current payroll year-to-date totals. By employee, by pay type. Payroll history transfers unreliably — more on that below.
8. Document every recurring template, memorized transaction, and custom report. Screenshot them. These don't transfer cleanly.
9. Choose your QBO subscription plan. Don't guess — match your Desktop feature usage to a QBO tier. Most Premier users end up on Plus at $99/month. Enterprise users land on Advanced at $235/month.
10. Pick a low-activity cutover date. End of month works best. End of quarter is even better. Don't migrate mid-payroll-cycle.

If your Desktop file is over 750,000 targets or has more than 3 years of bad reconciliations, stop and hire a ProAdvisor. The $500-1,500 in fees will save you weeks. I'm serious.

Step-by-Step Migration Process

Assuming your file is under the target limit and cleanly reconciled, here's the actual migration. Block out a full weekend. Don't try this on a Monday morning.

1. Sign up for QuickBooks Online. Go to quickbooks.intuit.com and start your chosen plan. Use a fresh company — don't reuse an old trial QBO account with test data in it. Trust me.
2. Inside QuickBooks Desktop, open your company file as Admin in single-user mode. Press F2 and confirm you're in single-user mode. Multi-user mode blocks migration.
3. Launch the export tool. In Desktop, go to Company > Export Company File to QuickBooks Online. If you're on Desktop for Mac, use Company > Export to QuickBooks Online (it's slightly different but similar).
4. Sign in with your Intuit account. Use the same email you used to create your QBO company. If your new QBO company doesn't appear in the list, you'll need to sign out and back in or verify you used the matching email.
5. Choose your inventory handling. You'll be asked whether to bring inventory over with FIFO starting from a specific date. Pick the date that matches when you started tracking inventory in Desktop. If you ran average cost, accept that numbers will shift.
6. Agree to the upload and wait. Small files (under 100MB) take 15-60 minutes. Large files can take 6-24 hours. You'll get an email when it's done. Don't touch either file during this period.
7. Review the migration confirmation email. Intuit sends a summary showing what moved and what didn't. Read every line. If something looks wrong, stop and investigate before proceeding.
8. Log into QBO and run the same reports you exported earlier. Compare side by side: P&L, Balance Sheet, Trial Balance, A/R Aging, A/P Aging. Totals should match to the penny. Differences usually trace to inventory valuation changes or unresolved reconciliation items.
9. Connect your bank feeds. QBO's bank feeds are different from Desktop's — they're continuous, not batch downloads. Connect each account and let 90 days of transactions flow in. Match, don't re-add, transactions that already migrated.
10. Lock the Desktop file as read-only. Rename it "COMPANY_NAME_ARCHIVED_YYYY-MM-DD.QBW" and move it to a separate folder. Your team should NOT keep entering transactions there. Pick one system and commit.

What Doesn't Transfer (And What To Do About It)

This is the section Intuit buries. Fair warning: some of these will hurt.

Payroll history. Year-to-date totals typically move, but individual paycheck details often don't. If you're mid-year, you'll need to manually re-enter historical paychecks or accept a clean-slate restart in QBO Payroll. Export your Desktop payroll reports first. Every detail. Every employee.

Memorized and recurring transactions. Templates don't transfer. You'll need to recreate every recurring invoice, bill, and journal entry in QBO's Recurring Transactions feature. Budget 1-3 hours depending on how many you have.

Budgets. They don't come over. Export your Desktop budgets to Excel, then re-enter them in QBO under Settings > Budgeting.

Custom reports. This one stings. Your carefully built Desktop reports don't migrate. QBO has different reporting logic. You'll rebuild the ones you actually use — and find that about 30% of them can't be exactly replicated.

Reconciliation reports. Historical reconciliation reports don't transfer in a usable format. Print or PDF them all before you migrate. Auditors will ask for them someday.

Audit trail details from before migration. Your QBO audit log starts fresh on migration day. Keep the Desktop file archived forever — it's your pre-migration evidence.

Closed periods and closing date passwords. Reset them in QBO under Settings > Advanced > Accounting. Set a closing date immediately after migration so nobody back-dates into your verified period.

Statement charges, some non-inventory item types, and certain price levels. Less common but still catches people. Review Intuit's official "what converts" list during your prep phase.

After Migration: The First 2 Weeks

Migration day is just the beginning. The first two weeks decide whether this goes well or becomes a horror story. Here's the checklist I give every client.

Week 1 — Verification. Compare the pre-migration Balance Sheet and P&L to the post-migration versions. Line by line. Any variance over $1 gets investigated. Check that all open invoices carry the correct balances and aging. Verify A/P — unpaid bills should have their original due dates, not the migration date.

Connect bank and credit card feeds. Re-link every account. When transactions flow in, match them against what migrated. Don't add duplicates. QBO's matching is decent but not magic — review every match during week one.

Re-create recurring templates. Build them as you need them rather than all at once. A month from now, you'll have rebuilt the ones you actually use and saved yourself work on dead templates.

Train your team on QBO. The biggest post-migration complaint isn't data loss — it's "I can't find anything." QBO's navigation is different from Desktop. Plan 2-3 hours of hands-on practice per user. Intuit's free QuickBooks Online tutorials are genuinely useful.

Reconcile fresh. Do your first post-migration reconciliation as early as possible. Bank reconciliations in QBO work differently than Desktop — start learning the workflow while transaction volume is low.

Lock the archived Desktop file. Remove desktop icons. Revoke user access. Don't let anyone sneak back to "just check something." Split-brain accounting is how books get destroyed.

Common Migration Errors and Fixes

These are the errors I see over and over. Bookmark this section.

• "File too large" error. You exceeded the 750,000 target limit. Run File > Utilities > Condense Data in Desktop to compress old transactions, or split the company into two QBO files by fiscal year.
• Balances off by a few cents. Almost always rounding on inventory items or multi-currency transactions. Create a one-line journal entry to true it up, dated migration day. Document the reason.
• Inventory quantities wrong. FIFO recalculation. Run an inventory valuation report in Desktop (before migration) and in QBO (after). Differences over 5% usually indicate a starting-date issue — you may need to redo the migration with a different FIFO start date.
• Sales tax liability doesn't match. QBO handles sales tax completely differently via its Automated Sales Tax engine. You'll need to review rates and re-configure. Don't file a return until this reconciles.
• Employees missing from payroll. Terminated employees sometimes don't migrate. Manually re-add them as inactive so their year-to-date totals remain searchable.
• Bank feeds won't connect. Your bank may require re-authorization for a new QBO company. Clear browser cache, try an incognito window, or use QBO's bank connection troubleshooter.
• Missing attachments. File attachments (receipts, documents) often don't transfer. Plan to manually re-upload critical ones. Most aren't critical — you'll be surprised how few actually matter.

Cost Comparison: Desktop vs Online 3-Year TCO

Let's talk money honestly. Here's what a 3-year total cost of ownership looks like for a mid-size small business (5 users, inventory tracking, payroll):

• QuickBooks Desktop Premier Plus (3 users, subscription model): $1,099/year x 3 years = $3,297. Add Enhanced Payroll at roughly $700/year = $2,100 over 3 years. Total: ~$5,397.
• QuickBooks Online Plus (5 users): $99/month x 36 months = $3,564. Payroll Core add-on at $45/month + $6/employee = roughly $2,160 over 3 years for a 5-person payroll. Total: ~$5,724.
• QuickBooks Online Advanced (25 users, advanced reporting): $235/month x 36 months = $8,460. Payroll Elite at $125/month = $4,500. Total: ~$12,960.

Pricing is close enough that the decision shouldn't be about money alone. QBO typically edges out Desktop on total cost once you factor in the USB backup drives you won't buy, the IT support hours you won't spend, and the hurricane-season anxiety you won't feel watching a server rack.

QBO plans range from $30/month for Simple Start to $235/month for Advanced. Match your plan to your actual feature usage — overbuying is the most common pricing mistake.

Consider Alternatives Before You Commit

One last honest moment. If you're migrating away from Desktop, you have the rare chance to also migrate away from Intuit's ecosystem entirely. Worth 30 minutes of thought.

Xero starts at $15/month and handles inventory, multi-currency, and bank reconciliation better than QBO at the equivalent tier. Popular outside the US, growing fast inside it. Better for businesses with international transactions.

FreshBooks at $19/month shines for service-based businesses and freelancers. Time tracking, project management, and proposals are built in. Weaker for inventory or complex GL work.

Wave is free for accounting and invoicing. It's genuinely free — not freemium-with-traps. Best for sole proprietors and micro-businesses under $50K/year in revenue. Limited if you need payroll, inventory, or multi-user access.

QuickBooks Online remains the safe default if you want the most accountants available, the deepest US tax-ready features, and the largest app ecosystem. Most businesses choose it for exactly those reasons.

Whatever you pick, commit for at least 12 months. Switching accounting systems twice in a year is a form of professional self-harm. Do the work once, do it right, and get back to running your business.