CSV trade import
for your Obsidian trading journal

Import broker CSV exports into Journalit, check the mapping, then review every trade inside your own Obsidian vault.

Trade import overview inside Journalit

Supported broker exports

Start with the file your broker actually exports. If your broker is listed here, use the guide before guessing at columns or report names.

Not listed?

Ask in Discord and tell us which broker you want added. We use requests to prioritise new export guides and adapters.

Broker or platformExport to useFormatJournalit pathGuide
Interactive BrokersFlex Query Orders exportCSVCSV ImportExport guide
TradovateReports → Orders exportCSVCSV ImportExport guide
TopstepXTrades module exportCSVCSV ImportExport guide
TradeZeroTrade history exportCSVCSV ImportExport guide
TradingViewPaper Trading Order History exportCSVCSV ImportExport guide
FX ReplayAnalytics exportCSVCSV ImportExport guide
BybitTrade History exportCSVCSV ImportExport guide
HyperliquidTrade History exportCSVCSV ImportExport guide
BlofinOrder Centre futures trade history exportCSVCSV ImportExport guide
Sierra ChartTrade Activity Log → Save Log AsText/CSV-style exportCSV ImportExport guide
MotiveWaveAccount → Executions exportCSVCSV ImportExport guide
ATASTrading Journal workbook exportXLSXCSV ImportExport guide
Trading TechnologiesFills widget downloadCSVCSV ImportExport guide
RithmicR | Trader Pro Order HistoryCSVCSV ImportExport guide
MetaTrader 4/5Account History → Save as ReportHTMLBroker adapterExport guide

How trade import works

The path is intentionally conservative: export the source data, validate the mapping, then let Journalit turn the imported trades into normal journal records on your own device.

  1. 1

    Export your trade history

    Start with a broker export, CSV file, or spreadsheet-style journal rather than screenshots or copy-pasted tables.
  2. 2

    Map the data correctly

    Use a broker guide, a built-in adapter, or manual mapping. In the plugin, this happens inside the CSV Import page. AI-assisted mapping can help interpret unclear columns.
  3. 3

    Review the import inside your trading journal

    Once imported, trades appear in your Trade Log and dashboards for normal journalling, filtering, and review.

What if your broker is not listed?

A supported guide is best, but you do not need a dedicated adapter for every file. Manual mapping exists for CSV, Excel, and table-style exports that use clear trade-history fields.

Start small

Import a week or month first so bad columns are easy to catch before a full migration.

Map the real fields

Use symbol, side, date, price, quantity, fees, and P&L fields rather than summary rows.

Validate before bulk import

Compare trade count, symbols, fees, and P&L against the source export before trusting the history.

Import paths Journalit supports

Most traders start with broker CSV export. These are the other paths when your history lives somewhere else.

Validate the import before trusting the history

A trade import is only useful if the imported records match the source file. Treat the first import as a verification step, not a bulk migration.

Start with a small date range

Import a week or month first so errors are easy to spot before you bring in years of trades.

Compare totals against the source

Check trade count, symbols, dates, side, quantity, fees, and P&L against the broker export.

Keep the original export

Do not overwrite the raw broker file. If a mapping needs to be fixed, the original file is your reliable source.

Validate a small sample first

Import a week or month, then compare trade count, symbols, dates, fees, and P&L against the broker export before trusting a full migrated history.

Generic trading journal CSV template

If your broker is not listed, start from a simple CSV shape and map the columns manually. Keep the first import small, then validate the Trade Log before importing years of history.

symbol,side,entry_time,exit_time,entry_price,exit_price,quantity,fees,pnl,setup,notes
ES,long,2026-04-29 09:35,2026-04-29 10:12,5241.25,5248.75,1,4.50,375,ORB,"Good execution"

Use clean field names

Clear column names make manual mapping and AI-assisted mapping easier to verify. Use explicit fields such as symbol, side, entry time, exit time, prices, quantity, fees, and P&L.

Clean messy exports first

If your broker file includes balances, repeated headers, or summary rows, remove that report noise before bulk import.

What trade import looks like

The import interface is designed to make messy broker and spreadsheet data legible before it touches your trading journal. Manual mapping is the main screen; AI mapping appears as a smaller assistive step rather than a full-screen workflow.

Manual trade import column mapping in Journalit
AI-assisted trade import mapping in Journalit

Privacy note

AI-assisted mapping only uses headers and a small sample of rows to infer column meaning.

Operational reality

A clean broker export usually imports quickly. Messy or non-standard files may still need manual verification before you trust the final mapping.

Common concerns before importing

Free vs Pro

Journalit is free for journalling, analytics, reviews, and templates. Pro unlocks automated imports only.

Free

$0forever

Everything you need to journal and improve.

Includes

  • Unlimited trades and accounts
  • Trade Log and analytics dashboard
  • Built-in templates for trade notes and reviews
  • Custom fields, tags, setups, and mistakes
  • Works offline with your vault as the source of truth

Pro

$15/month

Billed yearly ($180 once per year) or $18/month billed monthly.

For traders who want automated imports instead of manual logging.

Everything in Free, plus

  • CSV imports for any broker
  • Automated MetaTrader 4/5 sync
  • AI-assisted mapping for messy exports
  • Duplicate detection and multi-account support