Leaving Excel or Money Manager Ex without losing your history
How to migrate years of transactions from a spreadsheet or an .mmb file to a cloud app: what carries over, what does not, and how to prove the totals still match.
If you have been recording your spending for years, you have a problem that someone starting fresh does not: your history. Eight years of transactions are not an old archive. They are what makes your reports mean anything — without them you cannot compare this year to last, or know whether your grocery spending is really rising, or work out whether the car was a mistake.
That is why so many people are still running Money Manager Ex on a 2016 laptop, or a spreadsheet only they understand. It is not sentiment: it is that switching looks like starting from zero.
It does not have to be. But it has to be done in order.
Before touching anything: two copies
Obvious, and the step everyone skips.
- Money Manager Ex: copy the
.mmbfile somewhere else. A different folder and a different drive or cloud storage. It is a SQLite database; if it corrupts mid-export, it corrupts entirely. - Excel: save a copy with the date in the filename.
finances-2026-09-15.xlsx.
These copies are never touched again. Everything below happens on another copy.
What migrates and what does not
Nobody tells you this up front, and it is what decides whether the migration goes well. With a native
.mmb importer — Praxelle's, which is the one I can speak about with actual data — here is what
happens:
| What | Migrates? | Detail |
|---|---|---|
| Accounts | Yes | Name, type and opening balance. MMEX types are mapped: Checking → bank, Credit Card → card, Term → savings |
| Transactions | Yes | Date, amount, payee, category and notes |
| Categories and subcategories | Yes | The parent → child hierarchy is rebuilt |
| Payees | Yes | By name; the history then allows category suggestions |
| Transfers between accounts | Partial | They arrive as movements with their sign, not as linked transfers. Review them |
| Splits (one transaction across several categories) | No | They arrive under the primary category |
| Per-account currency | Partial | Each account is created in the currency the .mmb carries, provided rates exist for it (USD, EUR, CAD, GBP, CHF, JPY, AUD, MXN, BRL). Anything else, and accounts with no currency in the file, are created in the base currency, and the preview says so |
| MMEX attachments and budgets | No | Rebuild them |
That bold row is the one that changes the result most. If your .mmb mixes currencies, each account
keeps its own and no amount gets relabelled: consolidated net worth is computed by converting each
movement at the rate for its own date, not today's.
With one caveat worth checking before you migrate, and I would rather say it myself: today there are historical rates for USD, EUR, CAD, GBP, CHF, JPY, AUD, MXN and BRL. An account in any other currency — COP, ARS, CLP, PEN, UYU, VES — is imported in the base currency, because without rates we could not convert it and the totals would be invented. The preview tells you, account by account, which currency each one will end up in and flags the ones that fall back, before you confirm anything.
Migrating from Money Manager Ex
1. Update MMEX and check the file
Open your file in the latest version and run File → Database → Check integrity. A file with errors gives you an import with errors.
2. Tidy up before you move
This is half the work, and the only part no tool can do for you:
- Merge duplicate categories. "Groceries", "Supermarket" and "Weekly shop" are the same thing. Whatever you do not unify now, you carry forever.
- Archive closed accounts. That account you closed in 2019 is still in there. Mark it closed in MMEX before exporting.
- Fix blank payees. A hundred transactions with an empty payee are a hundred transactions you can never filter.
3. Import
Upload the .mmb. Before anything is written, you get a preview: how many accounts, how many
transactions, how many duplicates detected. Read it. If the transaction count does not resemble what
you had, stop and find out why.
4. Reconcile the totals
This is the step that separates a migration from a silent disaster. In MMEX, look at each account's balance as of today. In the new app, look at the same balance.
They have to match to the cent. If they do not, the causes in order of frequency are: an account that did not import, a split counted under its primary category, or a transfer counted twice.
5. Keep MMEX read-only for a week
Do not delete it. Run it in parallel for seven days: if something does not add up, the answer is in there.
Migrating from Excel
There is no standard file here, so the work is about shape.
1. One sheet, one table, no decoration
Most personal finance spreadsheets have three tables, two charts and a totals row in the middle. Make a copy and reduce it to a single flat table: one row per transaction, one header row at the top.
Remove: totals rows, subtotals, merged cells, blank separator rows and margin notes.
2. The minimum columns
| Column | Format | Required |
|---|---|---|
| Date | YYYY-MM-DD | Yes |
| Amount | Number, negative for expenses | Yes |
| Description | Text | Yes |
| Category | Text | Recommended |
| Payee | Text | Recommended |
| Account | Text | If you have more than one |
| Notes | Text | No |
Two details break more imports than anything else:
- Dates stored as text. If Excel holds "03/05/2024", nobody can tell whether that is 3 May or 5
March. Convert everything to
YYYY-MM-DD. - Amounts with thousands separators. "1,234.56" is text, not a number. Strip thousands separators and use a single decimal separator.
3. Income and expenses in one column
If you have two columns, "Income" and "Expense", merge them into one: expenses negative, income positive. That is what every importer expects.
4. Export as CSV in UTF-8
Save as → CSV UTF-8. Without UTF-8, every accent and special character arrives broken, and fixing a thousand descriptions by hand is not a plan.
5. Import in chunks if it is many years
If you have ten years, import one single year first. Check that categories mapped the way you expected and that the totals reconcile. Fix the mapping, then import the rest.
How to know the migration worked
Four checks, fifteen minutes:
- Current balance of each account, matching the old system to the cent.
- Total transaction count, with the difference explained (discarded duplicates, archived accounts you did not import).
- Total spending for any month last year, identical in both systems.
- Categories: no "Uncategorised" that was not already there in the original.
If all four pass, you are done. You can archive the old system.
One question to ask before choosing where you go
You are migrating because a tool fell behind, or shut down. Mint closed in 2024 and left millions of people exactly where you are now.
So before putting eight years of history somewhere else, check how you get out:
- Can you export everything as CSV, without paying?
- Does the export include categories and payees, or only amounts and dates?
- Can you export on the free plan, or do you have to subscribe in order to leave?
If the answer to the last one is "you have to pay to export", you already know how this ends the day you want to leave.
Disclosure: I am the founder of Praxelle, which imports Money Manager Ex
.mmb files, CSVs and Excel templates, always with a preview and duplicate detection. Each
account's currency is read from the file itself; that was not true until recently, and this article
used to say so. Exporting everything as CSV is included in the free plan, precisely because of the
last section.