QIF to QBO Converter QIF to QBO Converter

Download QIF to QBO Converter and Move Quicken Records into QuickBooks

QIF to QBO Converter turns Quicken .QIF exports and QuickBooks .IIF files into a Web Connect .qbo, the format the QuickBooks importer actually reads. CSV and a printable PDF come out of the same run, on your own Windows PC.

QIF to QBO Converter Screenshot.
You left Quicken and the only thing that came with you is a .QIF file. Quicken itself will not take it back into a checking, savings or credit card account, and QuickBooks does not read QIF at all. SoftOrbits QIF to QBO Converter closes that gap on your own machine: it reads the .QIF (or an .IIF export) and writes a Web Connect .qbo with a real financial institution ID inside, so the import is accepted on the QuickBooks side, not just on ours.

How to download and use the QIF to QBO Converter

Install it on Windows.

1. Install it on Windows

1. Install it on Windows

Download the QIF to QBO Converter and run the installer. The institution directory ships next to the program, so the bank list is there from the first launch. There is no account to create and nothing gets uploaded.

Load the QIF or IIF file.

2. Load the QIF or IIF file

2. Load the QIF or IIF file

Drag the file into the window. The program looks inside the file first, so a .qif that is really an IIF export is still parsed as IIF. A text preview opens before anything is written: the detected encoding, then the first rows exactly as the parser read them.

Pick your bank.

3. Pick your bank

3. Pick your bank

Open Lookup on the Financial Institution panel and type the bank name, or the INTU.BID you already have on hands. Rows that carry an INTU.BID come first, because a row without one is a rejected import waiting to happen. The bank code (FI ORG), the FID and the INTU.BID can also be typed by hand if you know them.

Convert, then import.

4. Convert, then import

4. Convert, then import

Choose QBO in the output box and press Convert. In QuickBooks Desktop the file goes in through File > Utilities > Import > Web Connect; in QuickBooks Online it goes in as a manual upload in the bank feed. Either way the transactions land in the feed for review, the same as a download from the bank.

Neither program wants your QIF.

Neither program wants your QIF

Quicken imports QIF only into asset, liability and cash accounts. Checking, savings, credit card, 401(k) and brokerage accounts are excluded, and it is so for many years already. QuickBooks is blunter about it: there is no QIF import there at all. So the archive you exported sits between two programs that both decline it, and it stays there until somebody turns it into the format the importer reads. That conversion is the whole job of QIF to QBO Converter.

Import it twice, get one copy

Re-importing a statement is how books get doubled, and a migration is exactly when people import twice. The FITID hash here does not include the position of a transaction in the file, so adding one row at the top does not renumber everything below it. DTSERVER is taken from the latest date in the document instead of the system clock. Run the same .QIF through the tool tomorrow and the bytes come out identical, which is what lets QuickBooks recognize the transactions it already has.

Import it twice, get one copy.
Nothing travels just to change format.

Nothing travels just to change format

A file that carries a client's whole payment history should not travel anywhere just to change its format. It is a desktop program that opens your .QIF where it already lies and writes the result beside it. You can run it on a workstation that was never given internet access at all, and result is the same file. For a bookkeeper working under a client confidentiality clause that is not a bonus feature, it is the condition for using any converter at all.

QIF and IIF, read by content

Every file is probed before parsing, because QIF and IIF are two different grammars and an IIF file often gets saved as .TXT. On the QIF side the parser handles single-letter codes D, T, P, M and L, the S, E and $ split codes, !Type:Bank, !Type:CCard and !Type:Invst blocks, and files that hold several accounts under separate !Account headers. IIF comes in as !TRNS / !SPL / !ENDTRNS sections with columns read by name. Investment lines survive too, with either an amount or a quantity.

The bank comes from a list

A directory of 6,839 financial institutions ships with the program, and 5,790 of them pass validation and can go into a .qbo as they are. Lookup searches by name and by INTU.BID, since people usually hold that number in hand rather than the bank's official spelling, and it returns rows that carry an INTU.BID first.

A refusal instead of a broken file

QIF to QBO Converter will not write a .qbo without a valid institution ID. Nothing lands on disk and the error is shown word for word, because the alternative is learning about it inside QuickBooks and blaming the converter. Validation rejects only what cannot physically work. An empty value. A space in the middle of the ID. An angle bracket, a control character. The tidy-looking 'digits only' rule would have thrown out 92 of the 6,839 institutions in that list, BB&T and NBCCMD among them.

Splits that keep the total

Split transactions arrive with their parts. In the CSV output a split is one row, since a parent row plus its parts would double the money in a SUM() column, and the parts are not expanded into extra rows. IIF split lines come in with their sign inverted, the way QuickBooks writes them. The CSV header stays English in every interface language: Excel formulas and import maps are keyed to those column names.

Three outputs, one pass

