Features Sentinel Brokers Community Pricing About Us Why VEXA Support Get Access Now

Import trades from NinjaTrader

NinjaTrader exports from the Executions tab of a Trade Performance report, and its timestamps use whatever timezone your platform is set to.

Same on every platform Updated

What this does

Brings NinjaTrader futures trades into VEXA from a Trade Performance export.

Before you start

  • Automatic sync shows a Coming soon banner. File import is the route today.
  • Check your platform’s timezone before exporting. NinjaTrader stamps the export in whatever timezone the platform is configured for, which for CME futures is usually Central. Find it under Tools > Options > General > Time Zone inside NinjaTrader, then set the matching broker server timezone in VEXA. See Set your broker server timezone.
  • Export the Executions tab, not the summary. VEXA reconstructs trades from fills.
  • E-mini and micro contracts, energies, metals and the rest of the CME and CBOT lineup are all supported, with the right contract size applied automatically.

Steps

Same on every platform

  1. Launch NinjaTrader and log into the trading account.
  2. In the Control Center, choose New, then Trade Performance.
  3. Open the Executions tab.
  4. Set the date range. All time gives you your full record.
  5. Right-click inside the executions list and choose Save As.
  6. Save as CSV.
  7. Upload it to VEXA, with the broker server timezone already set.

Contract sizes

VEXA applies the contract size for you, from a single shared table: ES at $50 a point, NQ at $20, MNQ at $2, and so on across the CME and CBOT contracts, including the micros.

If a contract is not in that table, the import still runs and the result panel warns you that the contract was unrecognised and imported with a size of one. That trade’s profit will be wrong by exactly the contract size, so report the symbol rather than working around it. See “Unrecognized futures contract” warning, and How futures contracts are imported for the wider picture.

Limits and gotchas

  • Date formats vary by region. US, European and ISO date formats are all handled, so you do not need to change anything in NinjaTrader first.
  • The timezone is the usual failure. A futures session that runs through midnight lands on the wrong day when the offset is wrong, which then puts the trade in the wrong journal day.
  • If your figures do not match NinjaTrader, re-import. Re-importing never duplicates.

What you should see

A result panel naming the NinjaTrader executions format, with counts. Check one futures trade’s profit against NinjaTrader before uploading a long history: if the contract size is right for one, it is right for all of them.

If it doesn’t work

  • “No trades were found in this file.” You exported a summary or performance tab rather than Executions.
  • Profit is out by a large round multiple. The contract was not recognised. Look for the warning on the result panel.
  • Trades are a day out. The platform timezone and the VEXA setting disagree.

Related

Upload a statement or CSV Where the upload area is on each device, which file types VEXA accepts, and what happens while the import is running. The three timezones VEXA holds The three different timezones VEXA holds, which brokers need the server one set, and where the setting lives on each device. Import trades from Tradovate Tradovate's order export carries no commission, so VEXA estimates it. The performance report carries the real fees, and it is the one to use.

Still stuck? Email support@vexatrade.ai.