Convert QuickBooks Desktop to QuickBooks Online

What transfers from QuickBooks Desktop to QuickBooks Online

Intuit's migration tool copies your Desktop company file into a QuickBooks Online subscription in the same country or region. Nothing is removed from QuickBooks Desktop, so the original file stays available as a historical record. From the conversion date forward, treat QuickBooks Online as the live set of books.

These are the main transfers you can count on:

Some data never crosses over. Bank and credit card connections do not migrate, so reconnect each account in QuickBooks Online. Custom form layouts, letter templates, price levels, units of measure, audit trail history, memorized reports, mileage entries, and past reconciliation reports stay behind. Existing Desktop users receive no Online access until you invite them. Intuit notes that budget data does not map cleanly, so rebuild budgets by hand. Sales tax needs one specific cleanup: migrated sales tax payments can apply to the wrong filings, so delete them and recreate them in the Sales Tax Center.

Plan limits also apply. QuickBooks Online Simple Start, Essentials, and Plus are capped at 250 chart of accounts, and Plus is capped at 40 combined classes and locations; Advanced removes those list limits. Billable users run 1, 3, 5, and 25 across the four plans. Check your Desktop lists against those numbers before the move — the QuickBooks Online setup guide covers post-conversion configuration in detail.

Before you convert: a pre-conversion checklist

Run this checklist inside QuickBooks Desktop. Every item reduces the chance of a failed transfer or a review that takes days instead of hours.

• Back up the entire company-file folder. Copy the .QBW file and its support files to an external drive, not just the database. The backup and restore walkthrough shows the full set of files.
• Update QuickBooks Desktop to the latest release. Older builds use older export code and fail more often.
• Verify and rebuild the data. Go to File → Utilities → Verify Data, then Rebuild Data if problems appear. A damaged file migrates damaged — see company file repair.
• Switch to single-user mode. Open the File menu. If it offers Switch to Multi-user Mode, you are already in single-user mode.
• Check the target count. Press F2 (or Ctrl + 1) and read Total Targets. Imports require fewer than 4,000,000 targets; files above 750,000 targets can be slow and prone to discrepancy.
• Reconcile every bank and credit card account and save the reports as PDF. Past reconciliation reports do not transfer, even though cleared marks do.
• Finish payroll first. Run payroll, then wait 2–3 business days before migrating. Complete the migration at least 7 business days before your next scheduled payroll.
• Confirm access and timing. You need admin access to both the Desktop file and the Online account. The self-serve window is 90 calendar days after you sign up for Online, or 180 days if an accountant signed up for you.

How to convert QuickBooks Desktop data to QuickBooks Online

Post-conversion checklist: reviewing the converted data

1. Run a Trial Balance and Balance Sheet in QuickBooks Online as of the conversion date and compare them to the same reports in QuickBooks Desktop. Expect small differences in inventory and sales tax; investigate anything else.
2. Run A/R Aging and A/P Aging reports and match the totals. Jobs that became projects or sub-customers are the most common source of a mismatch.
3. Reconnect every bank and credit card account, setting the download start date to the conversion date so you do not import transactions you already recorded. If a feed fails, the bank feed troubleshooting guide covers the usual fixes.
4. Rebuild sales tax: delete the migrated sales tax payments and recreate them in the Sales Tax Center, then run the Sales Tax Liability report.
5. Recreate custom form styles, invoice templates, budgets, and memorized reports. Your logo transfers; layouts do not.
6. Re-add attachments larger than 30 MB or stored outside the local hard drive.
7. Invite users under Settings → Manage users and assign roles. Desktop permissions and shortcuts do not carry over.
8. Verify payroll before the next pay run. Paychecks arrived as lump sums and pay item mappings did not transfer, so compare year-to-date figures with your payroll records — the payroll troubleshooting guide covers the common gaps.

If the conversion fails or the balances look wrong

Most failed conversions come back to three things: a target count that is still too high, unresolved data damage in the source file, or an existing Online company that was partially replaced. Recheck the target count first, run Verify and Rebuild once more, then retry the export into a clean Online company. If the built-in tool keeps failing, use the online migration tool and upload the backup file instead.

Do not repeat the export over and over on a damaged file. Each attempt costs time, and a file that cannot be repaired cleanly is better handled by professional repair before conversion. Keep the original Desktop file and backup intact throughout; they are the authoritative record if the Online copy is ever in doubt.

When to use a professional for the conversion

Call in an accountant, bookkeeper, or Intuit-assisted migration when any of these apply:

• The target count stays above 4,000,000 after condensing.
• You track inventory with average cost or FIFO, use assemblies, or run multi-currency.
• You run payroll mid-year and year-to-date figures must agree to the penny.
• You maintain several company files or a file with damage that Verify and Rebuild cannot clear.
• You rely on progress invoicing, custom fields, or multi-state sales tax.

An accountant can be added to both the Desktop and Online companies as an accountant user, and Intuit offers an Accountant Batch Migration Tool for firms moving up to 50 clients at once. For complex payroll or inventory files, Intuit support can guide or take over the migration. The cost of that help is usually smaller than the cost of discovering a wrong inventory value or payroll total three months later.