How long does a QuickBooks Desktop to Online migration take?

Intuit says the time depends on how complex and large the file is, and for a clean, small file the conversion itself runs in hours. The project around it, cleaning the file, printing what will not move, converting at a month end and tying every balance out, takes days for a simple company and weeks for one with inventory, payroll, multi-currency and years of history. Plan for the tie-out, not the upload.

Does inventory convert from QuickBooks Desktop to Online?

Yes, with a change. Desktop values inventory at average cost; Online imports it as FIFO from a start date you choose and recalculates quantities and values from there. The method cannot be changed later, and Intuit says to notify the IRS with Form 3115. Inventory from QuickBooks Desktop for Mac, or from Desktop 2015 and older, does not convert and must be set up from scratch.

Does payroll history move to QuickBooks Online?

Partly. Employees, wages, year-to-date balances and direct deposit details move, but paychecks arrive as regular checks and the current year’s amounts as lump sums, and pay item mappings do not move. Wait two to three business days after a payroll run before moving, and set up QuickBooks Online Payroll separately afterwards as the primary admin. Keep the Desktop payroll reports.

Can I keep using QuickBooks Desktop after moving to Online?

The two are independent and do not sync, so keep posting in one system only. Intuit gives view-only access to your Desktop data for 12 months after you cancel, if you are on Desktop 2023 R3 or newer, which is how we keep the archive. Intuit stopped selling Desktop Pro, Premier and Mac Plus to new US subscribers after September 30, 2024, and each version loses its services about three years after release.

Home / Blog / QuickBooks complex migration guide

Bookkeeping, close & software8 min readPublished February 2025Updated September 2026

QuickBooks complex migration: moving a big or messy Desktop file to Online without losing the numbers

Nare KhachatryanHead of Marketing, Hundred MS. Reviewed by Narek Abgaryan, CFA, FRM.

Illustration of a QuickBooks complex migration as a crane lifting a thick ledger book toward an open laptop

Stuck on this in your own books?

Bring it to a free 30-minute call with Narek. No pitch.

Book a call

The short answer

A QuickBooks migration becomes complex when the Desktop file is large, carries inventory, multi-currency or payroll, has years of history, or feeds other apps. Intuit’s own tool handles the plain case in an afternoon. The complex case is about what changes on the way: inventory recalculated on FIFO from a start date you choose, a single default receivables and payables account, sales tax payments that land on the wrong filings, and a list of things that do not move at all. Check the target count, decide whether to bring everything or only lists and balances, fix the file first, convert at a month end, and tie every balance out before anyone posts in the new company.

Key takeaways

Complexity is not file size. It is inventory, multi-currency, payroll, history and apps, and what each one does on the way over.
Print what will not move (sales tax report, reconciliation reports, audit trail) before you start, and freeze Desktop at a month end.
Intuit’s tie-out is the profit and loss and the balance sheet. Ours is the trial balance, the agings, every bank account and inventory, to the cent.

What makes a QuickBooks migration complex

Size. Intuit’s current limit is 4,000,000 targets (press F2 in Desktop to see yours). Above that, you condense or bring balances only.
Inventory. Desktop values items at average cost; Online recalculates them on FIFO from a start date. The numbers change, and the IRS has to be told.
Multi-currency. Preferences and transactions move, but the home currency is fixed once the feature is on, and some Online features switch off.
Payroll. Employees and year-to-date balances move; paychecks arrive as regular checks and lump sums, and Online Payroll is set up separately.
History. Twenty years of transactions, closed jobs, old sales tax and a reconciliation trail that does not come with you.
Apps and feeds. Bank connections, third-party apps and users all have to be reconnected or re-invited.

One or two of those still make a normal migration with a checklist. Three or more make it a project with a tie-out at the end, and the rest of this guide is that project. Whether to convert is no longer a question. Intuit stopped selling Desktop Pro, Premier and Mac Plus to new US subscribers after September 30, 2024, and each yearly version loses payroll, bank feeds and support about three years after release (the 2023 version on May 31, 2026). Only Enterprise is still sold.

Before you start: six checks

Count the targets. F2 or Ctrl+1 in Desktop shows Total Targets. Intuit says file size in megabytes does not matter, only targets. Over 4,000,000 means condensing (File, Utilities, Condense Data) or choosing “bring only lists and balances” in the tool.
Think twice before condensing. Intuit’s own page says it cannot be undone, that item-based reports go blank for the condensed period, cash-basis reports become inaccurate, summarized transactions lose their classes, and reconciliation reports may be wrong or gone. If you must, condense at a month end (Intuit’s tip, so average cost stays right), and print every reconciliation report first.
Fix the file. Update Desktop to the latest release, run Verify Data and then Rebuild Data under File, Utilities, and clear the errors. A file that fails Verify fails the migration.
Print what will not come with you. The sales tax report, every past reconciliation report and the audit trail. Categorize and reconcile all bank and card transactions first; Intuit lists that as a prerequisite.
Time the payroll. Wait two to three business days after a payroll run, and move at least a few days before the next one. Deactivate employees not paid this year. The target Online company must not already hold payroll data.
Know the clock. Intuit’s pages give 60 to 90 days from creating the Online company to import Desktop data (180 for a company an accountant created), and the tool will replace anything already in the Online company, which cannot be undone. Create the Online company when you are ready, not months before.

