Step 1
In Quicken Classic for Windows, choose File, File Export, QIF File. Select the account and date range, and include Transactions. Include account information when exporting more than one account. Export investment or business records separately; Clover's QIF migration supports Bank, Cash, CCard, Oth A and Oth L transaction sections.
Step 2
Use the .qif transaction file, not a Quicken backup or .qxf file. QFX is a different bank-exchange format. Category and class definition lists are not transactions, and memorized reminders are not imported as history.
Step 3
QIF has no reliable currency field. Export only accounts sharing one currency per file. Clover uses the selected account's currency or your default currency, so check that it matches the original export. For mixed-currency history, prepare the Clover CSV template with each row's original Currency instead.
Step 4
Keep every split's S, E and $ lines with its parent transaction. Clover checks the signed parts against the T total, then saves only the individual parts. Bracketed categories such as [Savings] stay transfers; each supplied leg is preserved without inventing another. Opening Balance and Starting Balance rows are skipped, so verify account balances separately.
Step 5
Use YYYY-MM-DD dates where possible. Clover accepts unambiguous day-first or month-first QIF dates and Quicken's apostrophe-year dates, but asks for clarification when the date order is ambiguous. Use decimal-point amounts with optional comma thousands separators. If the file lacks an account name, choose its Clover account before uploading.
Step 6
In Clover, select the Profile that should receive the history. Open Add Transaction, select Upload and choose your transaction file.
Step 7
Check the new transactions and account assignments before uploading another date range.
Common questions
What happens to split categories, classes and check numbers?
Category:Subcategory becomes a readable category path. Split memos are combined with the parent memo. A QIF class becomes a tag prefixed with QIF:. Original records, check numbers and cleared states remain in Clover's import evidence. Check numbers are not treated as unique IDs, so two legitimate transactions using the same number are retained. Reimporting the same source records preserves confirmed corrections.
Can I import investment trades, schedules or every QIF variant?
No. This supports non-investment transaction history, not a complete Quicken restore. Investment/business records, percentage-only splits, unsupported fields and malformed or incomplete splits reject the file before saving. Use a transaction CSV mapped into Clover's template for unsupported layouts. QIF exports from other apps must follow the same supported format; compatibility with every app version is not guaranteed.
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.
Quicken QIF export instructions ↗