Moving from YNAB to CoPilot
Assembled from both records. Nothing here is an opinion — it is the difference between two rows, written out.
Your data — read this first
YNAB records transaction export as Yes, so take the export first. CoPilot records history import as No: your history does not move, and you start from whatever your banks return on connection.
- Transactions
- No
- Balance history
- ?
- Budgets
- Rebuilt by hand
- Rules
- Rebuilt by hand
- Attachments
- ?
Transactions, balance history and attachments are CoPilot’s own import attributes. Budgets and rules never transfer between two apps in this index.
What you gain
- Real estate No → Yes
What you lose
- Split transactions Yes → No
- History import Yes → No
What is unchanged
- Free tier, Account aggregation, Manual accounts, Edit transactions, Rules engine, Export, Budgeting, Rollover budgeting, Recurring transactions, Net worth, Reports, Partner or household, 2FA / MFA
37 attributes are Unknown on one side and left out. Gains and losses are a diff of the two records.
How to do it
- Export from YNAB first
Take the transaction export while your subscription is live. The record says export is available.
- Connect accounts
Find out which of your banks fail before you are billed. CoPilot reaches banks through Plaid, MX, Mastercard, Akoya. Banks named most often in CoPilot’s 450 most recent App Store reviews: Plaid (34), Apple Card (10), Fidelity (9), Venmo (7), Amex (6) — read what they say before you connect those first.
- Rebuild budgets and rules
No app in this index imports another’s budgets or rules. Budgets are quick; rules are worth rebuilding as transactions arrive rather than all at once.