Step 1
Download the template below. Keep its header row and remove all four example transactions.
Step 2
Keep Migration Source set to spreadsheet. Fill Date in YYYY-MM-DD, Description, Amount, Currency, Account and Type. Use Income, Expense, Transfer In or Transfer Out. Record both transfer legs with each account's own amount and currency.
Step 3
Category and Subcategory preserve your category path. Separate Tags with semicolons. Excluded accepts true or false. Use a stable Transaction ID if the original export has one; do not invent new IDs each time you export.
Step 4
Save as CSV, TSV, XLSX, XLS or ODS and upload from Add Transaction in the correct Clover Profile. If Clover reports a row error, correct that row and retry. No transactions from an invalid recognized table are added.
Common questions
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.