Skip to main content

Switch from Mint, YNAB, Monarch or Copilot

Bring your history across with a guided CSV import that already knows each app's export format — including which way its amounts point.

Updated Jul 30, 2026

On this page

Every app on this list can export a CSV, and Fyncora has a guided path for each one. The important part isn't reading the file — it's reading it correctly, because these apps disagree about something fundamental.

Why the source app matters

There's no shared standard for "an amount" in a finance export:

  • Monarch writes a signed amount: -42.50 is money out.
  • Mint writes an unsigned amount plus a separate Transaction Type column saying debit or credit.
  • YNAB writes two columns — Outflow and Inflow — and fills in one of them.

Read a Mint file with Monarch's rules and every expense arrives as income. Fyncora ships a preset per source app so the signs come out right the first time.

Import your history

  1. Export a CSV from your old app (its own docs will say where; look for "export" in settings or the transactions screen).
  2. In Fyncora, open Transactions and select Switch from another app.
  3. Pick the app you're coming from.
  4. Follow the export guide shown for that app, then upload your file.
  5. Map each CSV account to a Fyncora account, creating any that don't exist yet.
  6. Review the preview, then commit the import.

You'll see the transactions appear in Transactions, and the import listed as a batch you can undo in one action if anything looks wrong.

Tip:

Tip: import one account first and check a handful of rows — especially that expenses are negative and income is positive. Then do the rest with confidence.

Warning:

Warning: Mint, Copilot, Monarch and YNAB are verified presets. Rocket Money, Empower and PocketGuard are marked beta: the mapping is our best reading of their format, so check the column mapping screen before committing.

What comes across, and what doesn't

Comes across: dated transactions with amounts, descriptions/merchants, and categories where the export includes them (category names are matched to yours, and anything unmatched lands uncategorized for you to fix in bulk).

Doesn't come across: budgets, goals, account history/balances over time, attachments, and rules. Those are quick to set up fresh, and they'd be wrong if we guessed them.

Note:

Note: imports are capped at 5,000 rows per file. If you have more history than that, split the CSV by year — the duplicate check means overlapping ranges are safe.

Duplicates are handled

Fyncora fingerprints each row (date, amount, description, account) and skips ones it already has, so re-importing an overlapping file doesn't double your history. The summary at the end tells you how many rows were added, skipped as duplicates, and rejected as invalid.

Undo an import

  1. Open Transactions and find the import batch.
  2. Select Delete batch.

Everything that import created is removed in one step. This is the safety net that makes trying a preset low-risk.

FAQ

Do I need my old app's password? No. Fyncora never asks for another service's credentials — you export a file, you upload it, you stay in control of what enters.

Can I import from a bank instead? Yes — the same wizard handles a plain bank CSV; you map the columns yourself. See Import your bank's CSV.

My categories didn't match. That's normal between apps. Use the category-mapping step, and fix the rest in bulk afterwards from Transactions.

Was this helpful?

Still need help? Open a ticket.