QBO is the default, and the same window also writes CSV for Excel or a printable PDF table, picked in the output box on the Convert page. The .qbo itself is written in CP1252, which is what OFX 1.x defines; declaring UTF-8 in a file QuickBooks is about to read is a guaranteed rejection. Cyrillic that does not fit CP1252 is transliterated and everything else becomes a numeric character reference, so nothing is dropped silently.

See the file before you convert

The preview exists so that nothing about the file is a guess by the time you press Convert. The free trial converts 20 transactions, which is enough to walk your own .QIF through the entire path (convert it, import it, look at what actually landed in the register) and judge the result on your file rather than on a claim.

QIF to QBO Converter
QIF to QBO ConverterDownload the QIF to QBO Converter, run your own .QIF through it, and watch the first 20 transactions land in QuickBooks.

Who needs QIF to QBO Converter Tool

People leaving Quicken

You are moving your own books to QuickBooks and the export you got is a .QIF. It is a move you make once, with a high price of error: either the transactions land correctly, or you retype years of them by hand.

Bookkeepers with a legacy client

A client hands over files from a program nobody runs anymore, often with several accounts inside one .QIF. They have to end up in that client's QuickBooks company, split by account, without a week of typing in between.

Admins preparing files for accounting

You collect .QIF and .IIF files from clients and branch offices and owe the accounting team one predictable import path. The program installs per workstation on Windows, keeps its institution directory as a plain text file you can open, and you can refresh that directory yourself in Notepad, or point the program at another copy of it, when Intuit changes its bank list.

QIF to QBO Converter

QIF to QBO Converter

Languages
File Size

9 Mb

Version

1.0

Last updated on

25/06/26

$ 29.99

🖥️ System Requirements

  • Windows 11/10/8.1/8/7 (32/64 bit)
  • Intel i3, AMD Ryzen 5 or above
  • 4 GB of RAM or above
  • NVIDIA® GeForce® series 8 and 8M, Intel® HD Graphics 2000, Quadro FX 4800, Quadro FX 5600, AMD Radeon™ R600, Mobility Radeon™ HD 4330, Mobility FirePro™ series, Radeon™ R5 M230 or higher graphics card with up-to-date drivers
  • 1280 × 768 screen resolution, 32-bit color
  • 1 GB of free hard disk space or above

🙋 Frequently Asked Questions

You convert it first, because QuickBooks has no QIF import of its own. Run the .QIF through QIF to QBO Converter, pick your financial institution, save the .qbo, then in QuickBooks Desktop use File > Utilities > Import > Web Connect and select that file. They arrive in the bank feed as items waiting to be matched, not as posted entries.

Quicken opens it, though not into every kind of account, as described above. Older finance applications and a few banks still write QIF as well. On Windows you can also open the file in the converter and just read the preview (count, encoding, first lines) without importing it anywhere. A .QIF is plain text, so Notepad shows it too, but the single-letter codes will not tell you much on their own.

Short answer: through the Web Connect import that sits in the File menu, under Utilities. Long answer: two things have to be true before that works. The file needs an institution ID QuickBooks recognizes, and your QuickBooks has to be recent enough. A version three years old or older will not import .qbo files at all, whoever made them. That limit belongs to Intuit and no converter can lift it, so check your version before you spend an evening on the file.

For bank transactions the practical list is short. Web Connect reads .qbo and nothing else. QuickBooks Online also takes .qfx and a CSV within its own size and column limits, while IIF stays in QuickBooks Desktop for lists and journal entries. QIF is not on that list anywhere, which is the reason this page exists. The converter reads .QIF and .IIF on the input side and gives the importer the .qbo it expects.

QuickBooks takes data in three ways. One is a live bank feed, another is a file you import yourself, and the third is typing. A migration from another program falls into middle one, because the old program is not a bank and cannot be connected to anything. So the whole task becomes a file task. Produce a .qbo the importer accepts, import it, then review the transactions in the feed before you match them.

Yes, through the bank feed as a manual upload rather than through the Desktop menu. The requirement about the institution ID does not change: the ID inside the file still has to be one Intuit knows about. That is exactly why the bank is picked from the directory here instead of being typed as a number somebody guessed.

Search by INTU.BID first and not only by name, because the same institution is often listed under a spelling you would never guess, and the search matches that number too. If it is genuinely absent, the panel accepts FID and INTU.BID typed by hand, and the common workaround is to use the ID of an institution QuickBooks does accept. The transactions are yours either way; the ID only tells QuickBooks which downloader to trust. What will not happen is a file written with an ID that cannot work, handed to you as a success.

Rate QIF to QBO Converter

  • Windows 7
  • Windows 8
  • Windows 10
  • Windows 11
Author: SoftOrbits (English)
Avg. rating: 4.5 from 842 votes

Risk-free download

14-day money-back guarantee
Full refund, no questions asked
progressive-webapps/apis/offline-first Created with Sketch.
100% offline
Your files never leave your PC
Safe & secure download
Directly from the official website
No sign-up required
No account or email to get started
Trusted since 2006
Desktop software for Windows