QuickBooks Desktop can't import a QIF directly anymore. Convert any bank or credit card QIF to a .qbo Web Connect file that imports through File, Utilities, Import.
No account needed for your first conversions. We never store your bank login.
QuickBooks Desktop no longer imports bank or credit card transactions from a QIF file directly. The transaction file it does import is a .qbo Web Connect file, so the reliable path is to convert your QIF export to a .qbo first, then bring it in through File, Utilities, Import, Web Connect Files. The converter at the top of this page does that conversion in one pass, and the same .qbo also works in QuickBooks Online.
Drop in a QIF file from Quicken, Microsoft Money, or any bank or finance tool that exports QIF. You get back a .qbo built to the Web Connect spec QuickBooks Desktop reads natively, plus Excel and CSV copies. The converter reads each transaction's QIF tags, the date (D), payee (P), and amount (T), and checks the parsed total against your original file before you download, so nothing is dropped on the way into Pro, Premier, Enterprise, or Accountant.
| Method | What it handles | Works for bank transactions? | Effort |
|---|---|---|---|
| Convert QIF to .qbo, import via Web Connect | Any bank or card QIF export | Yes, native import | One upload, no field mapping |
| QuickBooks Desktop QIF import | Removed for transactions in recent versions | No, not supported anymore | Not available |
| IIF file import | Transactions, but you build the IIF by hand | Yes, error prone | High, technical formatting |
| Direct Connect bank feed | Live feed from supported banks | Yes, if your bank supports it | Setup and login, recent dates only |
| Manual entry | Anything | Yes | Very high for large files |
Built for the QIF files Quicken and finance tools actually export, checked before it exports.
The converter adds up the transactions it parsed and matches that to your file total before you export, so nothing is silently dropped.
Valid OFX 1.02 with QuickBooks Web Connect headers. Online and Desktop import it as a standard bank feed.
Date, payee, and amount are read straight from the QIF tags, so there is nothing to map and no layout to match.
Bulk upload for catch-up and cleanup work. Each file gets its own reconciliation check and its own exports.
Mixed date formats, apostrophe years, currency symbols, and split lines in a QIF are cleaned up and summed before the .qbo is built.
One conversion, three files: the .qbo for QuickBooks, an XLSX to review, and a CSV for everything else.
Three steps. No column-mapping wizard.
Drag in a .qif export from Quicken, your bank, or another finance tool. Any QIF type works.
Every transaction is parsed and checked against your file total. You see the rows before exporting.
Download the .qbo and import it as a Web Connect bank feed. Excel and CSV are in the same download.
The specifics that decide whether the import is clean. If your case is not here, message us in chat.
Not for bank or credit card transactions. QuickBooks Desktop removed QIF transaction import in recent versions, so a QIF from Quicken or Money will not load on its own. To get bank or card activity in, convert the QIF to a .qbo Web Connect file and import that instead, which is exactly what the converter above produces.
Convert the QIF to a .qbo file first, then import it. Upload your QIF in the converter above, download the .qbo, and in QuickBooks Desktop go to File, Utilities, Import, Web Connect Files. Pick the .qbo, choose the matching account, and the transactions drop into the Bank Feeds center for review and matching.
QuickBooks Desktop imports bank and credit card transactions from a .qbo Web Connect file, which is OFX text with a financial institution block and a unique ID on every transaction. It no longer reads QIF transaction files, so a QIF has to be converted to .qbo before Desktop will accept it.
In QuickBooks Desktop, open the File menu, choose Utilities, then Import, then Web Connect Files. Select your .qbo file and click Open. QuickBooks asks whether to use an existing account or create a new one, then loads the transactions into the Bank Feeds center, where you review, match, and accept them.
Because QuickBooks Desktop dropped QIF transaction import; it takes .qbo Web Connect files for bank and card activity now. Renaming a QIF to .qbo does not help, since QuickBooks reads the file contents, not the extension. Convert the QIF into a real .qbo with the tool above and the import goes through.
Upload your QIF file in the converter above. It reads the date (D), payee (P), and amount (T) tags from each record, normalizes the dates, signs amounts correctly, and writes a valid .qbo with a unique ID per transaction. Download the file and import it through File, Utilities, Import, Web Connect Files.
Yes, once you convert the card QIF to a .qbo. Export the activity from your credit card or from Quicken, convert it here, and import the .qbo into the matching credit card account in QuickBooks Desktop. The converter sets charges as negative and payments as positive, the sign convention card imports need to balance correctly.
Export the account from Quicken as a QIF, then convert that QIF to a .qbo first. The converter above reads the QIF tags directly, so you do not need any intermediate step. After converting, import the .qbo through File, Utilities, Import, Web Connect Files and pick the matching account.
Web Connect (.qbo) import works in QuickBooks Desktop Pro, Premier, Enterprise, and Accountant, and in QuickBooks for Mac. The steps are the same across them: File, Utilities, Import, Web Connect Files. The .qbo built by the converter follows the standard Web Connect spec, so it imports into any of these editions.
A single .qbo file can hold a full year of transactions, far more than the small CSV uploads QuickBooks Online caps at 350 KB. For very large histories, splitting the file by account or by quarter keeps each import easy to review. The converter handles thousands of QIF records in one pass.
A QIF is a tagged Quicken text file with records separated by a caret, which is why QuickBooks Desktop no longer imports transactions from it. A .qbo is a Web Connect file QuickBooks reads natively, with bank identity and a unique ID per transaction. Converting QIF to QBO turns an unsupported export into the file Desktop expects.
Upload your QIF export in the converter above. The tool reads the date (D), payee (P), and amount (T) tags from every record, normalizes the dates to a single format, signs each amount correctly, and reconciles the parsed total against your file. Download the .qbo, then in QuickBooks Desktop go to File, Utilities, Import, Web Connect Files and pick it. The whole pass takes under a minute, with no IIF formatting and no mapping wizard.
Bookkeepers and accountants on QuickBooks Desktop rely on it most, because clients hand over a year of bank and card QIF exports that Desktop has no way to import on its own anymore. Businesses still on Pro, Premier, or Enterprise use it to backfill accounts the bank feed never reached, and anyone moving off Quicken or Microsoft Money uses it to load historical transactions without keying them in by hand.
Upload a QIF export, get a QuickBooks-ready .qbo back in seconds. No card to try it.
Working from a different source or tool? Use the QIF to QuickBooks Online converter if your books are online, turn any Quicken file into a .qbo with the QIF to QBO converter, handle card files on the credit card QIF to QuickBooks page, fix a failed import with the Web Connect import error guide, batch a backlog with the bulk QIF to QBO converter, learn what a .qbo file is, or compare the best QIF to QBO converters before you choose a tool. To convert a file now, start on the home page.
For the solo bookkeeper running a monthly close in QuickBooks.
USD / month
billed $288 yearly
For a firm or finance team converting across many clients and currencies.
USD / month
billed $888 yearly
For multi-bookkeeper firms managing many client books at scale.
USD / month
billed $2,988 yearly
