A Microsoft Money archive nothing will open
Money was discontinued and its exports were QIF. Converting to CSV gives you a file any spreadsheet reads, which is a far better long-term home for records you may need years from now.
Get transactions out of an old QIF archive as CSV, with the ambiguous date order resolved openly rather than guessed at.
Maintained by Roshan · Page and browser-local behavior last reviewed August 31, 2026.
Reads a QIF file in this tab and writes the transactions out as CSV. QIF is the format old finance software exported, so this is usually about getting data out of an archive. Nothing is uploaded.
Tested with a mixed file containing an apostrophe year, a comma thousands separator, a three-way split and an account header block. The split stayed a single row at its full amount rather than being expanded, and a deliberately ambiguous file reported that month-first had been assumed instead of presenting the guess as a reading.
More in this category
Find related browser-local tools for nearby tasks without starting another search.
Browse all developer and data tools toolsQuicken Interchange Format is the oldest thing on this site by some margin. It dates from an era when a transaction was a handful of one-letter codes on consecutive lines — D for the date, T for the total, P for the payee — terminated by a caret on a line of its own. Nearly everything exported it: Microsoft Money, early Quicken, GnuCash, a generation of building society and credit union systems. Nearly nothing reads it now, which is a problem when the file is the only remaining copy of a decade of records. This page reads it in your browser and writes out CSV. One thing deserves saying before you start, because it is the reason most QIF conversions go quietly wrong: the format never recorded whether a date is written day-first or month-first. Every other converter has to pick one. This one tells you which it picked and why, and lets you overrule it.
Money was discontinued and its exports were QIF. Converting to CSV gives you a file any spreadsheet reads, which is a far better long-term home for records you may need years from now.
British software wrote day-first; American converters assume month-first. If the preview shows implausible dates, switch the order and the whole file re-reads from the copy already in the tab.
Because the format never stored the day/month order and most converters assume American month-first. A British or Australian export then reads 06/07 as 6 July instead of 7 June. Here the order is inferred where the digits prove it, stated when it had to be assumed, and switchable.
No. A file with no header is read as bank transactions, which is what most exports are. A file declaring an investment or list type is reported instead, since those records are not payments and treating them as payments would be misleading.
The payment stays one row for its full amount, with a note in the memo saying how many split lines it had. Expanding splits into rows would count the same money twice and make the file's total disagree with the account.
Because QIF has no currency field. Anything in that column would be invented rather than read. If you know the currency, add it in the spreadsheet after converting.
Convert an OFX bank statement to CSV in your browser. No upload, no bank connection, no account. Transaction dates, payees, amounts and FITIDs come out as columns.
Convert a Quicken QFX file to CSV in your browser. Works without a Quicken subscription. No upload, no bank login, no account needed.
Convert a QuickBooks .qbo Web Connect file to CSV in your browser. No upload, no QuickBooks licence, no bank feed. See every transaction before you import.
Reconcile bank, ledger, processor and marketplace exports in your browser. Write your own matching rules, review the exceptions, and export a full audit package. The files are not uploaded.
Convert CSV to a JSON array locally. Parse quoted commas, embedded newlines, BOM files, duplicate headers, sparse rows, and optional safe value types.