QuickBooks Desktop to Online migration

Most migrations bring across 3 to 12 months of history instead of a full multi-year archive. Older closed years usually stay accessible in a read-only Desktop file instead of being ported line by line, which keeps the Cleanup portion proportional to what the new file actually needs to open with. We recommend the split before quoting anything.

Intuit has stopped selling new QuickBooks Desktop subscriptions, so every year the remaining installs run further behind on support and integrations, and the pool of bookkeepers who still know Desktop well keeps shrinking. Moving a client on your firm's schedule, before a payroll or bank-feed integration they rely on drops Desktop support, is a far smaller job than moving under pressure once it does.

There's no requirement to move everything at once, either. A company running Desktop on a single machine can migrate the current fiscal year first and bring older years across later, or leave them in a read-only archive for good. We recommend a specific split for that file instead of handing you an all-or-nothing plan.

The other common trigger is a client outgrowing what Desktop was built for: a second location added, a remote bookkeeper hired, or a lender who wants to see numbers online instead of receiving an emailed file. QuickBooks Online was built for exactly that kind of access. Desktop wasn't.

Client companies still running QuickBooks Desktop, whether that's Pro, Premier or Enterprise, on a single machine or a small office network, ready to move to QuickBooks Online but needing the historical data and reporting structure to survive intact. It fits whether the file has one user or several, and whether it's been maintained well or is overdue for a cleanup either way.

It's not the right fit for a client who wants to stay on Desktop. We won't talk anyone out of a decision that's working for them. If the file is already on QuickBooks Online and just behind, that's cleanup or catch-up, not a migration.

A current backup file of the client's QuickBooks Desktop company, admin access to create the new QuickBooks Online company, and bank statements for any period that needs reconciling further back than the bank feed will carry over on its own. If Desktop sits on a shared network drive rather than a single machine, knowing who holds admin rights on that install speeds up day one.

If the QuickBooks Online subscription isn't purchased yet, a note on the client's approximate annual revenue and how many people will need their own login lets us recommend the right subscription tier before the file is built. As a QuickBooks Certified ProAdvisor, we can also provision the new company with Intuit's 30% ProAdvisor discount on QuickBooks Online (plus Workforce & Time; ongoing when the firm pays Intuit, 12 months when the client pays directly), passing the software savings directly to the client.

Most migrations take 5 business days from receiving the Desktop backup to a reconciled, documented QuickBooks Online company. Files with heavy job costing or inventory can run longer, and the free file review gives you a specific day count for those before any work starts.

We open the Desktop backup and run the pre-migration audit before anything gets created in QuickBooks Online. The goal is to know what won't convert cleanly before the new company exists instead of discovering it afterwards. Your firm gets a written map of what's moving, what's being rebuilt and what's staying behind in a read-only archive, inside the first two days.

Yes. The Desktop company isn't touched or disabled during the migration, so the client's invoicing, payroll and reporting keep running there without interruption while the new QuickBooks Online company is built and checked. Most run both in parallel for one to two weeks after the new company is ready, entering new transactions in QuickBooks Online while confirming everything from Desktop landed correctly, before switching over for good.

Payroll almost always needs its own reconnection step, separate from the accounting data. Most payroll providers treat a move to QuickBooks Online as a new company setup on their side, not an automatic follow-along. Any point-of-sale, inventory or time-tracking integration that fed the old Desktop file needs the same check: some connect to QuickBooks Online natively, some need a different connector entirely, and a few have no Online equivalent at all. The pre-migration audit lists every connected app we find in the Desktop file, so none of it surfaces as a surprise mid-move.

More than most firms expect, which is why the audit runs before anything is created. Inventory is the big one: Desktop values inventory at average cost and QuickBooks Online uses FIFO, so quantities carry across but the valuation has to be rebuilt rather than converted, and the resulting cost of goods figures will not tie to the old file line for line without that work.

Custom invoice and form templates don't come across and are rebuilt in QuickBooks Online's own template editor. Historical reconciliation reports don't move either, though the reconciled status on individual transactions does, so past periods stay locked without the paperwork behind them. Sales orders and price levels have no direct QuickBooks Online equivalent and need a decision about what replaces them. The audit trail from the Desktop file stays in the Desktop file.

None of this is a reason not to convert. It is a reason to know the list before the switch rather than after, because every item on it is cheaper to plan for than to discover during a close.

Intuit's conversion tool has a hard ceiling on file size, measured in "targets" (roughly the individual lines inside every transaction rather than the transaction count itself). A file over the limit will simply refuse to convert, and a long-running Desktop company with years of detailed job costing or inventory activity hits it more often than its owner expects.

The fix is the same split we recommend for most migrations anyway: bring the current fiscal year and whatever prior history the new file genuinely needs, and leave the closed years in a read-only Desktop archive. That keeps the new company under the ceiling and, more usefully, keeps it clean. Condensing the Desktop file to squeeze under the limit is the other route, and it is usually the worse one, because it destroys the transaction detail behind the summary entries it leaves in place.