Migrating a Small Ontario Firm from QuickBooks Desktop to QuickBooks Online: What Actually Breaks, and How to De-Risk It
The short answer: Most of your day-to-day data — customers, vendors, chart of accounts, open invoices and bills, and the transactions behind them — does come across. But several things do not transfer cleanly, and a few change how your numbers are calculated. The four that catch Ontario firms off guard are: your audit trail does not come over, your bank reconciliations reset to zero, payroll paycheque detail is flattened into plain cheques, and if you track inventory, your costing method can change. None of this makes the migration a bad idea — but each one is a place where books get quietly corrupted if you migrate on a Friday and assume it "just worked" on Monday. This article lists exactly what breaks and gives you a checklist to migrate without that happening.
If you run a 5–50 person accounting, legal, HR, or insurance firm in Kitchener–Waterloo–Cambridge and you're still on QuickBooks Desktop, the dread is real: you've heard the horror stories, your books are the business, and a botched migration means explaining to a client (or the CRA) why a reconciled balance moved. Let's take the fear out of it by naming the actual failure points.
What actually does NOT transfer (verified against Intuit's own documentation)
These are Intuit-documented limitations, not opinion. Confirm the current specifics for your file — Intuit updates behaviour — but as of this writing:
1. The audit trail does not come across
Your historical Desktop audit trail (who changed what, and when) does not migrate to QuickBooks Online. QBO starts a fresh, improved audit log from your conversion date forward — but the Desktop history stays in Desktop. For a firm that may need to defend a historical entry to the CRA or a client, this matters: keep your Desktop company file as your permanent record of pre-migration history. Do not uninstall Desktop after you convert.
2. Bank and credit-card reconciliations reset
QBO assumes nothing has ever been reconciled. Every transaction up to your conversion date arrives as un-reconciled, even though it was reconciled in Desktop. You have to mark them reconciled again (a "mini-reconciliation" up to the conversion date) so your first real QBO reconciliation lines up. Skip this and your reconciliation drift compounds every month.
3. Payroll paycheques become plain cheques
This is the sharpest edge. When paycheque data converts, QuickBooks strips the payroll metadata — the itemized breakdown of source deductions, employer contributions, and tax line detail. Historical paycheques can land in QBO as ordinary cheques. Basic employee info transfers, but QBO Payroll is set up as a separate step, and you should not assume year-to-date payroll figures carried over intact. For an Ontario firm mid-year, verify YTD source-deduction totals before your next remittance.
4. Inventory costing changes (Average Cost → FIFO)
If you track inventory in Desktop on Average Cost (the default in QuickBooks Desktop Pro and Premier), QuickBooks Online uses FIFO (First-In-First-Out) — and this is not optional. QBO calculates inventory cost in FIFO only, with no setting to switch it, and that holds for the Canadian edition as well (QuickBooks Canada — inventory costing methods). So a Desktop→Online move on an Average-Cost file always changes your costing method. That's not cosmetic — it changes your cost of goods sold and can have tax implications. Most professional-services firms don't track inventory, so this may not apply to you — but if it does, treat it as a decision to plan for (a common approach is to zero out quantities and adjust values to opening balance equity before converting), not a surprise.
5. Sales tax (HST/GST) payments can misapply
Migrated sales-tax payments can attach to the wrong filing period in QBO. The Intuit-documented fix is to delete the migrated payments and recreate them in the QBO sales-tax centre. For an Ontario firm on HST, reconcile your HST payable and filed periods immediately after migration — before you file the next return.
6. The "leftovers" list — things you'll rebuild by hand
Intuit documents these as non-transferring: custom form/invoice templates, memorized/scheduled (recurring) transactions, budgets, user permissions, bank feed connections, third-party app connections, fixed-asset item lists, reconciliation reports, and vehicle mileage. Also: company name, address, and email are not carried over — you re-enter them. None of these is hard individually; the risk is forgetting one (a recurring monthly invoice that silently stops going out).
7. File-size ceiling
Very large or old files struggle. Intuit flags files with more than 750,000 "targets" (roughly, transaction lines) for data discrepancies — especially in inventory — and slow conversions. If your file is large or spans many years, check your target count before you start (Desktop shows it in Product Information, Ctrl+1 / F2).
The de-risking playbook
The migration doesn't fail because the tool is bad. It fails because someone treats a one-way data conversion like a routine software update. Do this instead:
- Migrate a copy first, never your live file blind. Import into a trial/second QBO company and inspect it before committing your real books.
- Freeze a hard "conversion date" and stop entering in Desktop. No parallel data entry across both systems, or you'll never reconcile them.
- Reconcile Desktop completely the day before. Migrate from a clean, fully-reconciled starting point so any post-migration drift is obviously from the migration.
- Pick a low-activity window. Month-end and quarter-end (HST filing) are the worst times. A quiet week with a day or two of buffer is the whole "downtime window" you need — the conversion itself is mostly waiting.
- Keep Desktop as your permanent archive. It is your audit trail and your rollback. Don't cancel it the moment QBO looks fine.
The reconciliation checklist (run this immediately after migration)
Tie out these numbers in QBO against your last clean Desktop reports — before you trust the file:
- Trial balance / balance sheet total matches Desktop as of the conversion date
- Bank and credit-card balances match; mark pre-conversion transactions as reconciled
- Accounts Receivable aging matches (open invoices, totals, and dates)
- Accounts Payable aging matches (open bills)
- HST/GST payable ties out; migrated tax payments checked for wrong-period misapplication
- Payroll YTD source-deduction and employer-contribution totals verified before next remittance
- Inventory quantities and values match (and costing-method change, if any, is understood)
- Recurring/memorized transactions rebuilt; nothing that should auto-send has silently stopped
- Custom invoice/estimate templates rebuilt to match your firm's branding
- User permissions reconfigured (don't leave staff with owner-level access by default)
- Third-party app and bank-feed connections re-authorized
If every line ties out, you migrated cleanly. If one doesn't, you caught it in the first week — when Desktop is still there to compare against — instead of three months later.
The rollback plan (because you should always have one)
Your rollback is simple and it's why you keep Desktop: if QBO doesn't tie out and you can't resolve it quickly, you keep operating in Desktop while you fix the migration. Since you froze the conversion date and didn't enter new data in both systems, no work is lost — you re-run the migration once the source issue is corrected. A migration with no rollback isn't a migration; it's a gamble with your books.
If you'd rather not run this checklist alone, we offer a free 20-minute automation audit for KWC professional-services firms — we'll look at your current setup and where a QBD→QBO move (or the follow-on automation) would actually save you hours. No obligation, no pitch you didn't ask for. Grab a time here: calendly.com/siddhantbadola5/30min.