Skip to main content
Skip to content
FREE TOOL — BROWSER-BASED

Convert IIF Files to Sage Format Instantly

Moving from QuickBooks Desktop to Sage? Convert IIF transaction files to Sage CSV. Works with Sage 50, Sage Business Cloud, and Sage Intacct.

100% PrivateInstantIIF Format

FAQ

Convert to
Sage
Questions

Can't find what you're looking for? Reach out to our support team.

Contact Support

It converts bank statement files from multiple formats — QBO, OFX, QFX, IIF, QIF, CSV, MT940, CAMT.053, and XLSX — into a Sage Accounting-compatible CSV file that you can import directly into Sage 50, Sage Business Cloud, or Sage Intacct via their bank statement import feature.

Why Convert IIF Files to Sage?

IIF (Intuit Interchange Format) is the proprietary export format used by QuickBooks Desktop. When businesses migrate from QuickBooks Desktop to Sage Accounting, they often have years of historical transaction data locked in IIF files. Sage cannot import IIF files directly — the tab-delimited TRNS/SPL/ENDTRNS structure is completely incompatible with Sage's CSV-based bank import feature.

PrimeConnect's free IIF to Sage converter solves this migration challenge. Upload your IIF file and the tool parses every transaction group — flattening the complex multi-line TRNS/SPL/ENDTRNS blocks into simple rows with dates, descriptions, and amounts — then outputs a properly formatted Sage CSV. The converter handles check numbers, journal entries, deposits, and payments, making it the fastest way to move QuickBooks Desktop data into Sage 50, Sage Business Cloud, or Sage Intacct.

Understanding the IIF File Format

IIF is a tab-delimited text format that QuickBooks Desktop uses for importing and exporting transaction data. Unlike CSV files which have one row per record, IIF uses a multi-line structure for each transaction:

  • TRNS line — The primary transaction line containing the transaction type (CHECK, DEPOSIT, JOURNAL, BILL, etc.), date, account name, amount, payee name, and memo. This is always the first line of a transaction group.
  • SPL line(s) — Split lines representing the contra-side entries in double-entry bookkeeping. A simple check has one TRNS and one SPL line. Complex journal entries may have multiple SPL lines allocating amounts across different accounts.
  • ENDTRNS line — Marks the end of a transaction group. The converter knows to process the accumulated TRNS/SPL data at this point.
  • Header rows — Lines starting with !TRNS and!SPL define the column structure. These are used to map tab positions to field names (DATE, AMOUNT, NAME, MEMO, ACCNT, etc.).

Our converter parses all of these elements and extracts clean transaction rows suitable for Sage import. Each TRNS line becomes a single row in the Sage CSV with Date, Description (from NAME + MEMO), and Amount fields.

Migrating from QuickBooks Desktop to Sage

QuickBooks Desktop to Sage is one of the most common accounting platform migrations, particularly for UK and European businesses that need stronger multi-currency support and VAT compliance features. Here is a step-by-step migration workflow:

  1. Export from QuickBooks Desktop — Go to File → Utilities → Export → Lists to IIF or use the Timer Export for transactions. You can also export specific date ranges using Reports → Transaction Detail → Export to IIF.
  2. Convert IIF to Sage CSV — Upload the IIF file to this converter. The tool flattens the TRNS/SPL/ENDTRNS structure into simple rows and lets you choose 3-column or 4-column Sage format plus your preferred date format.
  3. Import into Sage — Follow the bank statement import process for your Sage edition (see below). Review the preview carefully to ensure all transactions appear correct.
  4. Set up Chart of Accounts — Sage uses different default account names than QuickBooks. Use our Chart of Accounts Generator to create a Sage-compatible chart of accounts for your industry.

Sage 50 vs Sage Business Cloud: Import Differences

While both products accept CSV bank imports, the import process differs significantly:

Sage 50 (Desktop)

Sage 50 is a desktop application (also known as Sage 50cloud Accounts in the UK). Bank statement imports go through the Bank Statement wizard: Bank Accounts → select account → Bank menu → Statement → Import. The wizard provides flexible column mapping, so even if your CSV has extra columns, you can map just the ones Sage needs. This makes Sage 50 very forgiving with different CSV layouts.

Sage Business Cloud Accounting

Sage Business Cloud is the web-based version. Navigate to Banking → select your bank account → Import Statement → CSV. The cloud version is more strict about CSV structure — it expects either the 3-column or 4-column format with a header row. Our converter outputs CSV in exactly the format Sage Business Cloud expects, so imports should work on the first try.

Common IIF to Sage Conversion Issues

  • Multi-line journal entries — IIF journal entries can have many SPL lines distributing amounts across multiple accounts. The converter creates one Sage CSV row per TRNS line (the primary entry), which is what Sage expects for bank transaction imports.
  • US date format (MM/DD/YYYY) — IIF files from QuickBooks Desktop use US date format by default. If your Sage installation uses UK dates (DD/MM/YYYY), select the appropriate format in the converter settings before downloading.
  • Account names in IIF — IIF files reference QuickBooks account names (e.g., “Checking”, “Accounts Payable”). These are used for the converter's internal parsing but do not appear in the Sage CSV output, which only contains Date, Description, and Amount.
  • Class tracking and custom fields — QuickBooks Desktop supports class tracking and custom fields in IIF exports. These fields are not included in the Sage CSV output since Sage's bank import does not support them. Use Sage's own categorization features after import to replicate this functionality.

Related Free Accounting Tools

The IIF to Sage converter is part of PrimeConnect's complete suite of free financial file conversion and utility tools: