Skip to main content

Switch from another journal

Your trades are yours. Each page below says how that journal's export works, what lands in TradeFlow Quantum, and what does not — read from the vendors' own documentation on the date shown, with the one honest caveat where a file format is not public.

Four journals, four pages

Only one export format is documented well enough for a one-click preset today. The others import through the generic mapping, which looks for common column names, and the page says so.

  • Switch from Tradervue

    Export recognised from its header; one-click import.

    CSV export · One row per completed trade (round trip), with an execution count · checked 2026-11-09

  • Switch from TradeZella

    CSV export documented; file format not public — imports through the generic mapping.

    CSV export · One row per trade, with an Executions count · checked 2026-11-09

  • Switch from TraderSync

    CSV export documented; file format not public — imports through the generic mapping.

    CSV export · Two files: a trades CSV (one row per trade) and an executions CSV (one row per fill) — the only one of these four journals with a per-fill export · checked 2026-11-09

  • Switch from Edgewonk

    Excel export documented; column set not public — save as CSV, then the generic mapping.

    XLSX export · One row per journaled trade in an Excel sheet · checked 2026-11-09

How an import works here

Upload the file on the import page. A recognised header picks its preset by itself; any other file goes through the generic mapping, which looks for the common header names for symbol, side, price, quantity and date (the rest is optional). Round-trip rows keep the vendor's realized P&L figure as written; per-fill rows are paired into trades here.

The recognised CSV formats page lists every header the importer knows, and the comparison pages cover what differs once you are in.