QIF to QBO: Import Quicken Data Into QuickBooks

You have a .qif file, QuickBooks wants a .qbo file, and no amount of renaming the extension will bridge the gap. QIF is the Quicken Interchange Format: a plain-text format from the late 1980s that Quicken itself deprecated for bank downloads two decades ago. QuickBooks has never accepted it. Yet QIF files keep turning up. Some banks still offer them as a download option, old Quicken and Microsoft Money archives are full of them, and plenty of legacy finance tools export nothing else. This guide explains what a QIF file actually contains, why QuickBooks rejects it, and three honest ways to get that data into QuickBooks Desktop or QuickBooks Online.

What Is a QIF File?

QIF stands for Quicken Interchange Format. Intuit created it in the late 1980s so early versions of Quicken could exchange data with other programs and with itself across upgrades. It is pure plain text: no markup, no encryption, no checksums, no bank identifiers. Each transaction is a short block of lines, where the first character of every line is a code that says what the rest of the line means. A caret on its own line ends the record.

Here is what a simple bank-account QIF looks like inside:

!Type:Bank
D01/15/2026
T-42.50
PGROCERY STORE
MDebit card purchase
^
D01/16/2026
T1250.00
PPAYROLL ACME LLC
^
D01/18/2026
T-9.99
PSTREAMING SERVICE
LEntertainment
^

The letter codes are the entire "format." The common ones:

• !Type: header that declares the account type (Bank, CCard, Cash, Invst)
• D is the transaction date
• T is the amount (negative for money out, positive for money in)
• P is the payee or description
• M is an optional memo
• L is an optional Quicken category or transfer account
• ^ marks the end of one transaction

That simplicity made QIF popular, and it is why so many old tools still write it. It is also the format's fatal flaw. There is no unique ID per transaction, no declared date convention, no currency field, and no way for the receiving program to verify it parsed the file correctly. Quicken itself moved on: starting with the 2005 US editions, Quicken stopped accepting QIF imports for checking, savings, and credit card accounts and pushed everyone to QFX (Web Connect) instead. QIF has been a legacy format ever since.

Why QuickBooks Rejects QIF

QuickBooks has never supported QIF, in any version, Desktop or Online. This surprises people because Quicken and QuickBooks are both Intuit products, but the two use different import pipelines:

• QuickBooks Desktop imports bank data through Web Connect, which requires a .qbo file. A QBO file is structured OFX-style markup that must include a financial institution ID that QuickBooks validates before importing. QIF has no field for any of that.
• QuickBooks Online accepts QBO, QFX, OFX, and CSV uploads. QIF is not on the list, and renaming .qif to .qbo does not work because the file contents are completely different formats, not just different extensions.
• No FITIDs. QuickBooks relies on the FITID (a unique per-transaction ID) inside QBO and OFX files to detect transactions it has already imported. QIF records have no IDs at all, so even if QuickBooks parsed the file, it would have no reliable way to prevent duplicates.
• Ambiguous dates. A QIF line like D01/02/26 is unparseable without knowing whether the file came from US or UK software. QuickBooks would have to guess, and guessing wrong corrupts a ledger silently.

In short, QIF lacks everything QuickBooks needs to import safely. If you want the deeper background on how QBO, OFX, and CSV differ, our QBO vs OFX vs CSV guide covers the three formats side by side. What follows are the three realistic paths from QIF to QuickBooks.

Method 1: Convert the Original PDF Statement to QBO (Recommended)

Most QIF files are middlemen. The data usually started life as bank transactions, which means there is almost always a PDF statement covering the same date range sitting in your bank's document archive. If that is your situation, the best move is to ignore the QIF file entirely and convert the source statements to QBO. You sidestep every QIF weakness at once: the dates on a statement are unambiguous, the amounts are printed with running balances you can verify against, and the QBO output carries proper FITIDs so QuickBooks can deduplicate future imports.

This route also works when the QIF file itself is damaged, truncated, or exported with the wrong date convention, which is common with files that have been passed between old programs for years. The statement is the source of truth. Going back to it is cleaner than repairing a lossy copy.

Method 2: Use a Dedicated QIF to QBO Converter Utility

If your QIF data never came from a bank statement (manually entered Quicken registers, cash accounts, or data migrated out of Microsoft Money, for example), there is nothing to go back to, and you need a tool that converts the QIF file itself. A small category of desktop conversion utilities exists for exactly this job. Most are paid software with trial versions, and they all work roughly the same way: parse the QIF, ask you to confirm the date convention and account type, generate synthetic FITIDs, and write out a QBO file that QuickBooks will accept.

A few things to check before trusting the output of any QIF converter:

• Date convention setting. The tool must let you declare whether the file uses month-first or day-first dates. If it silently assumes one, verify a few transactions after conversion.
• Two-digit year handling. Ask what century the tool assigns to a year like 98 or 03. Old Quicken exports mix conventions, including an apostrophe notation for years after 1999.
• FITID generation. Because QIF has no transaction IDs, the converter invents them. Converting the same file twice with different settings can produce different IDs, which defeats QuickBooks duplicate detection. Convert once, verify, then import.
• Test with a small file first. Cut a dozen transactions into a test QIF, convert, import into a scratch QuickBooks account, and confirm dates and signs are right before running the full history.

Method 3: QIF to CSV in Excel, Then CSV Into QuickBooks Online

Because QIF is plain text, you can restructure it into a CSV yourself with nothing but Excel, then use QuickBooks Online's native CSV upload. This is free but manual, and it only works for QuickBooks Online. QuickBooks Desktop does not accept CSV bank imports.

The catch: a CSV import has no FITIDs either, so QuickBooks falls back to fuzzy duplicate matching on date and amount. If you later connect a bank feed or import an overlapping file, expect to review potential duplicates by hand.

Which Method Should You Use?

Rule of thumb: if a bank statement exists for the period, use Method 1. Use Method 2 when the data has no statement source and the file is too large to rebuild by hand. Use Method 3 for small, one-off files going into QuickBooks Online.

QIF Pitfalls to Watch For

Whichever method you choose, these are the failure modes that bite people during QIF conversions. All of them trace back to how little information the format actually records.

Frequently Asked Questions

Related Articles