Moving from WalletHub to Emma
Assembled from both records. Nothing here is an opinion — it is the difference between two rows, written out.
Your data — read this first
Whether WalletHub can export your transactions is unrecorded. Emma imports transaction history, so what you exported comes with you.
- Transactions
- Yes
- Balance history
- ?
- Budgets
- Rebuilt by hand
- Rules
- Rebuilt by hand
- Attachments
- ?
Transactions, balance history and attachments are Emma’s own import attributes. Budgets and rules never transfer between two apps in this index.
What you gain
- Nothing recorded
What you lose
- Nothing recorded
What is unchanged
- Free tier, Account aggregation, History import, Budgeting, Recurring transactions, Bills, Goal tracking, Subscription tracking, Net worth, Investment tracking, Reports, Trends, Credit scores, Alerts, Partner or household, Full mobile app, Customizable dashboard
47 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 WalletHub first
Take the transaction export while your subscription is live. The record is unknown on export, so check before you cancel.
- Get the file into a format Emma reads
Its record lists CSV. If your export is something else, a spreadsheet can usually re-save it as CSV.
- Import before you connect anything
Import the file first. Connecting banks first creates duplicates that then have to be merged one by one.
- Connect accounts
Find out which of your banks fail before you are billed. Emma reaches banks through TrueLayer. Banks named most often in Emma’s 56 most recent App Store reviews: Chase (7) — 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.