Move QBO Transactions to QIF: What Stays and What Changes

Move basic transactions from a QBO statement into a QIF file while reviewing what the new format can keep. This guide follows the actual controls and output of CSV2QBO, so you can distinguish a completed file conversion from a verified import.

Prepare the right source

Start with a bank or credit-card QBO, not an investment OFX. The source account type is used to choose Bank or CCard in the QIF header.

Work with a copy covering one account and a known date range. An export from a bank or finance application is preferable to a manually reconstructed table because it gives you an original to compare. Never rename a PDF or a company backup to a different extension and expect its contents to become transaction data.

Convert and review

1. Open the QBO to QIF Converter. Use Download sample file or the sample button first if you want to inspect the workflow with fictional data.
2. Choose the original qbo file. The converter reads it locally. Keep an untouched copy for comparing counts and values later.
3. Review the parsed transactions. For QIF or IIF, set the source date order explicitly; OFX-family files already contain structured dates.
4. Inspect the preview and resolve any errors. Read and acknowledge format limitations when they appear, then download the qif output.
5. Compare the downloaded file with the original before importing it into your destination software.

What changes in this format

The output retains dates, signed amounts, payees and memos. FITIDs, bank-specific types and check numbers are not included by this exporter. The conversion panel asks you to acknowledge this boundary before download.

Worked example: verify the meaning, not just the extension

Suppose the QBO contains a debit of -42.50 with a merchant name and a separate reference in MEMO. The QIF keeps the signed amount, payee and reference. It does not carry DEMO-TXN-2 as an OFX FITID. Reimporting the resulting QIF is therefore not the same duplicate-matching operation as uploading the original QBO again.

Set up the destination

For QIF output, check that the target application accepts this format for the intended account type. The exporter keeps basic transactions rather than reconstructing an entire accounting system. Import a small date range into a test account, compare it, and avoid importing the same batch twice.

Common mistakes to avoid

Import into a test account first and compare the transaction count and net movement. A file accepted by one finance application is not a guarantee that every Quicken edition will offer the same account import choices.

An invalid date or amount blocks export rather than quietly removing a transaction. If an error names a record or source row, correct that record in a copy of the source and load it again. A date that is valid in two different orders still needs your explicit choice. Check a date whose day is greater than twelve to confirm the source convention when such a row is available.

A final comparison before import

Compare the first and last transaction dates, the number of main transactions, the total money in and the total money out. Inspect at least one refund or reversal when the source has one. A matching net total alone is insufficient: two errors with opposite signs can cancel each other. Keep the source and output together until the destination has been checked.

The local file limit is 5 MB, and supported financial inputs are bounded to 50,000 records. The destination software may allow less. Files remain in your browser; no account is needed, and no conversion file is stored on CSV2QBO servers.

Use QBO to QIF Converter or explore the other converters. For a related workflow, review a QBO as a spreadsheet.