Updated: For the Orders CSV format, follow the Tradovate Orders FIFO import guide.
Tradovate export can be clean if you use the right menu path and date window. The common failure is exporting account statements instead of execution history, which creates incomplete rows for journaling.
Use this path inside Tradovate web: Reports or Performance area, then select executions or fills, set your exact date range, and export CSV. If you trade across sessions, include full UTC day windows so overnight fills are not dropped.
After export, check five columns before upload: symbol, side, quantity, entry or fill price, and exit or close price. If scaled entries are separated into multiple fills, keep all rows and let the importer aggregate where supported.
A frequent issue is missing fees. Some exports include commissions separately while others blend fees into net P&L. If your journal expects explicit fees, map that column manually or enable commission defaults.
Snap Trade is faster for single trades. Take a confirmation screenshot, upload, verify parsed values, and save. This is ideal when you need fast same-day logging without waiting for end-of-day exports.
Upload a screenshot and review parsed trade fields
When should you use CSV versus screenshot. Use CSV when you need bulk history, backfill, or multiple days. Use screenshot when you want immediate logging after each trade. Many traders use both methods in one workflow.
If a row fails import, first normalize timestamp format and decimal separators. Then confirm symbol formatting such as MNQ versus NQ contract roots. Finally, check whether your file has header labels recognized by the mapper.
See Rithmic import guide and ThinkOrSwim import guide for platform-specific differences. If you trade Topstep accounts, pair this with Topstep setup steps.