Step 1
In the Spendee mobile app, open More, then Export. Select the accounts and date range, then choose CSV or XLS. Spendee currently does not offer export on the web. Its Free plan can export the last 365 days; Plus and Premium remove that date restriction.
Step 2
Download Clover's migration template below and remove every example row. Copy the exported dates, account names, descriptions, categories and notes into the matching columns. Keep Migration Source set to spreadsheet. Spendee export layouts are not automatically identified as a dedicated source profile, so use this mapping step even for CSV.
Step 3
Use YYYY-MM-DD dates. Set Type to Income, Expense, Transfer In or Transfer Out. Use each account's original Currency and original transaction Amount, not a converted summary. Keep both transfer legs, with their own accounts, amounts and currencies. Do not import opening balances or totals as income.
Step 4
Separate labels with semicolons in Tags. Keep any stable transaction identifier in Transaction ID, if present. Save CSV, TSV or a compatible spreadsheet. Start with a short date range and compare the result before moving the rest of your history.
Step 5
In Clover, select the Profile that should receive the history. Open Add Transaction, select Upload and choose your transaction file.
Step 6
Check the new transactions and account assignments before uploading another date range.
Common questions
Is this an automatic Spendee converter?
No. This guide uses Clover's validated spreadsheet template. Clover does not claim to recognize every Spendee export version or language automatically. You must map the original amounts, currencies and transaction directions first. Photos, budgets and app settings do not move with this transaction file.
What moves into Clover?
Recognized transaction tables preserve dates, amounts, original currencies, account names, notes, categories and available labels. Category groups become a readable path such as Food / Lunch. Split components remain separate rows. Budgets, recurring schedules, attachments, goals, opening balances and the other app's settings do not automatically migrate with a transaction export.
What if Clover cannot recognize my export?
Export layouts vary by app version and language. Copy the transaction data into Clover's migration template, retaining its headings. Use YYYY-MM-DD dates and an explicit Income, Expense, Transfer In or Transfer Out type. Include each account's original Currency, such as PHP or IDR. Do not substitute a converted home-currency amount for the original amount. Remove all example rows before uploading.
Can I upload overlapping history?
Clover checks repeat imports against previously imported rows in the same Profile and account. Stable transaction IDs are preferred; without IDs, identical occurrences are compared. Edits made inside Clover do not change the saved source identity when the original export evidence is available. Renamed or reassigned accounts, changes to the source export itself, and different export layouts can prevent a match. Start with a short date range and inspect it before importing the rest. Matches do not overwrite confirmed transactions. Connected-bank matches use the existing bank overlap checks, which may require review when evidence is ambiguous.
How do I check the result?
Compare the transaction count and income, expense and transfer totals for the same accounts, currencies and dates in both apps. Pending, void and summary rows are skipped. Excluded entries stay excluded when the export supplies that flag. A transaction export may omit starting balances, so matching transaction totals does not guarantee matching account balances. Keep the original export until you have checked the result.
Sources and verification
Institution menus and availability can change. Check the official instructions if your app looks different. Clover is independent of these institutions.
Spendee export instructions ↗