QuickBooks Online to Desktop Migration: Edition, Date Range, and Cutover

A move from QuickBooks Online to Desktop can strand audit history, payroll, and multicurrency; here is how our engineers scope a clean cutover.

Moving books from QuickBooks Online to QuickBooks Desktop is a rebuild, not an export. Three decisions shape everything that follows: the destination edition, the version year, and how much history comes across. This page is the sequence our engineers run, from scoping through a tied-out cutover.

When does this migration make sense?

Run it when the books need something Online cannot hold: units of measure, sales orders, more simultaneous users, or a local file you control end to end. Subscription cost pushes some companies the same way.

Time the move at a period boundary. A closed month, or a closed year with adjusting entries done, gives you a clean cutoff to tie against. A mid-period move doubles the reconciliation work on both sides.

Choosing the Desktop edition and version year

The edition is decided by what the books already use. Multicurrency needs Premier or Enterprise, since Pro has none. Sales orders sit in Premier and Enterprise. Pro and Premier lists stop near 14,500 combined entries; Enterprise goes far past.

Pick the year deliberately: Desktop file formats move forward only. Once a file has opened in a given year, it will not open in an older one. Name the exact year you hold a licence for before conversion starts, and plan to stay on it.

Our scoping check is a short inventory of the Online company: classes, locations, multicurrency, automated sales tax, inventory, and user count. Match each against the candidate edition. A gap found now is cheap; the same gap after cutover is expensive.

Full history or a cutoff date range?

Full history converts every transaction, so comparatives print and auditors can drill down. The cost is file size and a longer rebuild list, because every year of inventory costing and old payroll items needs review.

With a cutoff, all lists convert plus transactions from a chosen start date, usually the first day of a fiscal year. Open invoices and open bills must come across as individual transactions, not lump balances. Otherwise payments made after cutover will not apply to them.

History before the cutoff stays in the Online company as a read-only archive. Our default is the cutoff; choose full history only when audit, financing, or comparability demands it.

What converts cleanly?

Chart of accounts, customer and vendor names, items, and the core transaction set all carry. That set covers invoices, bills, payments and bill payments, credits, deposits, checks, credit card charges, journal entries, and sales receipts. Class assignments on transactions generally survive the move.

What has to be rebuilt by hand?

Plan to rebuild the audit log, file attachments, bank rules, custom report layouts, and recurring templates. Locations have no Desktop equivalent, so decide before conversion whether they become classes or a segment in the customer name.

Payroll history does not convert; Desktop payroll is a separate subscription with its own setup. Automated Sales Tax needs review, because Desktop computes tax on its own engine. Cleared flags do not carry, so previously reconciled items arrive unreconciled.

Multicurrency books aimed at Pro need a decision first. Step up to Premier or Enterprise, or have the file rebuilt in home currency through our QuickBooks multi-currency removal service.

Running the conversion and verifying the file

Export from the Online company, or hand the export to our QuickBooks Online to Desktop conversion service when the books are large or the rebuild list is long.

Open the result in the chosen edition and let any update finish. Press F2 and confirm the Product Information screen shows the edition and year you planned for. Close every window, switch to single-user mode, and run File, Utilities, Verify Data.

A clean verify reports no integrity problems. If it fails, run Rebuild and verify again before anything else touches the file. Rollback point: keep the untouched export and any pre-existing Desktop backup until verify passes.

Tying the converted file back to your Online balances

Before export, pull five reports from the Online company as of the cutoff date: trial balance, receivables aging, payables aging, inventory valuation summary, and balance sheet. Save them outside both systems.

After conversion, run the same five in Desktop and compare line by line. Expect small gaps: uncategorized amounts pushed to a default account, retained earnings detail rolled up, and rounding in averaged inventory costs. Clear each with a dated journal entry, or fix the source and reconvert when a difference is structural.

Then restore reconciliation status: mark prior cleared items manually, or reconcile each account against the statement balance as of the cutoff so the R column locks. For close mechanics after a move, see what a migration does to a set of books.

Cutting over and rolling back

Freeze entry in the Online company on the cutoff date and switch all new work to Desktop. Keep the Online subscription alive and read-only until the first Desktop month closes and the bank accounts reconcile.

The rollback is simple because Online stays the system of record until tie-out passes. If anything fails, resume entry there and nothing is lost. Do not cancel the subscription early; with a cutoff, that archive is your history.

A clean outcome

The trial balance matches to the penny, or every difference is documented and journaled. Both agings match by name. Inventory valuation matches, or its gaps trace to cost averaging. Verify Data passes clean, the file opens in the edition and year you chose, and the first month closes with nothing unusual in it. That is the file you keep.