Bottom line: Moving from QuickBooks Desktop to QuickBooks Online is often sold as a simple upgrade. In practice, teams hit payroll and tax form mismatches, incomplete history, and months of cleanup. If your books are fine on Desktop—or you want a ledger file you hold—you are allowed to say no to QBO and choose a deliberate path: stay on Desktop, run a documented cutover to another system, or use local-first software like Privbooks where the general ledger lives in browser SQLite you can export and back up.
What breaks in real QBD → QBO projects
Forum threads and operator stories repeat the same failure modes—not because Intuit is uniquely evil, but because two different products with different rules are being asked to behave like one continuous system. Common pain points:
- Payroll and year-end: history and tax setups do not always map one-to-one. That can surface as wrong W-2 or 941 narratives, duplicate or missing earnings history, and expensive CPA rework.
- Open AR/AP and attachments: invoices, bills, payments, and links between them may import partially or with wrong statuses—especially in older or very large company files.
- Inventory and job costing: layer-based inventory, assemblies, and class or location splits are frequent weak spots in automated converters.
- “Too large” or fragile files: some files are flagged as unsuitable to migrate; cleanup vendors and third-party tools add cost and still fail.
- Support loops: when something is wrong in payroll or tax, you need a definitive answer fast. Ticket queues and handoffs between payroll, product, and accounting firms burn calendar time.
None of that means QBO is never the right product—it means migration is a project with downside risk, not a button click. Treat it like an ERP cutover: freeze scope, pick an as-of date, and get your CPA in the loop before you strand the team.
When staying on Desktop (or going local-first) is rational
You are not “behind” because you still run a desktop file. Many businesses stay put when:
- Payroll and tax are stable in Desktop and you have no appetite to re-validate every employee record in a new stack.
- You need offline access, predictable latency, or a custody model where the canonical books are not only reachable through a vendor's hosted UI.
- You already accept CSV bank workflows or limited live feeds and would rather keep control than chase parity with every QBO feature.
Privbooks is built for operators who want double-entry books and exports their preparer can re-perform—in the browser, on SQLite, with optional cloud plumbing only for billing and optional snapshots—not for hosting the live ledger. That is a different custody story than “all history lives in Intuit's cloud by default.”
How Privbooks covers common Desktop workflows (without QBO)
If you are comparing “what we do in QuickBooks Desktop today” to “what we need in the next system,” these are the kinds of objects Privbooks ships for day-to-day operations—always subject to your own scope and CPA review:
- Accrual invoices and customer payments with A/R applications—not only cash-basis shortcuts.
- Estimates (no GL until you convert) and sales receipts for cash sales without open A/R.
- Vendor bills, bill payments, and optional check number / payee metadata for printed check stubs.
- Customer statements: open balance or activity by invoice issue date—useful when someone asks “what did we bill last quarter?” without exporting to another tool.
- FIFO inventory layers, multicurrency with a functional currency, and bank CSV import plus optional paid Plaid feeds when you choose them.
What Privbooks does not pretend to be: a full payroll tax compliance and government e-file engine. Keep payroll in a product designed for it, or with your payroll provider, and tie the GL through journal entries your firm approves. The shipped boundaries are summarized in docs/EXTENSIONS_AND_COMPLIANCE.md.
If you move anyway: cutover beats “magic import”
Whether you go to QBO, another cloud suite, or Privbooks, the reliable pattern is the same: opening balances and lists that tie, a frozen as-of date, and a read-only copy of the old file for history. For a step-by-step that matches how Privbooks thinks about imports and CPA handoffs, read the QuickBooks cutover playbook and data ownership and a portable general ledger.
Checklist before you agree to QBO migration
- Written scope from whoever runs the migration: payroll, inventory, open AR/AP, fixed assets, and attachments—in or out.
- A parallel trial on a copy of the file, with reports compared side-by-side before you cut over live work.
- CPA sign-off on payroll and year-end continuity, not only “the balances look close.”
- A rollback plan: who can still post in Desktop, and for how long, if QBO is wrong.
Closing
The right accounting stack is the one your team can run cleanly and defend at tax time. If forcing everything into QuickBooks Online feels like the riskiest option on the board, you have alternatives: stay on Desktop while you plan, or move to a local-first ledger you control. For a broader comparison framework, see the local-first accounting buyer guide—then open the Privbooks homepage and validate exports and backups against your own checklist.