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

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.

Web Updated

What this does

TraderVue users tend to arrive with years of history rather than months, so the steps below assume a large import done in several files rather than one.

The importer lives on the web. VEXA AI Import reads a CSV, maps the columns itself, and previews the result before writing anything.

Before you start

Do not cancel TraderVue to do this. Export, import, and run both for a fortnight. That is the only comparison that tells you anything about your own trading.

A broker export beats a journal export. VEXA rebuilds trades from individual executions, so a file straight from the broker carries more of what VEXA needs. Use TraderVue’s export for the years your broker will no longer hand over, which for a long-standing TraderVue user is usually the point of the exercise.

Import in chunks if the history is very long. One file per year is easier to check than one file per decade, and re-uploading an overlapping range is harmless because duplicates are skipped.

Steps

Web only

  1. In TraderVue, 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 TraderVue.
  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 timezone the file’s times are recorded in, then set the timezone you want to read trades in.
  9. Read the preview of the first ten rows and check the dates, symbols and sides.
  10. Press Confirm Import.
  11. Repeat for each additional file.

What you should see

Counters for Total, Parsed, Rejected and Symbols while the file is read, then an Import Complete panel with Trades Created, Open Positions Updated and Duplicates Skipped.

On the second and later files, expect a duplicate count. That is the overlap being caught, which is what you want.

Once everything is in, open your trades list, sort to the oldest trade, and check it against TraderVue. Then do the same at the newest.

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 so a parser can be added.

The import stopped on a futures contract. VEXA refuses to import a futures trade whose contract multiplier it does not recognise, rather than storing P&L it knows is wrong. The message names the symbol. Send it to support and it can be added.

Options P&L looks a hundred times too small or too large. That is a multiplier problem in the source file. Check that the export carries a multiplier column, and tell support which symbols are affected.

Your P&L does not match TraderVue’s. Check gross against net first. Commissions and fees must be present 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 TraderSync to VEXA Export your TraderSync history as CSV, import it with VEXA AI Import, and keep TraderSync running while you compare the two. 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.