Switching From Mint, YNAB, or Quicken Without Losing a Decade of Transactions
Published

By Ian, founder of ThriftyOwl.money
If you are reading this, you have probably already made the decision. The subscription went up once too often, or the app you used was switched off, or the method that was supposed to simplify your money has turned into a weekly chore. What is stopping you is not the new app. It is the years of records in the old one.
That worry is reasonable. A budgeting app is, among other things, a diary of your finances: every grocery shop, every salary, every year's tax bill. Losing it would hurt, and some apps make leaving harder than it should be. This guide covers the practical side. It explains how to get your history out of Mint, YNAB and Quicken, what makes the journey safe, and how to confirm that every transaction arrived before you close anything down.
The one rule: export first, cancel last
Before anything else, get a copy of your data out while your old account still works. Everything below follows from that.
- Do not cancel your old subscription until your history is in the new app and you have checked it. Most services keep your data for a short time after you leave, and some delete it quickly.
- Keep the exported files. They take up almost no space. They are your insurance policy, and they are also your proof if you ever need to answer the question "what did I pay for that in 2016?"
- Export everything, not just this year. It is far easier to delete history you don't want than to recover history you didn't export.
If you are leaving Mint
Mint is the awkward case, because it is gone. Intuit closed it in 2024 and pointed people to Credit Karma. Most sources give March 23, 2024 as the end of the window for downloading a transaction CSV, and accounts and histories were reported to be removed after that, so a live export is no longer possible.
Whether you can still rescue your history depends on one thing: did you ever download a file?
- If you saved a CSV (or a zip of CSVs) in 2023 or 2024, you can still use it. Look in your Downloads folder, your email attachments, a cloud drive, and any old backups. A Mint export is an ordinary CSV with one row per transaction, so it can be imported like any other.
- If you used a Mint export extension or converted your data to another tool, the output of that is probably a CSV too.
- If you have nothing, the data is very likely gone. Intuit's data request process was described in 2024 as another route, but I could not confirm that it still works, so treat it as a long shot.
Mint's export had its limits. Third parties reported a cap of around 10,000 transactions on a single download and a three-year limit on history. If your file seems short, that may be why, and it is worth knowing before you assume the import lost anything.
To bring a Mint CSV into ThriftyOwl.money, use Import CSV (see below). Mint's columns, including date, description, amount, category and account name, are the kind that the importer recognises. One thing to watch for is that Mint listed spending as positive amounts with a separate "transaction type" column. If your spending arrives as income, tick the flip the sign option on the column-check step and the preview will show it corrected.
If you are leaving YNAB
YNAB is the easiest of the three, because it still lets you take everything with you, and the export is generous.
In the web app (the mobile app doesn't offer this), click your budget name in the top left and choose Export (the exact wording has changed over the years, so look for "Export Budget" or "Export Plan"). YNAB gives you a zip file containing two CSVs:
- The register file holds your transactions. This is the one you want. It lists every transaction, with its account, date, payee, category, memo, the amount going out or in, and whether it was cleared.
- The budget (or plan) file holds your category allocations month by month. It is useful as a record of how you budgeted, but it is not transaction history, and you will rebuild budgets in the new app rather than import them.
Open the register file and look at it before you import it. Two things are worth noting:
- It covers all your accounts in one file, with an Account column. ThriftyOwl.money's CSV import reads that column and turns each different account name into its own account, so you do not have to split the file by hand.
- YNAB's amounts are split into Outflow and Inflow columns. The importer recognises those names, and treats them as money out and money in.
Transfers deserve a mention. YNAB records a transfer between your own accounts as a pair of transactions, one in each account. Because the register file holds all your accounts, ThriftyOwl.money sees both sides during the import and tries to match them up and link them as a single transfer. Any side it can't match, for example because the other account wasn't imported, still comes in as an ordinary transaction, so your balances and history are complete either way.
If you are leaving Quicken
Quicken has two things going for it: it has been around long enough that nearly everything can read its files, and it has always been able to export to QIF. It also has one big drawback, which is that an export is something you must do yourself, and a Quicken data file is not a format other programs can open.
In Quicken for Windows, QIF export is under File → File Export → QIF file. You choose an account and a date range, and Quicken writes a file. A few things to know:
- Check whether you can export all accounts at once. Reports differ between versions and between users. Where it is a single account at a time, export each account separately, and name the files after the accounts.
- Quicken calls QIF a legacy format. It recommends its own newer format for moving data between Quicken files, but QIF is the one that other software understands.
- Investment accounts are the weak point. Securities, lots and prices do not travel well in QIF. If most of your history is in checking, savings and credit card accounts, QIF works well. If you rely on detailed investment tracking, check that part of the result carefully, and keep the original Quicken file.
- If QIF is not an option, use Quicken's report export to produce a CSV of the transactions you want, with a column for the account.
QIF carries categories, memos, cheque numbers, split transactions and cleared status, so it is the richest option. If you are moving from Quicken, the steps in How to Export Your Microsoft Money File and Actually Keep Your History apply almost exactly: one QIF file per account, collected into one archive and imported together. For a plain-language look at how QIF compares with CSV, see QIF vs OFX vs CSV.
What you do when you've got the files
The importer accepts the three kinds of file you are now likely to hold:
| You have | Use |
|---|---|
| A Mint or YNAB CSV, or any bank or spreadsheet CSV | Import CSV |
| A multi-sheet Excel workbook | Import Excel (each worksheet can become its own account) |
| QIF files from Quicken or Microsoft Money | Import Microsoft Money |
For a CSV, upload the file (or a zip of several files that share exactly the same columns). Before anything is saved, ThriftyOwl.money shows what it detected.

The Check your columns step is the part that protects you. It shows which column it believes is the date, the payee, the amount and the category, the date format it chose, and a preview of your first rows.

If something is wrong, you fix it here, before any of your data is imported. The two common problems are the date format (is 03/04/2024 the third of April or the fourth of March?) and the sign of the amounts. Look at one transaction you remember, such as a rent payment or a salary, and check that the date and direction in the preview match what you know to be true.
You then choose which accounts to bring across and what type each one is. Rows without a readable date or amount are skipped, and the free plan has a limit on how many accounts you can import, so start with the accounts that matter most.
How to check that nothing went missing
This is the step that turns "I think it worked" into "I know it worked". It takes about fifteen minutes and is worth doing before you cancel anything.
- Count. Compare the number of transactions in each account against your old app, or against the row count of your export file.
- Compare balances. Choose a date and compare each account's balance in the new app against the balance your old app showed on that date. If the totals match, every transaction almost certainly arrived.
- Check the ends. Look at the oldest and the newest transaction in each account. Missing history usually goes missing from one end or the other.
- Spot-check the awkward ones. Look at a split transaction, a transfer between accounts, and anything with unusual characters in the payee name.
- Look at the categories. Years of categories tend to include duplicates and old names. Tidy them now, while you remember what they meant.
- Look at one year you know well. Compare your total spending on a single category, such as groceries, with a report from the old app.
If a total doesn't match, the usual causes are an account that wasn't in the export, an export that hit a row limit, or a sign or date problem in the mapping. All of those can be fixed by importing again with a corrected setting. Because you kept the original files, you lose nothing by trying again.
What does not come with you
It is better to know now than to find out later.
- Budgets. Exports hold transactions, not your budgeting setup. Rebuild your categories and limits, and use your imported history to see what you really spend.
- Recurring bills and scheduled payments. Set these up again. It is a good excuse to remove the ones you no longer pay.
- Some transfer links. The import matches the two sides of a transfer where it has the transactions for both accounts. If you import only one account, or the two sides don't line up, the transfer arrives as an ordinary transaction, and you can tidy it afterwards.
- Reconciliation history. QIF carries cleared status from Quicken, but a plain CSV usually does not.
- Attachments, receipts and notes held only inside the old app. Download any you want to keep before you leave.
A sensible order of work
If you want a plan to follow, this is the one I'd use:
- Export everything from your old app today, while it still works.
- Put the files in a folder, and make a second copy somewhere else.
- Import one small account first as a test, and look at the result.
- Import the rest.
- Run through the checks above.
- Rebuild budgets and bills.
- Run both apps side by side for a month if you can, then cancel the old one.
The bottom line
Moving apps loses your history only when people leave before they've exported, or when they skip the checking afterwards. With the files in hand and a preview before anything is saved, a decade of transactions is entirely portable. The old app can be switched off, repriced or retired, and your records will still be yours.
If you're ready to move, ThriftyOwl.money imports CSV, Excel and QIF files, and shows you what it found before it saves anything. If you're still weighing up where to go, YNAB alternatives for people who just want a budget and Mint is gone: where its users went next cover the choices.
About the author: Ian is the founder of ThriftyOwl.money and writes its white papers on the personal finance software industry.
Sources: YNAB Support, "How to Export Plan Data"; Tiller, "How to Easily Export YNAB Transactions to a Spreadsheet"; PocketSmith, "Importing accounts and transactions from YNAB"; Quicken, "Export data from Quicken"; Intuit Community, "Mint shutting down in less than two months"; Infinite Kind, "Importing From Microsoft Money".