QuickBooks Desktop IIF Export Covers Lists Only, Not Transactions

Moving data out of QuickBooks Desktop trips people up in the same place every time. The built-in export to IIF produces tidy files, yet the transactions are missing. A recent community exchange between a user and a third-party app developer walked through the cause and a working fix, and we have laid it out below.

The IIF export covers lists only

Desktop’s own IIF export writes four kinds of records: accounts, customers, vendors, and items. That is the entire scope. Invoices, sales receipts, bills, checks, and deposits never leave the company file through this route. If you were counting on it for a full data move, the omission is by design rather than a setting you missed.

Can Desktop export transactions to IIF on its own?

No. The desktop program has no built-in command that writes transactions to IIF, which is why third-party IIF exporters exist as a product category. The company file is a dead end too. The app in that thread cannot read the .QBW file directly, and that is common: the format is proprietary, so importing tools work from exports instead of the file itself.

A report-to-CSV route for sales receipts

Reports are the practical bridge. In QuickBooks Desktop:

1. Open Reports, then Custom Reports, then Transaction Detail.
2. Set the date range to All.
3. On the Filters tab, set Transaction Type to Sales Receipt.
4. Leave the default columns as they are.
5. Click Excel, choose Create New Worksheet, and save the sheet as CSV.

That CSV is what the receiving app imports. The same pattern works for the Deposit Detail and Check Detail reports, so checks and deposits can travel the same road.

Invoices are the awkward case

At the time of the exchange, the report route covered sales receipts but not invoices, and invoice support sat on the developer’s roadmap. Two workarounds fill the gap meanwhile. A third-party IIF transaction exporter can produce files Desktop will not write itself. The developer also confirmed that QuickBooks Online works with the app as an import source, so routing through it is another option.

Line up your lists first

Order matters more than speed here. Import the IIF list files before any transaction CSV, so customer and item names match what the rows reference. A name that does not match tends to arrive as a duplicate or an error. Spot-check a handful of names before committing to the full run.

Test one month before you export everything

Run the transaction report for a single month, import it, and compare totals against the same period inside QuickBooks. When the numbers agree, set the date range back to All and finish the migration. A short check now beats a long cleanup later.