Mint CSV to Beancount
Convert the Mint transactions archive you downloaded before Mint closed into balanced double-entry Beancount transactions — the Transaction Type column is mapped, so debits and credits get the right sign.
Column mapping verified against a real Mint export
How to export your Mint transactions
- 1
There is no live export to run: Mint shut down on 23 March 2024. Find the CSV you downloaded before then — usually “transactions.csv” in your Downloads folder, or inside the ZIP a Mint export tool produced.
- 2
Open it and check the first line reads Date, Description, Original Description, Amount, Transaction Type, Category, Account Name, Labels, Notes. That is the archive layout this preset is mapped to.
- 3
The archive holds every account at once, so keep the rows for a single Account Name, copy them together with the header line, and paste them below.
The sign lives in Transaction Type, not on the amount
Mint never wrote a minus sign: Amount is always a magnitude, and the direction sits in Transaction Type, where “debit” is money out and “credit” is money in. This preset reads that column, so purchases come out negative while refunds, paycheques and card payments come out positive — no sorting the file into two halves and no find-and-replace first. Two other archive habits are handled for you: dates are unpadded and month-first (8/1/2026, and older files use two-digit years), and long card descriptors sometimes wrap onto a second line inside their quotes, which the parser reads as one field rather than a broken row.
Beancount output
Mint export questions
Can I still export from Mint?
No. Intuit closed Mint on 23 March 2024 and transaction history was not carried over to Credit Karma, so the only Mint data anyone has is the CSV they downloaded before that date. If you pulled yours in batches to get past Mint's 10,000-row export cap, convert each file and paste the results one after another — the converter is stateless, and Beancount reads transactions by their date, not by the order you appended them in.
Should I map Description or Original Description?
Description is Mint's cleaned-up merchant name, and it is what the preset maps because it reads better in a ledger. Original Description is the raw string your bank sent — switch the Description select to it if you would rather keep the exact wording for matching against old statements later. Both columns are in every archive file; the converter uses one and leaves the other untouched.
What happens to my Mint categories, labels and notes?
Nothing is discarded — they stay in your source file — but the converter maps only date, description and amount, so every transaction balances against the single category account you name. Mint's taxonomy (Restaurants, General Merchandise, Transfers…) has no direct Beancount equivalent, so the usual approach is to convert first and then reassign accounts in your ledger one category at a time.
Keep the ledger you just converted
Beancount.io hosts your plain-text ledger, imports future statements for you, and keeps every number auditable.
Start Free→