A question before you convert

Press F2 in Desktop. How many targets, and how many years of history? If the answer is millions and decades, decide now whether the new company needs all of it, or reconciled balances and a view-only archive.

What converts, what changes, and what does not

All of this is from Intuit’s own conversion guide, read in September 2026. It changes; check the page again on the day.

Area	What happens	What to do
Inventory	Imported as FIFO from a start date you set; quantities and values recalculated; the method cannot be changed later; Mac and Desktop 2015 or older do not convert inventory at all	Choose the FIFO start date with your tax adviser and file Form 3115; print the Inventory Valuation Summary before and after
Multi-currency	Preferences and transactions move (Essentials and up); home currency cannot change once the feature is on; Bill Pay and Payments are not compatible with it	Set the home currency before you enable anything; one account per currency
Payroll	Employees, wages and year-to-date balances move; paychecks become regular checks, current-year amounts arrive as lump sums; pay item mappings and timesheets do not	Set up Online Payroll separately as the primary admin; keep the Desktop payroll reports
Sales tax	Some taxes move as journal entries and not for every transaction; Desktop payments apply to the wrong filings in Online	Intuit’s fix: delete the migrated sales tax payments and recreate them in the sales tax center
Lists	One default A/R and one default A/P account (the last used); jobs become projects or sub-customers; price levels, customer types, sales reps, credit limits and item custom fields do not move	Clean the lists first; decide Essentials versus Plus before converting if jobs must stay sub-customers
Transactions	Estimates close, progress invoices and pending sales do not move, purchase orders lose their link to bills, some checks and invoices arrive as journal entries if tax rates were flat	Bill what you can before the move; relink open POs after
Reports and history	Audit trail, memorized reports and past reconciliation reports do not move; accrual reports match, cash-basis reports may not	Save the reports as PDFs; keep Desktop in view-only mode for 12 months (2023 R3 or newer)
Feeds, apps, users	Bank rules move (Windows only); bank connections, app connections and user access must be set up again	List every app and feed before the move; reconnect on day one; re-invite users

Bring everything, or lists and balances?

The tool offers both. Bringing everything keeps the history searchable in one place and suits a clean file under the limit. Lists and balances suit a huge or damaged file: you open with reconciled balances at a month end and keep Desktop, in view-only mode, as the archive. Either way, freeze Desktop at a month end. A cut-over mid-month is how the first close in Online fails.

The tie-out that says you are done

Intuit’s post-migration advice is to compare the Profit and Loss and the Balance Sheet in both systems, all dates, accrual basis, and to check Accounts Receivable and Undeposited Funds. That is the minimum. Ours is longer, because a balance sheet that agrees in total can hide two errors that cancel.

Trial balance, account by account, all dates, accrual, in both systems.
Receivables and payables aging by customer and vendor, and the single default A/R and A/P accounts checked.
Every bank and card account to its last reconciled balance, then the first Online reconciliation done immediately.
Inventory valuation summary before the move against Online after the FIFO recalculation, with the difference explained and journaled, not plugged.
Sales tax liability by agency, after the payments have been recreated.
Detail types on every account (Intuit assigns generic ones), and the closing date password set.

In a recent migration onto QuickBooks Online, from an enterprise ERP rather than Desktop, the tie-out ran to 721 reconciliation rows across three dates and every one read 0.00 before the client posted a single transaction. That is the standard we mean by “done”.

Where AI helps, and where it does not

The mechanical part of a migration is a matching problem: thousands of Desktop transactions against thousands of Online ones, lists against lists, balances against balances. AI does that in minutes and flags every difference. What it cannot do is decide the FIFO start date, whether a job should be a project or a sub-customer, or whether a difference is a timing issue or a lost transaction. In our work an accountant decides those, the AI keeps the tie-out workbook honest, and a senior accountant signs before the Online company goes live.

When to get help

A single-entity file under the target limit with no inventory and no payroll is a job you can do with Intuit’s tool and a careful weekend. Inventory, multi-currency, payroll, several years of history or a file that fails Verify make it a project where mistakes cost more than the help. Our QuickBooks migration service starts with a look at your file and a written scope and quote within two days; if the answer is “you can do this yourself”, we say so.

Where this goes wrong

The problem	What it costs you	The fix
The file is condensed in a hurry to get under the limit	Item reports go blank, classes vanish, reconciliation reports are gone, and it cannot be undone	Print every report first, condense at a month end, or bring lists and balances instead
The cut-over lands mid-month	The first Online close does not tie and nobody can say which system a transaction belongs to	Freeze Desktop on the last day of a month and open Online on the first
The balance sheet totals agree, so the migration is declared done	Two errors that cancel each other surface months later in an audit	Tie out account by account, aging by aging, and explain every difference