Step 1
Open a transaction list in Bluecoins and export Excel (.csv). Use a transaction-level export rather than a budget or balance-sheet summary.
Step 2
Clover recognizes the published standard/advanced CSV template column profile: Type, Date, Item or Payee, Amount, Parent Category, Category, Account Type, Account, Notes, Label, Status and Split. The advanced profile also contains Currency and Conversion Rate. If your report export differs, map it into Clover's template.
Step 3
Keep both signed legs of each transfer and every split component. Include original currencies. Clover keeps split components as separate transactions, retains labels as tags, and skips void entries.
Step 4
In Clover, select the Profile that should receive the history. Open Add Transaction, select Upload and choose your transaction file.
Step 5
Check the new transactions and account assignments before uploading another date range.
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.
Sources and verification
Institution menus and availability can change. Check the official instructions if your app looks different. Clover is independent of these institutions.
Bluecoins export and CSV guide ↗