Reporting and evidence

3 min read

Export NinjaTrader trade history to CSV or Excel

Choose the record type before exporting. Orders, individual fills and matched trades describe different events, so their row counts need not match.

Conceptual illustration of three ivory trays holding one large teal record, separate amber fill tokens and paired teal-and-amber records beside a grid sheet and archive folder.

Quick answer

Open Control Center > New > Trade Performance, choose From and To dates, and select Generate. Choose Trades, Executions or Orders in Display, filter the account and instrument, then right-click that grid and select Export. Choose CSV or Excel and a filename.

Choose trades, executions or orders

The export command saves the grid you selected. Choose the view required by your spreadsheet or journal before creating the file.

DisplayWhat a record representsUseful for
OrdersA historical order.Reviewing recorded orders.
ExecutionsAn individual fill, including its quantity, price and identifiers.Matching fills by execution ID and Order ID.
TradesA completed entry/exit pairing based on position and quantity.Reviewing completed-trade results.

Check dates, account filters and identifying columns

The Control Center Executions tab shows the current day. Use Trade Performance when you need a historical date range.

Expand the report’s Filter options to select accounts and instruments. Filtering works on executions, not completed trades. Templates selects ATM strategies. After changing dates and pressing Generate, review the filters again: the new scan can recheck previously unchecked items.

A report can include activity before its From date to reconstruct a position back to when it was flat. Earlier rows do not by themselves mean the date selection failed.

For an execution export, review Instrument, Quantity, Price, Time, ID and Order ID. Account Display Name and Account Name can differ. Grid Properties controls visible columns; inspect the saved file’s headers before importing it into another application.

Why the three exports can have different row counts

One order can produce several executions through partial fills. For example, a three-contract order filled as one contract and then two has two execution records for that order; the quantities still total three.

Trade Performance treats scaled entries and exits as separate trades. Its pairing follows the overall account position, even when multiple NinjaScript strategies trade that account. It does not isolate the pairings by strategy. For an individual strategy’s performance, use its performance view from the Strategies tab.

Compare quantities and identifiers within the same record type before treating a row-count difference as a duplicate or missing fill.

An export cannot recover missing executions

Performance reporting depends on the historical executions available to NinjaTrader. Not every broker supplies that history; an order filled while the platform was disconnected can therefore be absent from the report. Compare the missing period with the broker’s execution records before deciding what needs correction.

For unexpected commission totals, use the separate commission-template guide. If support requested application diagnostics, collect log and trace files; a Trade Performance CSV serves a different purpose.

Official sources

Platform monitoring

Keep platform health in view

Ninja Watchdog monitors NinjaTrader and supports recovery after platform interruptions. Email alerts are available today; SMS and WhatsApp alerts are coming soon.

Explore the free trial