Conversion

Convert an Old Quicken QIF to a Modern QFX

Modern Quicken won't import a QIF into bank accounts. Convert QIF to QFX: restructure its D/T/P codes into OFX and add the Intuit headers Quicken verifies.

5 min read
Updated 2026-08-06
By EasyBankConvert Team

TL;DR - Quick Summary

Modern Quicken no longer imports a QIF into checking, savings, or credit card accounts, so a legacy QIF stalls. Converting QIF to QFX restructures its single-letter codes into OFX transaction blocks, generates a FITID for each, and adds the Intuit headers Quicken uses to verify the file through Web Connect.

Modern Quicken won't import QIF into bank accounts

QIF was Quicken's own text format for years, but modern Quicken dropped QIF import for the everyday account types, checking, savings, and credit card, and now expects a Web Connect QFX for those. So a QIF sitting in an old backup, or exported by a program that still writes QIF, cannot go straight into a Quicken bank account anymore. Converting it to QFX is the way in, and it takes two distinct changes, not one.

QIF is flat; QFX is OFX plus Intuit headers

This is where a QIF differs from an OFX that only needs a header tweak. QIF is flat: single-letter codes, D for date, T for amount, P for payee, M for memo, N for a check or reference number, one per line. QFX is OFX underneath, a STMTTRN block per transaction, plus Intuit's headers. So the conversion does two jobs at once: it restructures the coded QIF lines into proper OFX transaction blocks, and it adds the Intuit headers that make it a QFX. A rename cannot do either.

FITIDs the QIF never had

Every QFX transaction carries a FITID, a unique identifier Quicken uses to avoid importing the same item twice. QIF has no equivalent, so the conversion generates a FITID for each transaction as it builds the OFX blocks. That is what lets Quicken skip duplicates if you ever import the same QFX again, instead of stacking a second copy of every line, a safeguard the original QIF simply could not provide.

Clearing Quicken's verification

Quicken checks who a Web Connect file came from before it will import, using the Intuit headers, chiefly INTU.BID, along with ORG and FID. A file without them, which is every QIF, triggers the OL-221 error, can't verify financial institution. The conversion supplies valid headers so the QFX passes that check. QIF carried no bank identity at all, so this identifying layer is something the conversion adds, not something lifted from the source.

Accuracy and privacy

The QIF's real content, dates, amounts, payees, memos, and check numbers, carries into the QFX unchanged, and the result is reviewable before you import it into Quicken. What the conversion adds, the OFX structure, FITIDs, and Intuit headers, is what Quicken requires, not edits to your transactions. Because the file holds real account activity, it is processed to build the QFX and then deleted automatically, with nothing kept on a server afterward.

How it works

  1. Start with the QIF: Have the QIF file from old Quicken or your legacy program ready.
  2. Restructure to OFX: Convert the QIF to QFX, mapping its D/T/P/M/N codes into OFX STMTTRN blocks with a generated FITID each.
  3. Add the Intuit headers: The conversion adds the INTU.BID, ORG, and FID so Quicken can verify the institution.
  4. Import into Quicken: Import the .qfx into Quicken through its Web Connect path and select the account.

Comparison

AspectQIFQFX
StructureSingle-letter codes (D, T, P)OFX STMTTRN blocks
Intuit headersNoneINTU.BID, ORG, FID
Quicken bank importNot supportedWeb Connect
Transaction IDNoneFITID per transaction
FieldsDate, amount, payee, memo, checkSame, restructured

A legacy QIF converts to a Quicken-ready QFX in about 30 seconds. Convert your statements now.

See pricing

Frequently Asked Questions

Related guides and articles

Try It Yourself

Experience the power of automated conversion

Start Converting