Conversion

Convert a Legacy QIF to a QBO for QuickBooks

QuickBooks dropped QIF import years ago, so a QIF won't load. Convert QIF to QBO, restructuring its D/T/P codes into Web Connect blocks with FITIDs QuickBooks accepts.

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

TL;DR - Quick Summary

Intuit removed QIF import from QuickBooks years ago, so a QIF file will not load: QuickBooks Desktop takes only QBO Web Connect files. Converting QIF to QBO restructures its single-letter codes into OFX statement blocks, generates a FITID for each transaction, and sets a financial institution ID QuickBooks accepts.

QuickBooks no longer imports QIF

QIF is a legacy Quicken text format, and Intuit dropped direct QIF import from QuickBooks years ago. QuickBooks Desktop now accepts bank transactions only through QBO Web Connect files, and QuickBooks Online takes QBO or OFX. So a QIF exported from old Quicken or another legacy program has nowhere to go in QuickBooks as-is. Converting the QIF to QBO is the only path to get that data in, which is why the conversion exists at all rather than a simple rename.

QIF and QBO are different formats

The two files are not variants of each other. QIF uses single-letter field codes, one per line, D for the date, T for the amount, P for the payee, M for a memo, N for a check or reference number, with a caret ending each transaction. QBO is OFX under the hood, SGML markup with a STMTTRN block per transaction. Converting means restructuring the QIF's coded lines into those OFX blocks, not renaming the file, so each QIF entry becomes a properly tagged QBO transaction QuickBooks can read.

FITID and duplicate detection

QBO gives every transaction a FITID, a unique identifier QuickBooks uses to catch duplicates. QIF has no such field, so the conversion generates a FITID for each entry. The payoff is real: if you import the same QBO twice, QuickBooks recognizes the repeated FITIDs and skips the transactions it already has, instead of doubling them. That deduplication only works because the conversion assigns stable, unique IDs the QIF never carried.

Choosing a financial institution ID

A QBO file also names the institution through an FID, and QuickBooks checks it. The conversion sets one, and there is a known workaround when a bank is not in QuickBooks's list: you select the FID of another supported institution so the file still imports. QIF carried no bank identity at all, so this is one more piece the conversion supplies to satisfy QuickBooks's Web Connect import rather than something lifted from the source file.

Accuracy and privacy

The QIF's real content, dates, amounts, payees, memos, and check numbers, carries straight into the QBO, and the result is reviewable before you import it into QuickBooks. What the conversion adds, the OFX structure, FITIDs, and institution ID, is scaffolding QuickBooks requires, not changes to your transactions. Because the file holds real account activity, it is processed to build the QBO and then deleted automatically, with nothing kept on a server afterward.

How it works

  1. Start with the QIF: Have the QIF file exported from Quicken or your legacy program ready.
  2. Convert to QBO: Convert the QIF to QBO, restructuring its D/T/P/M/N codes into OFX STMTTRN blocks with a generated FITID each.
  3. Set the institution ID: Set a financial institution ID; if your bank is not listed, choose another supported institution's FID.
  4. Import into QuickBooks: Import the QBO into QuickBooks Desktop through File, Utilities, Import, Web Connect files.

Comparison

AspectQIFQBO
StructureSingle-letter codes (D, T, P)OFX SGML STMTTRN blocks
QuickBooks importNot supportedWeb Connect
Transaction IDNoneFITID per transaction
Institution IDNoneFID required
FieldsDate, amount, payee, memo, checkSame, restructured

A QIF file converts to a QuickBooks-ready QBO in about 25 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