A QIF to QFX converter rewrites an old Quicken Interchange Format export as a QFX Web Connect file. Quicken's help pages disagree on whether current Quicken takes QIF into bank and card accounts, so test a QIF import first. A converter earns its place when that import is refused, or when you want IDs that stop duplicate imports.
Does current Quicken still need a QIF to QFX converter?
Current Quicken may not need a QIF to QFX converter, but its help is split. Its page on importing data from a QIF file says you can now import any account type using QIF. Its guide to importing data into Quicken for Windows says QIF import isn't available for checking, savings or credit card accounts. Test a QIF import first.
That answer changes the job. Before you buy or install anything, open your Quicken and look at the file import menu. If it offers a QIF import and lets you pick a checking or credit card account as the target, test it with a copy of your data file. If the import works, you are done, and the QIF file goes in as it is.
A converter still makes sense in three situations:
- Quicken refuses the QIF import. Older releases did not let QIF in for every account type, and Quicken's Windows import guide still says the same for bank and card accounts. A QFX file goes through the Web Connect route instead, which is built for bank and card accounts.
- You will mix the history with bank downloads. A QFX file carries a transaction ID on every line. Quicken can use those IDs to recognize a line it has already seen. A QIF file has no such ID.
- Another program wants QFX. Some budgeting and personal finance tools read QFX or OFX but not QIF. For those, the conversion is the only way in.
If none of those apply, skip the conversion and keep things simple. Every extra step is one more chance for a date or a sign to change.
What the QIF file actually is
QIF is a plain text format. Each transaction is a short block of lines, and each line starts with a single letter that says what it holds. Quicken and many banks used it for years to move data between programs. You can open any QIF file in a text editor and read it, which helps a lot when you check a conversion later.
Why older Quicken releases blocked QIF imports into bank accounts
Quicken limited QIF imports into bank accounts because QIF cannot identify a bank, an account number or a single transaction. Web Connect files carry all three, so bank and card data had a better route. One Quicken help page calls the limit a thing of older versions; its Windows import guide still applies it.
The limit was practical rather than arbitrary. A QIF file only says what kind of account its lines belong to, with a header line such as !Type:Bank or !Type:CCard. It does not say which bank produced the file or which of your accounts it belongs to. When Quicken reads a block of QIF lines, it has no way to tell whether those lines are already in your register.
A Web Connect file solves both problems. It names the institution, it states the account, and it labels every transaction with an ID. That difference is a reasonable way to read why older releases treated QIF with caution for accounts that link to a bank.
If you are still on one of those releases, you have two choices. You can convert the QIF to QFX and import it through Web Connect. Or you can import the QIF into an account type your version does allow and move the lines across by hand. The conversion is usually less work once you have more than a few dozen lines.
The upgrade route is worth a thought too. If your Quicken is old enough to block the import, it may also be old enough to have lost online services. Check what your version still supports before you spend time on a conversion that only helps for a short while.
What a converted QFX file must carry for Quicken to accept it
A converted QFX file must carry a header, an institution block, an account block with a number and type, a statement date range and a transaction list where each line has a type, date, amount and unique ID. A QIF file supplies only the transaction details, so the converter fills in everything else.
QFX is Intuit's version of OFX, the Open Financial Exchange standard maintained by the FDX OFX Work Group. A QFX file adds a few Intuit-specific lines to an OFX statement, the most important being the Intuit bank ID. Quicken reads those lines to decide which institution the file came from.
Here is what a converter has to produce, and where each value comes from:
- Institution details. The organization name, its numeric ID and the Intuit bank ID. A QIF file has none of these. A careful converter asks you for them or copies them from a real QFX download from the same bank.
- Account number and type. The QIF header gives the type:
Bankbecomes checking or savings, andCCardbecomes a credit card. The account number must come from you. - Currency. Usually USD for a US account. QIF does not state one.
- Start and end dates. Taken from the first and last transaction, unless you set them to match a statement period.
- A transaction ID per line. The converter has to build these. Stable IDs, such as the date plus a counter, keep a second conversion of the same file from looking like new data.
The institution block is the part most likely to fail. Quicken tries to match it to a bank it knows. A made-up value can lead to a refusal or to a prompt asking which account to use. If you still have access to the bank, download one real QFX file, even a short one, and keep it as a reference for those values.
QIF to QFX field mapping, line by line
Each QIF line letter maps to one QFX tag: D to the posted date, T to the amount, P to the payee name, M to the memo and N to the check number. The converter adds a transaction type and an ID that QIF never had, and it drops category and split lines that QFX has no room for.
The table below follows one transaction through the conversion. The values are examples made up for this post.
| QIF line | Meaning | Example QIF value | QFX tag | Example QFX value |
|---|---|---|---|---|
| D | Date | 11/07'25 | DTPOSTED | 20251107 |
| T | Amount | -86.15 | TRNAMT | -86.15 |
| P | Payee | Corner Hardware | NAME | Corner Hardware |
| M | Memo | Shelf brackets | MEMO | Shelf brackets |
| N | Check number | 2214 | CHECKNUM | 2214 |
| L | Category | Home:Repairs | (none) | Dropped |
| (none) | Type | Not in QIF | TRNTYPE | DEBIT or CHECK |
| (none) | Unique ID | Not in QIF | FITID | 20251107-001 |
| ^ | End of record | ^ | Closing tag | End of the transaction block |
Three rows in that table deserve a second look.
The date line
The QIF date 11/07'25 uses an apostrophe before a two-digit year, a style Quicken used for years after 1999. The converter has to turn it into 20251107. It also has to decide whether 11/07 is November 7 or July 11. US Quicken files put the month first, but a QIF file from software made elsewhere may not. Find a date with a day above 12 in the file to settle the order before you trust the output.
The category line
The L line holds the Quicken category. QFX is a bank statement format, and banks do not send categories, so the tag does not exist. Expect to recategorize after the import, or let Quicken's own rules do it. Keep the original QIF as a reference for what you chose before.
The ID line
FITID has no QIF source at all. The converter builds it. Ask the tool how. An ID built from the date and a counter stays the same when you convert the same file twice. An ID built from the time of conversion changes on every run.
Header values the converter must ask for
Beyond the transaction lines, the converter needs about five values that only you can give it: the bank name, the account number, the account type, the currency and the date range. A tool that never asks for them is guessing. If the bank still exists, a real QFX download is the most reliable place to copy the institution values from.
Will a QIF to QFX conversion duplicate transactions Quicken already has?
A QIF to QFX conversion can duplicate transactions when the account already holds lines from bank downloads. The converter's made-up IDs never match the bank's real ones, so Quicken sees every converted line as new. Trim the QIF to dates before your first download, or import into a new account.
This is the most common way the job goes wrong. Someone has an old Quicken file with ten years of history and a current Quicken account that has been downloading from the bank for two years. They convert the whole QIF and import it into the current account. The two years that overlap now appear twice.
Quicken's duplicate check relies on the IDs. A bank-issued ID looks nothing like a converter's ID, even for the same purchase on the same day.
Before you convert, do these three things:
- Find the date of the oldest downloaded transaction in the target account.
- Open the QIF in a text editor and delete every record on or after that date. Each record ends with a
^line, so cut whole records only. - Convert the trimmed file and import it.
Opening balances need the same care. If the target account already has an opening balance entry, imported history from before that date changes the running balance. Compare the balance after import with a statement from the same date. If it is off by the old opening balance, adjust that entry rather than deleting real transactions.
Loan accounts raise the same issue in a different program. If the QIF came from a Quicken loan account and the loan now lives in QuickBooks, the converted history is the wrong tool. Connecting a loan account to QuickBooks Online covers how to set up that balance instead.
QIF history that is better left as QIF
Some QIF history is better left alone. If the file covers closed accounts, years you only keep for tax records, or data with categories you want to keep, a conversion loses detail and adds work. Store the original QIF and a printed or PDF register instead, and convert only what you will actually use.
Ask yourself what the history is for. A register you will never reconcile again does not need to be inside your current Quicken file. A text file in an archive folder is easy to search. Quicken can also print an old register to PDF if you still have a working copy of it.
Some files are better sent somewhere other than QFX:
- You moved to a different program. If the target is a tool that wants plain OFX, see the QIF to OFX converter guide instead. The fields are nearly the same, but the Intuit lines are left out.
- You have QFX files already and need OFX. That is a smaller change, covered in converting QFX to OFX.
- You are moving to QuickBooks. QuickBooks Desktop reads QBO rather than QFX, as the CSV vs QBO comparison explains. The usual path is a spreadsheet: lay out the date, amount and payee lines as columns and run them through a CSV to QBO converter.
If your recent records exist only as PDF bank statements, SimpleBankConvert may help with that part. It is in early access and is being built to turn PDF statements into CSV or QBO files for QuickBooks, not into QFX for Quicken. See the SimpleBankConvert homepage for what it covers today.
A last check before you start: count the records in the QIF by searching for the ^ lines, and write the number down. After the import, the register should show the same count for the same dates. If the numbers differ, look for records that the converter merged or skipped before you trust the rest.