Import broker CSV
Not every broker offers a clean API. Trade Republic history, an old Degiro export, a bank PEA without OpenAPI — many European investors still depend on CSV or Excel files. A good import is not “upload and hope”: it is mapping accounts, preserving cash flows, and avoiding duplicate rows when you later add a live sync. This guide walks through a CSV-first workflow in Wolfora.
When CSV is the right path
Use CSV for closed brokers, one-off history migration, PEE or employer plans with only annual statements, or any account where read-only API does not exist yet.
Prefer live sync (Saxo, IBKR Flex) when available — CSV is maintenance. Many users combine both: CSV for the pre-2020 era, API for today forward.
If you plan to connect IBKR later, import legacy neo-broker CSV into a clearly named account (e.g. “Trade Republic archive”) rather than merging unlike histories into one blob.
What to export from the broker
Request activity / transaction history, not just current positions. Performance math needs buys, sells, dividends, deposits and withdrawals — not a snapshot of holdings today.
Export the widest date range once for the initial load. Narrow incremental exports are fine later if your broker supports them; otherwise re-export annually and dedupe.
Keep original files. When Wolfora mapping improves, you may re-import from source rather than editing hundreds of rows by hand.
Mapping accounts in Wolfora
Create one Wolfora portfolio account per legal envelope you care about: PEA, CTO, PEE, crypto exchange. Labels should still make sense in two years.
Map CSV columns to Wolfora fields (date, side, ticker, quantity, price, fees, amount). Tickers may need manual normalization (.PA, .DE) so they match Yahoo quotes used for marks.
Cash dividends should import as DIVIDEND rows with amount, not as fake “buy” lines. Deposits and withdrawals must be separate from trades or TWR will lie.
Avoiding duplicates when adding sync later
If you CSV-import 2020–2024 and then connect IBKR Flex for 2024–today, overlap windows duplicate trades unless you trim one source. Pick a cut-over date: CSV ends the day before Flex starts.
Do not CSV-import the same period twice with slightly different formats. If you must re-import, delete or soft-reset the affected account range first (follow in-app guidance).
Saxo OAuth and IBKR Flex both dedupe by external IDs; manual CSV rows use different keys — plan the hand-off explicitly.
Quality checks after import
Compare open positions vs broker: quantity and ticker, allowing small FX differences on price.
Spot-check three dividend payments and one deposit against the broker PDF.
Open the performance chart only after cash flows look right. A perfect-looking allocation chart on broken cash history is worse than an empty chart that forces you to fix data.
CSV + Wolfora in a multi-broker setup
Typical French setup: PEA at bank (CSV), CTO at IBKR (Flex), old Trade Republic (CSV archive). Wolfora consolidates in the global view while keeping envelopes separate for tax thinking.
Read the multi-broker tracker guide for account structure, then Saxo or IBKR guides when you add sync on top of CSV baselines.
FAQ
Which brokers support CSV import in Wolfora?
Wolfora supports flexible CSV mapping for common export shapes. If a broker uses a unusual format, start with a small sample file and fix mapping before importing ten years of history.
Can I import only positions without history?
You can seed current holdings manually, but performance and dividend history will start from today. For long-term analytics, transaction history is strongly recommended.
Will CSV import overwrite my live Saxo sync?
No if accounts are separated. Keep Saxo on its linked account and CSV history on another named account, or use non-overlapping date ranges on the same account.
How often should I re-import CSV?
Only when the broker has no API and you trade rarely — quarterly or after large activity. If sync exists, use it instead of repeated CSV uploads.
Related guides
- Why a multi-broker wealth tracker
PEA, Saxo, IBKR, bank brokerage and crypto in one place: why a multi-broker wealth tracker beats Excel for TWR, allocation, dividends and real net worth.
- Connect Saxo Bank to Wolfora
Connect Saxo Bank to Wolfora via OpenAPI: OAuth setup, what syncs (transactions, positions, TWR/NAV), PEA vs brokerage accounts, and read-only best practices.
- IBKR Flex Query and Wolfora
IBKR Flex Web Service with Wolfora: create token and Flex Query, sync cash and trades, optional live marks, and how to combine IBKR with PEA or Saxo accounts.
- Track portfolio dividends
How to track dividends received, upcoming payments and yield across PEA, CTO, Saxo and IBKR — without spreadsheets that break every tax season.