Does trade import only work with CSV files?

No. CSV is common, but the workflow also covers spreadsheet-style journals and other broker export formats that can be mapped safely.

Does trade import work with any broker?

It works best with supported broker guides and common export formats. For everything else, manual mapping exists as the fallback path.

What if my file is messy or inconsistent?

That is exactly where manual mapping and AI-assisted mapping help. You still need to sanity-check the first import instead of assuming the source file is perfect.

Should I import years of history in one shot?

Not blindly. For messy exports or unfamiliar brokers, start with a smaller sample range, validate the result, then import the larger history.

Import trades into a private trading journal

Bring in broker exports and CSV trade history, validate the data, then turn each trade into a reviewable journal record inside Obsidian.

In the plugin UI this workflow still lives under the CSV Import page. Analytics, dashboards, review templates, and unlimited trades stay in the free plan. Pro exists for automation: trade import and MetaTrader sync.

Install free Start Pro trial How it works

How it works/Import types/Supported brokers/Validation/CSV template/Screenshots/FAQ/Pricing

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
Export your trade history
Start with a broker export, CSV file, or spreadsheet-style journal rather than screenshots or copy-pasted tables.
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
Review the import inside your trading journal
Once imported, trades appear in your Trade Log and dashboards for normal journalling, filtering, and review.

What kinds of trade imports Journalit supports

CSV is still the most common path, but the workflow is broader than a single file format.

Broker CSV imports

Import broker and platform CSV exports with built-in guides, adapters, or manual mapping.

Spreadsheet and Excel-style journals

Bring in older spreadsheet-based trade logs without rebuilding the history by hand.

MetaTrader sync

If you prefer ongoing automation instead of repeated file imports, use the MT4/MT5 sync workflow.

Import docs

Read the full import workflow and product behaviour.

Broker export guides

Follow export instructions for supported brokers before importing.

Bybit, Hyperliquid, and IBKR guides

Start with the most common crypto and multi-asset export paths users search for first.

Free trading journal

See what you can do before paying for any automation features.

Best free trading journal

See why Journalit is a strong free option if you want to avoid another monthly SaaS bill.

Trading journal with notes

See how written context and screenshots fit into the wider workflow.

Trading journal vs Excel

See when a spreadsheet still works and when a dedicated journal becomes the better fit.

Obsidian trading journal

See how trade import fits into the wider workflow.

Supported broker export paths for trade import

These are the broker and platform formats Journalit currently documents for import. Start with the file your broker actually exports, keep the original file unchanged, and use manual CSV mapping only when the export is not covered by a dedicated guide.

Broker or platform	Export to use	Format	Journalit path	Guide
Interactive Brokers	Flex Query Orders export	CSV	CSV Import	Export guide
Tradovate	Reports → Orders export	CSV	CSV Import	Export guide
TradeZero	Trade history export	CSV	CSV Import	Export guide
TradingView Paper Trading	Order History export	CSV	CSV Import	Export guide
FX Replay	Analytics export	CSV	CSV Import	Export guide
Bybit	Trade History export	CSV	CSV Import	Export guide
Hyperliquid	Trade History export	CSV	CSV Import	Export guide
Blofin	Order Centre futures trade history export	CSV	CSV Import	Export guide
Sierra Chart	Trade Activity Log → Save Log As	Text/CSV-style export	CSV Import	Export guide
MotiveWave	Account → Executions export	CSV	CSV Import	Export guide
ATAS	Trading Journal workbook export	XLSX	CSV Import	Export guide
Trading Technologies	Fills widget download	CSV	CSV Import	Export guide
Rithmic	R \| Trader Pro Order History	CSV	CSV Import	Export guide
JDR / MetaTrader statement	Account History → Save as Report	HTML	Broker adapter	Export guide

Do not see your broker?

Journalit can import many CSV-style exports through manual mapping, but an unsupported broker format may need cleanup or a new adapter. Start with a small sample file and ask in Discord if you want a broker-specific guide added.

Supported guide beats guesswork

If your broker appears in the table, use that guide first. Broker exports often have similar names, and choosing the wrong report is the most common reason imports fail.

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

Install free

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

Start Pro trial

Learn about MetaTrader sync