Importing executions
Getting your broker data into the trade log.
The import screen
Everything the product calculates comes from your executions, so import is the foundation. The import screen handles files directly; for brokers that do not export usable files, see the Bridge chapter.
The layout is simple by design:
- An account selector at the top.
- A drop area in the middle.
- A preview and confirmation once a file is read.
The drop area accepts a click to browse, a paste of file content, or a drag and drop. Supported file types include CSV, TXT, JSON, Excel, and TLG.
Also in the header:
- Load sample data puts a demo set into your trade log so screens are populated while you explore. It is tagged, and the screen reminds you to remove it before importing your own data.
- Custom Import switches to the advanced mapper for formats the automatic converters do not handle.
Import is idempotent in the way that matters: executions already in your log are recognized and not duplicated. If everything in a file is already present, the screen says so rather than importing nothing silently.
Formats and brokers
Format detection runs automatically. When the content is ambiguous the screen asks you to pick, and the format list marks which options actually match the file you provided.
| Format | What it is |
|---|---|
| Auto-detect | Detect from the file content. The default |
| IBKR TLG | Interactive Brokers TradeLog Gateway files |
| CSV with Headers | A standard CSV with a header row |
| CSV (No Headers) | A CSV with fixed columns and no header |
| DAS / LightSpeed round-trip | Closed position CSV, converted back into executions |
| WeBull | WeBull orders CSV |
| Internal Format | The product's own CSV format |
Separately from the file format, you confirm which broker the file came from. That matters because two brokers can produce the same shape of CSV with different meanings for the same column, and because the broker is recorded with your executions.
If a file matches nothing, the import can build a mapping for it with AI assistance: you confirm the interpretation, then either Confirm import or Edit in Custom Import to adjust it by hand. The mapping you approve is saved to your profile so the next file from the same broker is handled without repeating the work.
The DAS and LightSpeed round-trip converter is worth understanding. Those exports contain closed positions rather than fills, so the converter reconstructs executions from them. The reconstruction is faithful for position and result but it cannot invent fills that the export does not describe.
The preview
Nothing is stored until you confirm. The preview is your chance to catch a bad file before it contaminates every statistic you have.
The header reads Import preview and shows a summary: how many trades, how many executions, how many are new, how many are already in your log, and the time range covered.
A switch toggles the view between Trades and Executions. Trades are the round trips the converter built; executions are the individual fills. Look at both. The executions tell you whether the fills are right; the trades tell you whether they were paired into positions the way you actually traded.
Actions:
| Button | What it does |
|---|---|
| Confirm import | Writes the executions into your trade log |
| Download preview CSV | Exports what you are about to import, for checking outside the app |
| View raw source | Shows the original file content |
| Cancel | Discards the preview |
What to check before confirming: the date range is the range you expected, the symbols are yours, the sizes are plausible, and the account alias at the top is the right one. Importing to the wrong alias is the most common mistake, and it is easier to fix before confirming than after.