Step 1
In Monarch on the web, open Settings, Data and Download Transactions. For one account, open Accounts, select the account, then Edit and Download transactions. Choose transaction history, not balance history.
Step 2
Clover recognizes Date, Merchant, Category, Account, Original Statement, Notes, Amount and Tags. Keep negative expenses and positive inflows. If Currency is absent, add the original currency code to every row or select a matching Clover account; do not assume that every dollar amount is USD.
Step 3
Keep ISO dates (YYYY-MM-DD). For ambiguous dates, add Date Format with DMY or MDY. Standard Transfer and Credit Card Payment categories stay transfers. For custom transfer categories, add Type with Transfer In or Transfer Out, matching the amount sign. Use the Clover template if your export has a different layout.
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
Will hidden transactions and custom transfer categories be detected?
Only information present in the file can be preserved. A Hidden or Excluded column with true/false retains exclusion from totals. If your export omits that field, add it before importing. Custom transfer categories need an explicit Type column or Category Group set to Transfers. Positive refunds keep their incoming direction and source category. Account balance history and attachments are separate from transaction history.
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.
Monarch download instructions ↗