Pick your path
Coming from YNAB
Brings accounts, categories, transactions, and your monthly assignments into
a new budget.
Coming from Monarch
Two CSV files become a new budget with accounts, categories, and
transactions.
Coming from Actual
Reads your Actual export and builds a new budget from it.
A CSV from your bank
Map columns and add transactions to an account you choose.
An OFX or QFX file
A structured bank or Quicken file — no column mapping needed.
Link the bank instead
Skip files entirely and let transactions sync on their own.
Decision guide
| You have | Use | What you get |
|---|---|---|
| A full YNAB budget | YNAB | New budget: accounts, categories, transactions, assignments |
| A Monarch account | Monarch | New budget: accounts, categories, transactions |
| An Actual Budget file | Actual | New budget: accounts, categories, transactions, assignments |
| A bank CSV download | CSV | Transactions added to one account |
A .ofx or .qfx file | OFX/QFX | Transactions added to one account |
| A bank that Plaid covers | Bank link | Transactions sync automatically |
How the two kinds differ
Whole-budget migrations (YNAB, Monarch, Actual) build a complete new budget so you can switch to Budget Bandit without losing structure. Because they always create a new budget, you can run them safely even if you have been experimenting already — nothing you have built is touched. Transaction imports (CSV, OFX/QFX) add rows to a single account you pick. They run duplicate detection so re-importing an overlapping file does not double your history. Use these to top up an account that is not on a bank feed.After any import
Imported transactions arrive in your To Review queue. Confirm and categorize them, and any rules you have set apply automatically to matching rows.If rows do not come through
See Why rows did not import for skipped dates, bad amounts, and duplicate handling.Related
CSV format reference
Exactly which columns and formats are expected.
Connect a bank
The no-file alternative.