Skip to content
Guide

Import your trade history without breaking the numbers.

Most journal imports fail quietly: a wrong decimal separator, a local timestamp read as UTC, or duplicate partial fills. This guide explains how to export, map and verify the file so the P&L you see matches the exchange.

CSV import on every planDry run before writingUndo a batch

The six steps

From exchange export to a reviewable trade

  1. 1

    Export the execution history, not the order history

    An order can fill in several pieces. Export executions or fills so the journal can reconstruct one trade from all of its partial fills. Order history alone loses size and price detail.

  2. 2

    Keep the file exactly as the exchange produced it

    Do not open and re-save it in a spreadsheet first. Spreadsheet apps rewrite timestamps, strip leading zeroes and can change the decimal separator.

  3. 3

    Map columns explicitly in the wizard

    The importer never guesses a column. You choose which header holds the timestamp, symbol, side, price, quantity and fee. Required fields are highlighted before anything is written.

  4. 4

    Run the dry run

    The dry run parses, maps and validates without writing. It reports valid rows, rejected rows with the exact reason, duplicates already in the file and your plan limits. No quota is used.

  5. 5

    Review rejected rows, then confirm

    Download the rejected-row report, fix the source file and retry. Only after confirmation are executions stored and reconstructed into trades.

  6. 6

    Review the trades in your inbox

    Imported trades arrive in Unreviewed trades. Add strategy, planned stop and take-profit, planned risk and reasoning. Until those exist, analytics say not enough data rather than guessing.

Template status

A template becomes verified only after a real export file has been imported and checked. Until then the generic mapper is the primary path.

  • Binance spot trade historyunverified
  • Binance USDⓈ-M futures trade historyunverified
  • Bybit execution historyunverified
  • OKX fills historyunverified
  • Generic column mapperworks with any CSV

No guessing

The importer rejects ambiguous dates, impossible numbers and rows it cannot map. It never invents a side, a price or a stop. Missing analytics fields are shown as “not enough data”.

CSV export is safe to reopen

Exported cells that start with =, +, - or @ are prefixed so a spreadsheet cannot execute them as formulas.

Try it with your own file

Open TradeDNA → Import & sync. The dry run needs no quota and writes nothing.

Open the importer

FAQ

Questions traders ask before importing

If a question is missing, the same answers apply to the in-app wizard.

Which exchange CSV formats are officially supported?

The generic column mapper works with any CSV you can export. Exchange-specific templates for Binance, Bybit and OKX are included but marked unverified until a real export file has been tested, because exchanges change their export layouts without notice.

Does the import use my plan quota if every row is rejected?

No. A dry run never uses quota. If every row is rejected or every row already exists, nothing is committed and no import allowance is consumed.

How are partial fills and position flips handled?

Executions are combined into a net position with an average entry. A fill that closes more than the open size records a flip into the opposite direction. Fees and funding are included in the realized P&L, and the exchange-reported P&L is cross-checked where the export provides it.

What happens to my time zone and decimal separator?

You choose the file time zone, decimal separator and date order before previewing. Timestamps are stored in UTC. Ambiguous day/month values are rejected rather than guessed.

Can I undo an import?

Yes. Each committed batch can be undone from Import history. The batch rows are removed, other batches are rebuilt from their remaining executions, and the audit trail is kept. Import quota is not refunded.

What does read-only exchange sync require?

A plan that includes exchange sync and a dedicated read-only API key. The app refuses keys with trading or withdrawal permission. When an exchange cannot report permissions, you confirm read-only explicitly. Cloudflare cannot provide a fixed outbound IP, so IP allowlisting is not possible.