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.
What this does
Gets your existing trade history into VEXA, so your scores and metrics start from what you have actually done rather than from today.
Do the import on the web. VEXA AI Import reads a CSV it has never seen before, works out which column is which, and shows you a preview before anything is written.
Before you start
Do not cancel TradeZella first. Nothing about importing requires it, and running both for a couple of weeks is the only honest way to compare them on your own trades. Your VEXA trial is long enough to do exactly that.
Import from your broker if you can. A broker export contains individual executions, which is what VEXA rebuilds trades from, and it is the more accurate source. A journal export is usually one row per finished trade. Use the broker file as your main import, and use the TradeZella export to fill in history your broker will not give you any more. See the broker articles for how far back each broker’s export reaches.
Know your timezone. VEXA asks two questions during the import: what timezone the times in the file are recorded in, and what timezone you want to read your trades in. Getting the first one wrong shifts every trade onto the wrong day.
Steps
Web only
- In TradeZella, export your full trade history as a CSV. Their own help center is the authority on where that export currently lives.
- In VEXA, open Profile from the sidebar.
- Find the VEXA AI Import / Manual CSV Template card and open it.
- Under Select Your Broker, search for the broker the trades were taken at, not for TradeZella.
- Under Select Target Account, choose an existing account, or create one so the imported history stays separate from your live sync.
- Drag the CSV into the upload area.
- Press Analyze with VEXA AI and let the status chips run through to Ready to Import.
- In Timezone Settings, set the timezone the file’s times are in, then set the timezone you want to read your trades in. The second one is required.
- Read the preview of the first ten rows. Check that the dates, symbols and sides look right.
- Press Confirm Import.
What you should see
Four counters above the preview while VEXA reads the file: Total, Parsed, Rejected and Symbols. A small number of rejected rows is normal if the export has summary or header rows in it. A large number means the file is not what VEXA expected, and the reason is printed against each row.
After confirming, an Import Complete panel shows Trades Created, Open Positions Updated and Duplicates Skipped.
Then open your trades list and check the oldest and the newest trade against your TradeZella records. If both ends match, the middle almost always does.
If it doesn’t work
“We couldn’t parse this file yet.” VEXA could not make sense of the layout. The message offers a support request that sends the file to the team so a parser can be added. That is the fastest route for an unusual export.
Every row was rejected. Check that you exported CSV rather than XLSX, and that you did not open and re-save the file in a spreadsheet with a different date format.
Your P&L does not match TradeZella’s. Check whether the export is gross or net. VEXA works from net figures where the file provides them, and a gross export will read higher.
Duplicates. Re-uploading the same file is safe. VEXA matches on the facts of each execution and skips what it already holds, so an import that reports everything as a duplicate has not lost anything.
Related
Still stuck? Email support@vexatrade.ai.