What converts, what doesn't
- Converts well: chart of accounts, customers/vendors, transaction history (in most US files), items lists, basic templates
- Converts with damage: inventory (Desktop's average-cost world becomes QBO's FIFO, quantities and values need post-move verification), sales tax setup (rebuilt, not moved), memorized transactions (become recurring, need review)
- Doesn't convert: payroll history detail (summaries at best, export everything first), bank feed rules, attachments in some paths, custom reports (rebuild), audit trail, and any third-party integrations (reconnect fresh)
- May block conversion: very large files (target limits exist) and certain Desktop editions/features (advanced inventory setups, units of measure), oversized or complex files sometimes migrate lists-plus-balances only, with history archived in a Desktop copy
The migration order that works
- Pick the moment: month-end, ideally year-end or a quiet season, never mid-close, never the week before a filing
- Clean BEFORE you move: reconcile every account, clear old AR/AP ghosts, run Desktop's file utilities. Migrating a mess produces a portable mess ( Cleanup & Catch-Up Bookkeeping Services if the mess predates the move)
- Export the archives: payroll reports, key financials by year, and a final Desktop backup you keep forever, your history insurance
- Run the conversion (Desktop's built-in export to QBO), then DON'T touch the new file until step 5
- Verify against Desktop: P&L and balance sheet for this year and last, A/R and A/P agings, inventory quantities/values, bank balances. Material mismatches: resolve now, while re-running is cheap
- Rebuild the non-movers: bank feeds + rules, sales tax, recurring transactions, users/permissions, integrations, payroll setup
- Run parallel for one close if you can, one month of both systems agreeing buys permanent confidence, then retire Desktop to read-only archive duty
The classic post-migration mistakes
- Working in both files 'temporarily', two live files diverge within a week and someone's month is lost; cut over cleanly
- Trusting inventory blindly. FIFO revaluation makes margins drift; verify before the first post-move reports drive decisions
- Skipping the verification step entirely, discovering a conversion gap at tax time costs 10x what discovering it in week one does
- Expecting Desktop muscle memory. QBO's workflows differ (bank feeds are the center of gravity); an hour of orientation saves a month of frustration
Frequently asked questions
How long does the whole thing take?
The conversion itself: hours. The full professional job, pre-clean, convert, verify, rebuild, parallel close, typically one to three weeks of calendar time. Plan around it like the systems change it is.
Should we just start a fresh QBO file instead of converting?
Sometimes genuinely yes, ancient bloated files, or history too messy to be worth porting: start fresh with opening balances and keep Desktop as archive. The tradeoff is losing in-file history; the test is whether you ever actually query it.
Can you run our migration?
Yes, pre-clean, conversion, verification, and rebuild are a fixed-scope project for us, usually bundled with taking over the monthly books after. Bookkeeping Services for Small Businesses