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

Move your journal from TraderSync to VEXA

Export your TraderSync history as CSV, import it with VEXA AI Import, and keep TraderSync running while you compare the two.

Web Updated

What this does

Moves your TraderSync history across so VEXA has something to score you on from the first day instead of the handful of trades you take this week.

The importer lives on the web. VEXA AI Import takes a CSV, maps the columns itself, and shows you a preview before writing anything.

Before you start

Keep TraderSync connected while you try VEXA. There is no requirement to cancel first, and two weeks of running both is the only comparison worth anything.

Prefer a broker export where you have one. VEXA rebuilds trades from individual executions, so a broker file is the more faithful source. A journal export is generally one row per completed trade. Import the broker file as your base, and use the TraderSync export for older history your broker no longer offers.

Have your timezone answer ready. The import asks what timezone the file’s times are recorded in and what timezone you want to read trades in. The first one decides which day each trade lands on.

Steps

Web only

  1. In TraderSync, export your trade history as a CSV. Their documentation is the authority on where that export currently sits.
  2. In VEXA, open Profile from the sidebar.
  3. Find the VEXA AI Import / Manual CSV Template card and open it.
  4. Under Select Your Broker, search for the broker the trades were taken at rather than for TraderSync.
  5. Under Select Target Account, pick an existing account or create one for the imported history.
  6. Drag the CSV into the upload area.
  7. Press Analyze with VEXA AI and wait for the status to reach Ready to Import.
  8. In Timezone Settings, set the file’s timezone, then set your display timezone. The second is required before you can continue.
  9. Read the preview of the first ten rows and check the dates, symbols and sides.
  10. Press Confirm Import.

What you should see

Counters for Total, Parsed, Rejected and Symbols while the file is read. Rejected rows are listed with a reason rather than dropped silently, so you can see exactly what VEXA refused and why.

After confirming, an Import Complete panel reports Trades Created, Open Positions Updated and Duplicates Skipped.

Open your trades list and check your oldest and newest imported trade against TraderSync. If the two ends agree, the history between them will too.

If it doesn’t work

“We couldn’t parse this file yet.” The layout was not readable. The message offers a support request that sends the file to the team, which is the quickest way to get an unusual export supported.

Everything was rejected. Confirm you exported CSV and not a spreadsheet file, and that no spreadsheet app re-saved the dates in a different format on the way through.

The trade count looks low. Check whether the export covered your full date range. Many exports default to the last month.

Your P&L reads higher than it should. The export is probably gross rather than net. Commissions and fees have to be in the file for VEXA to subtract them.

Related

Move your journal from TradeZella to VEXA Export your TradeZella history as CSV, import it with VEXA AI Import, and run both journals side by side while you decide. Move your journal from TraderVue to VEXA Export your TraderVue history as CSV, import it with VEXA AI Import, and run both journals in parallel while you decide. Move your journal from Edgewonk to VEXA Export your Edgewonk history as CSV, import it with VEXA AI Import, and run both while you compare Edgewonk's Tiltmeter against VEXA's CDI scores.

Still stuck? Email support@vexatrade.ai.