Switching
Bring your budget with you.
If you already keep a budget in YNAB, nYNAB or Actual Budget, beatrax imports it rather than making you start from an empty ledger.
What comes across
| From | What imports |
|---|---|
| YNAB 4 | Register and budget CSV exports — categories, budget history, transactions, splits, payees, accounts and transfers. |
| nYNAB (the web version) | The same CSV pair, with its own column shape recognised separately. |
| Actual Budget | The exported budget file read directly, including cleared status, splits, schedules and goals where present. |
How the import behaves
- Nothing lands until you approve it — The import stages everything first and shows a summary. You promote it into your ledger, or you don't.
- Re-running changes nothing — Import the same export twice and the second run is a no-op — every row is fingerprinted.
- It tells you what it couldn't map — Anything without a home in beatrax's model is listed as an unmapped-items summary rather than dropped silently.
- Merging is three-way — If you import into a ledger that already has data, conflicting records are reconciled rather than duplicated.
What doesn't come across
Payees become counterparties and budget categories become envelopes, which is close but not identical — some structures have no equivalent because the models genuinely differ. The unmapped-items summary at the end of the run tells you exactly what fell into that gap, so nothing disappears quietly.
Coming from a bank app or a spreadsheet
There is no importer for those, because there is nothing standard to import. Start instead with a statement export — most banks will give you the last year or more in one file, and beatrax will reconstruct your history from it, detect the recurring charges, and resolve the counterparties as it goes.