Moving off Desktop? Don’t just convert. Migrate properly.

Online has no object to write it into. Intuit’s own transfer article (updated 2026-09-11) lists what doesn’t move: memorized reports, custom form templates (logos do move), memorized transaction groups (“Groups don’t exist in QuickBooks Online”), units of measure, price levels, custom fields on items and employees, and progress invoices based on estimates. Nothing breaks visibly; the item is simply absent when someone goes looking. The fix is manual and has to be planned before conversion: the memorized reports listed, the templates saved as PDFs, the transaction groups written down — then each rebuilt in Online as a custom report, a custom form style, or a set of recurring transactions. Budgets are the grey area: the same Intuit article lists Profit and Loss budgets among what moves and also says “Budgets aren’t recreated in QuickBooks Online due to mapping differences,” so we check them in the new file rather than assume either way.

Online stores it differently, so history is recomputed. Inventory is the clearest case: Intuit imports inventory “as First-In, First-Out method (FIFO)” from a FIFO start date you set, and its after-the-move article (updated 2026-08-05) says that because QuickBooks Online “may calculate inventory values and cost of goods sold (COGS) differently, your reports may not match exactly” — adding that you may need to notify the IRS of the change on Form 3115. The quantity on hand comes across; if the Desktop file valued inventory at average cost, the value can legitimately change, and it has to be documented as a known variance rather than hunted as an error. Sales tax works the same way — Intuit says “Some taxes move as journal entries. Sales tax won’t copy for all transactions,” so the agencies and rates are set up again in Online and the liability is verified against the Desktop figure rather than assumed. Desktop’s class-and-job structure maps onto Online’s class, location and project model — Intuit moves leaf-node jobs as projects and the remaining jobs as sub-customers — which is a different shape, so the mapping is a decision, not a copy.

It converts into a different kind of transaction. Payroll is where this bites. Intuit says paychecks move “as regular checks” and that “QuickBooks Online copies the current year’s paycheck information as lump sums.” Employees, payroll items and year-to-date balances are on Intuit’s list of what moves, and the paycheck-by-paycheck detail stays in the Desktop file, which the migration tool doesn’t delete or change — so before the first Online payroll run, every employee’s year-to-date is checked against the last Desktop payroll summary and tied to the returns already filed. Other records change shape too: memorized transactions convert into recurring transactions, sales orders (open and closed) move, and estimates move with active ones marked Closed and inactive ones marked Rejected — so each is checked, and any estimate still in play is reopened.

It is excluded by design. Intuit lists the Audit Trail among the reports that don’t move; Desktop’s history of who changed what is not part of the new file. Past reconciliation reports stay behind too — Intuit says reconciled transactions arrive with an R in the cleared column, which is why the first reconciliation in the new file has to be re-proven rather than trusted. Attachments move only if they are 30MB or smaller and stored on the computer’s hard drive; anything else is downloaded before the move.

And what “transfers” still has to be proved. We check the converted file for transactions that are missing or doubled, and we check open invoices and bills item by item, so the aging matches the control account in detail and not only in total. Anything that didn’t tie in Desktop — an unreconciled account, an open undeposited-funds balance — is carried across as it was and, in our experience, can surface as a shifted opening balance, for example in Opening Balance Equity. That account is worth reading before it is cleared: it is a summary of what didn’t convert cleanly.

Verification is a comparison, so it starts before anything is converted. On the agreed conversion date we capture the Desktop baseline: the trial balance; the balance sheet and profit and loss for the open year; the accounts-receivable and accounts-payable agings; the inventory valuation summary; the sales-tax liability; the payroll liability balances and the last payroll summary; and, for every bank and credit-card account, its ending balance and the date it was last reconciled — all on the same basis, so the two files are compared on equal terms. The Migration Integrity Protocol is the seven checks the hub describes; on a Desktop-to-Online move, this is how each one is proved.

1. Opening balances. Every balance-sheet account in Online, as of the conversion date, is set against the Desktop trial balance line by line. A difference is classified before it is touched — an expected re-basing, an unsupported item, or a conversion error — and only the last is corrected.
2. Bank and credit-card feeds. Reconnected only after the converted transactions are in, with the first download checked against what already converted so nothing posts twice. Then a reconciliation is run in Online through the last Desktop statement date. The reconciled flag came across; a zero difference proves it.
3. Payroll history. Each employee’s year-to-date checked and tied to the last Desktop payroll summary before the first Online run, since current-year paychecks arrive as lump sums, and the liability balances agreed to the returns already filed.
4. Vendor and customer lists. Counts match, duplicates merged, and the A/R and A/P agings agree with Desktop’s item by item — not just in total, because a summary balance that happens to equal the detail is exactly the error this check exists to catch.
5. Inventory. Quantity on hand per item matches. Value can differ, because Intuit imports inventory as FIFO and says Online may calculate inventory values and COGS differently; the difference is documented against the Desktop valuation as a known variance rather than left for your CPA to discover.
6. Recurring transactions. Memorized transactions convert into recurring transactions; each one is checked against the memorized list captured before conversion, memorized transaction groups are rebuilt, and the schedule is test-fired, so the first month’s rent, loan payment and subscriptions post on schedule.
7. Report parity. The profit and loss and balance sheet are run in both files for the same dates on the same basis, and every remaining difference is explained in writing.

Sign-off is the written transfer summary: one row per check, with the Desktop figure, the Online figure, the difference, and what was done about it. A migration is not finished when the new file opens. It is finished when that table has no unexplained rows.

This page reflects how TechBrot performs QuickBooks Desktop-to-Online migrations. The QuickBooks Desktop support dates and platform facts on this page were checked against Intuit’s own current help articles, cited where each fact is used. TechBrot performs the migration and coordinates with your CPA, who files your tax returns.