“I need to move my Mint history into another app”
Moving years of categorised history between budgeting apps is not a single import; it is a migration where some things transfer intact and others cannot. Knowing which is which before you start saves rebuilding categories twice.
Symptoms
The export is one large CSV covering every account together Categories from the old app do not exist in the new one Split transactions arrive as single lines with the total only
What actually causes it
Export files combine all accounts
The download contains an account name column rather than one file per account. Importing it whole puts every account’s history into whichever account you selected, and separating them afterwards means editing thousands of rows.
Category names are app-specific
Categories are labels in the exporting app’s own scheme, not a standard. The new app either creates duplicates for every unfamiliar name or discards them, and neither outcome preserves the structure you had.
Splits and transfers flatten on export
A transaction divided across several categories exports as one row carrying the total, and a transfer between two accounts exports as two unlinked rows. The detail existed only inside the old app’s database.
How to fix it
- Split the export by account before importing, and import one account at a time into a matching destination account.
- Check each split file with the tool below: dividing a CSV by hand is where quoting and column alignment usually break.
- Build your category list in the new app first, then map on import rather than letting the importer create categories from the file.
- Accept that splits and transfer links will not survive, and reconstruct only the ones that matter for tax or reporting.
Related import problems
Skip the manual edit — fix it automatically
The checker verifies column alignment and quoting after you split a large export by hand, which is exactly where that operation goes wrong. Free, no signup, no upload.
Open the fixer