Migrations feel like a technical task and are really a verification task. The transfer itself is largely automated. Whether you can trust the result depends entirely on what you check afterwards.
Decide the cutover first
Before touching anything, pick the date the new file becomes the system of record, and stop entering transactions in the old one after it.
The failure mode is running both in parallel "for a bit." Transactions get entered in one and not the other, and reconciling the divergence afterwards is worse than either file alone.
A fiscal year boundary is cleanest. A quarter end is workable. Mid-month is asking for trouble.
What does not come across cleanly
This varies by version and by how the file was used, which is why the check matters more than the list. Common gaps:
- Reconciliation history. Balances usually migrate; the record of which transactions were cleared in which reconciliation often does not. You may find accounts showing as unreconciled despite correct balances.
- Attachments and memos. Documents attached to transactions frequently do not travel.
- Custom reports and templates. Almost never migrate. Rebuild them.
- Payroll detail. Historical payroll often arrives summarised rather than transaction by transaction.
- Inventory valuation method. Desktop and Online do not support identical costing methods. If yours is not supported, the values change, and that is a material difference rather than a cosmetic one.
- Some list detail. Custom fields, price levels, and multi-level items may flatten.
The verification that actually matters
Before the old file is retired, run the same three reports from both and compare them line by line:
Balance sheet as of the cutover date. Every account, both files. This is the single most important check — if the balance sheets agree, the foundation carried across.
Profit and loss for the full prior year. Confirms the historical detail arrived intact and did not summarise unexpectedly.
Trial balance. Catches anything the first two aggregate away.
Differences are not necessarily errors — some reflect legitimate structural differences between the platforms. But every one should be identified and explained rather than noticed later.
Keep the old file
Do not cancel the Desktop licence the week you migrate. Archive a copy of the company file and keep the ability to open it for at least a year.
Questions about pre-migration periods come up — during a year-end, during a loan application, occasionally during an examination. Being able to open the original file is the difference between a five-minute answer and a reconstruction.
Rebuild rather than recreate
A migration is a rare opportunity to fix things, and most people waste it by faithfully reproducing a chart of accounts that was never right.
If the account structure has accumulated duplicates, dead accounts, and a cost-of-goods-sold split that was always wrong, the cutover is the moment to correct it — cleanly, at a period boundary, with a note recording what changed. Doing it later means breaking comparability mid-year.
After the cutover
Reconcile the first full month in the new file before relying on it. Connect every account, including dormant ones. Rebuild the reports you actually use, and set bank rules conservatively rather than importing habits wholesale.
Our team are QuickBooks ProAdvisors, and this is what migration covers — with the verification step treated as the deliverable rather than an afterthought. If the old file is also behind, that is a cleanup in addition, and it is usually cheaper to clean up before migrating than after.
Behind on Your Books?
We handle your bookkeeping end-to-end — categorization, reconciliation, month-end close, and clean financial statements, so your books stay current and CPA-ready.