Moving from Mint to YNAB
Assembled from both records. Nothing here is an opinion — it is the difference between two rows, written out.
Your data — read this first
Mint has been discontinued. If you exported your transactions while you could, YNAB imports transaction history, so what you exported comes with you.
- Transactions
- Yes
- Balance history
- Yes
- Budgets
- Rebuilt by hand
- Rules
- Rebuilt by hand
- Attachments
- ?
Transactions, balance history and attachments are YNAB’s own import attributes. Budgets and rules never transfer between two apps in this index.
What you gain
- Balance history import No → Yes
What you lose
- Free tier Yes → No
What is unchanged
- Account aggregation, Manual accounts, Edit transactions, Create manual transactions, Rules engine, Mass edit, Split transactions, Export, Budgeting, Rollover budgeting, Recurring transactions, Goal tracking, Net worth, Reports, Trends, 2FA / MFA
46 attributes are Unknown on one side and left out. Gains and losses are a diff of the two records.
How to do it
- Find your Mint export
The product is gone, so the file you already have is the only history that moves. Without one, skip to step 3 and accept a shorter history.
- Get the file into a format YNAB reads
Its record lists CSV · QFX · QIF. If your export is something else, a spreadsheet can usually re-save it as CSV.
- Import before you connect anything
Import the file first. Connecting banks first creates duplicates that then have to be merged one by one.
- Connect accounts inside the trial
Find out which of your banks fail before you are billed. YNAB reaches banks through Plaid, MX, TrueLayer.
- Rebuild budgets and rules
No app in this index imports another’s budgets or rules. Budgets are quick; rules are worth rebuilding as transactions arrive rather than all at once.