Rebuilding QuickBooks Desktop Data from an IIF Export

When the company file is gone and only an IIF export survives, here is what that file can restore, and how to rebuild your lists and entries.

The company file is gone. The only survivor is an export with an .iif extension. That file is not a company file, and QuickBooks Desktop will not open it as one. Most of what an IIF holds can still be brought back through the front door, by importing it into a new company. Some of what the old file knew never made it into the export, and no import puts it back.

What can an IIF file actually be used for?

An IIF file is a tab-delimited text file. QuickBooks writes it when you export lists or transactions, and reads it back when you import them. Each line carries one record: an account, a customer, a vendor, an item, an invoice, a bill, a check, or a journal entry.

What it does not carry is the database. An IIF holds no audit trail, no user list, no reconciliation status, and none of the links that tie a payment to the invoice it settles. That is why the file cannot be opened, repaired, or converted into a working QBW: there is nothing inside it to convert. A repair service cannot do it either, ours included. Import is the only road back, so treat it as a rebuild, not a restore.

Search for the original file first

Before rebuilding, spend an hour hunting for the real file. An import rebuild is always second best to the original.

Search every drive for .qbw, .qbb, and .qbm files, including external drives, network shares, and removable media. Check email attachments and cloud sync folders, and ask your accountant whether a copy is still on file there. Look in the Company Files folder under Public Documents too, because QuickBooks writes backups there without anyone noticing.

Pay special attention to the .tlg transaction log. If one sits beside a stale backup, it holds every transaction recorded after that backup was made. Our engineers can pair the two and recover the gap; see recovering transactions from a QuickBooks transaction log. That outcome usually beats an IIF import.

Rebuilding the data, step by step

  1. Create the new company. From the File menu, choose New Company and use Express Start. Match the edition and country of the old file, since tax lines and account types must line up. Skip the chart of accounts setup; the import brings your accounts in, and hand-built ones will only duplicate them.
  2. Close every open window and switch to single-user mode from the File menu. Imports misbehave when another user or process holds the file.
  3. Back up the new, empty file before importing anything. An IIF import cannot be undone with one command; the only rollback is restoring that backup. Repeat the backup before each further import.
  4. Import the file. From the File menu, choose Utilities, then Import, then IIF Files, and select your export. QuickBooks shows an import summary when it finishes. If rows fail, note them and fix them in a plain text editor only: a spreadsheet rewrites dates, drops leading zeros, and breaks the tab structure.
  5. Check the lists. Open the Chart of Accounts, the Customer and Vendor Centers, and the Item List. Names and balances should match what the old file showed on the day of the export.
  6. Check the transactions. Open invoices, bills, and payments from several different months. Run a Profit and Loss and a Balance Sheet dated to the export day, then compare them against your last statements.
  7. Run Verify Data from the Utilities menu, fix anything it flags, then back the file up again.

How do you know the rebuild worked?

Three signs tell you the import took. The lists are present and none are duplicated. Aged Receivables and Aged Payables tie to your statements, within normal rounding. Verify Data completes clean, and the file reopens normally.

If a whole list is missing, the export never included it. Recreate it from whatever source survives.

The limits an IIF rebuild cannot cross

Payment links are the classic weak point. Payments can import and still sit unapplied to the invoices they settled, leaving balances open that were never open. Reconciliation status is gone, so every account shows unreconciled entries until you reconcile again. Payroll history, quantity on hand, budgets, memorized transactions, and the audit trail do not survive the round trip.

Importing more data cannot fix any of this. The links live in the database, and the database is the thing that is missing. If your totals from step 6 disagree materially, stop patching and treat the rebuilt file as interim; see QuickBooks data recovery when the file will not open for the durable route. Meanwhile, the imported file keeps you invoicing and paying bills.

Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.