IIF to QIF Converter

Convert IIF files from QuickBooks Desktop to QIF format for Quicken, GnuCash, or Microsoft Money. Free, instant, 100% in your browser.

100% freeNo signup neededData never leaves your browser
1
2
Upload file

Drop your IIF file here

or click to browse

How to convert IIF to QIF

1

Get your IIF file

Export transaction data from QuickBooks Desktop as an IIF file.

2

Upload IIF

Drop the file into the converter above — transactions are parsed automatically.

3

Import QIF

In Quicken, GnuCash, or Microsoft Money: File > Import > QIF File.

Moving from QuickBooks Desktop to Quicken

QuickBooks Desktop and Quicken are both Intuit products, but they use incompatible transaction formats. QuickBooks Desktop exports and imports IIF (Intuit Interchange Format) — a tab-delimited format with double-entry TRNS/SPL/ENDTRNS record blocks. Quicken, along with GnuCash and Microsoft Money, uses QIF (Quicken Interchange Format) — a much simpler single-entry format with single-letter field codes.

Our converter reads each TRNS row from your IIF file — matching the DATE, AMOUNT, and NAME/MEMO columns by header — and generates a valid QIF file with D (date), T (amount), and P (payee) lines for each transaction, ready for Quicken's QIF import.

This is the fastest path when leaving QuickBooks Desktop for a personal-finance tool, or when consolidating old QuickBooks Desktop company files into a Quicken register without re-entering transaction history by hand.

How IIF fields map to the QIF file

IIF columnQIF lineQIF code
DATEDateD
AMOUNTAmountT
NAME (falls back to MEMO)PayeeP
SPL offset linesnot carried over

Only the primary TRNS line is converted per transaction — QIF has no double-entry concept, so the SPL offset row from IIF is dropped rather than duplicated.

Common issues

"No TRNS rows found in IIF file." This means the file doesn't contain a !TRNS header line followed by TRNS rows — double-check you exported transaction data (not a list export like Customers or Items, which use different IIF headers).

Payee names are missing. Some IIF exports only populate the MEMO column and not NAME. The converter falls back to MEMO automatically, but if both are blank in the source file, the payee will be blank in QIF too.

Quicken assigns everything to the wrong account. QIF files don't carry account information the way IIF does — Quicken assigns all imported transactions to whichever account you select during the File > Import step.

Frequently asked questions

When would I need IIF to QIF conversion?

When you have transaction data exported from QuickBooks Desktop as an IIF file, but you're moving to Quicken, GnuCash, or Microsoft Money — all of which read QIF, not IIF.

What is the difference between IIF and QIF?

IIF (Intuit Interchange Format) is QuickBooks Desktop's tab-delimited transaction format, built around double-entry TRNS/SPL/ENDTRNS blocks. QIF (Quicken Interchange Format) is a simpler, single-entry, single-letter-coded format used by Quicken, GnuCash, and Microsoft Money. They come from the same era but aren't interchangeable.

How do I export an IIF file from QuickBooks Desktop?

In QuickBooks Desktop, go to File > Utilities > Export > Lists to IIF Files for lists, or use a report/register export depending on your version. Many users instead generate IIF via a bank download or third-party export tool — either way, this converter reads any IIF file with TRNS transaction rows.

How do I import the QIF file into Quicken?

In Quicken, go to File > Import > QIF File, select the downloaded .qif file, choose the account it belongs to, and confirm the import.

Does this preserve payee names?

Yes — the payee/name field from each IIF TRNS row is mapped to the QIF Payee (P) line, falling back to the MEMO field if no NAME column is present.

Does it handle split transactions?

The converter reads each top-level TRNS row (date, amount, payee) and skips the SPL offset lines — since QIF doesn't use double-entry accounting the way IIF does, only the primary transaction amount is carried over.

Is there a transaction limit?

No — completely free, no size or transaction-count limit. Your file never leaves your browser.