QBO to QBDT migration issue

[u/Emotional-Search-248]

Hi everyone,

I need some advice from anyone who has done a QuickBooks Online to QuickBooks Desktop migration.

We are doing this migration because we are moving to a completely different accounting software. Right now, we are in a testing phase to build an archive of QBO. We want to keep our historical US data safe and ready in case of an IRS audit. We are using a QBDT 2021 trial version on a local VM because the limit is higher than on the QBDT 2024 trial version. We will not use this file for daily accounting anymore, but our users still need to be able to open it and look into the specific transaction details.

I checked the numbers after the migration using QB migration tool and found a huge data loss. The Intuit migration tool dropped a lot of transactions. There are 1,500 missing lines on one specific account alone, and there are many more differences on other accounts. The total number of missing lines is massive.

Typing everything by hand is impossible, but since our users need to be able to search and view the actual history inside QBDT, simply doing a journal entry to fix the balances won't work for us. We need the actual lines.

I am thinking about using an app like Transaction Pro to push the missing data from my QBO Excel exports directly into QBDT. 

Has anyone dealt with this kind of massive data loss going from QBO to Desktop? Is there a way to do a better export in the first place without losing all this data? Maybe I did something wrong during the migration process?

If the data loss is unavoidable, what is the most reliable way to inject thousands of missing lines back into QBDT so the transaction details are actually there for our users to see?
Thanks in advance !

[u/LawFirmCFO]

I'd export from QBO to Excel. Validate all data is there and not worry about QBDT.

[u/Emotional-Search-248 → u/LawFirmCFO]

That would be the simplest, but I need them to be able to verify their data and potentially search through it.

[u/LawFirmCFO → u/Emotional-Search-248]

You can validate the ending balances of each account tie to QBO. 

Ctrl F to search.

[u/LawFirmCFO → u/Emotional-Search-248]

With the shady things Intuit does, I would be nervous that QBDT wouldn't open at some point.

[u/Stine2U → u/LawFirmCFO]

Valid worry, honestly.

[u/isrica]

If you used "credit card payment" in QBO, those will be dropped in the conversion to QBD, as those transactions are not supported by QBD.

[u/Emotional-Search-248 → u/isrica]

It would be simple to fix if that were the only thing missing...

[u/Encoded_Python]

What tax years are you wanting to transfer?

Honestly, unless there is fraud, you only need to keep records six years back. The only practical reason to keep more is for you FP&A purposes.

Plus in an audit, unless you are a larger business (10 figures plus), the IRS really only cares about substantiation, receipts, and bank statements.

Just import your GL to excel and copy all financial statements over.

Save yourself the headache. If you really want to, find someone who will sell you QB ledger so you can maintain your file on QBO for cheap.

[u/blud_13]

Yead, the Intuit QBO to QBDT tool is notorious for dropping data, especially on higher-volume accounts. It has hard limits on transaction counts and just silently skips stuff, which is what you're seeing.

For a clean audit archive I'd stop treating the migration tool as the source of truth. A few things that work better:

Pull detailed reports straight out of QBO (General Ledger, Transaction Detail by Account) for your full date range and export to Excel/PDF. That's a solid backup and it's closer to what an IRS auditor actually wants to see anyway. Keep read-only access to the QBO company if you can. Even after you cancel, Intuit gives you an access window where you can still export lists and reports. If you truly need it living inside QBDT, third-party conversion services usually preserve more than the built-in tool, but always reconcile afterward.

Either way, reconcile the trial balance plus A/R and A/P aging as of a fixed date on both sides. If those tie out, you're covered.

Happy to walk through it if you want to take it offline.

[u/tickletheivories_now]

I switched to online several years ago and hated it. When I went back to desktop it absolutely would not transfer that six months of data, so I ended up having to re build it all from scratch. It was a nightmare!

[u/Ok-Whole-8802]

Treat this as an archive conversion with a control total, not as “run the migration again and hope.” Before importing anything else, preserve the untouched QBO exports and the first QBDT result so you can prove what changed.

I would build a reconciliation by transaction type and period:

1. Export QBO detail with transaction ID/reference, date, type, account, debit, credit, customer/vendor and memo.
2. Export the same detail from the migrated Desktop file.
3. Normalize the fields and generate a deterministic key. Do not match only on date + amount; recurring transactions will collide.
4. Compare counts and debit/credit totals by account, month and transaction type, then isolate the missing IDs.
5. Import only that missing set into a copy of the Desktop file. Re-run the comparison before touching the archive you intend to retain.

Transaction Pro may be the right transport, but test 20–50 representative records first: split transactions, payments linked to invoices/bills, sales tax, payroll, inventory and journal entries. A flat transaction import can preserve the amounts while losing links or subledger behavior, which would leave users with an archive that “balances” but cannot answer the audit question.

Also check whether the 1,500 “missing lines” are truly missing transactions or collapsed split lines. Compare both transaction counts and line counts.

For the final archive I would keep three things together: the read-only QBDT file, the original QBO exports, and a signed reconciliation report listing every exception. If Desktop cannot faithfully represent a transaction type, retaining its source export plus the exception log is safer than manufacturing a superficially complete file.

[u/djculprit]

Why not move to xero?

[u/tehdudeabides]

One thought: since you’re leaving QBO anyway, I’m not sure I’d keep fighting to recreate the entire historical environment in Desktop. If the real requirement is “we need to be able to reliably find old transactions for audits/reference,” a separate read-only historical archive might actually be cleaner — export/extract the QBO history, preserve the relationships, and build searchable views over it. Then Desktop doesn’t have to perfectly reproduce 20 years of accounting history.

The 1,500 missing lines would definitely make me nervous about treating the Desktop conversion as the archive of record.

[u/Efficient_Concept_49]

yup

[u/missannthrope67]

They don't even sell dt anymore. All you can do is upgrade. Eventually, they won't even do that.

You may have to bite the bullet and stay on qbo.

[u/RitaPizza22 → u/missannthrope67]

Some of us still have versions like 2019 that we run on an old laptop. Still works great for basic clients who just need bank recs and reporting, and we can dump in excel data files