MT4 trading journal — import your MetaTrader 4 history

File-based import. MetaTrader 4 statements are read as CSV or JSON.

There is no automatic sync. MetaTradee does not connect to MetaTrader 4, does not use the investor password, and never asks for broker credentials or an API key. You export a statement; you upload it. That is the whole integration, and it is deliberately the boring kind — nothing to revoke, nothing to leak.

File types

.csv, .json, .txt

Maximum file size

20 MB

Rows per file

50,000 — split larger exports

Spreadsheets

XLSX is refused; export or re-save as CSV

Archives are not unpacked, so upload the statement itself rather than a ZIP of one. Anything the importer cannot read is refused at the upload step with the reason, before any of it reaches your journal.

1. 1Open MetaTrader 4 and go to the Terminal panel (Ctrl+T), then the Account History tab.
2. 2Right-click inside the history grid and choose the period you want — All History, or a custom range.
3. 3Right-click again and choose Save as Report (or Save as Detailed Report). MetaTrader 4 writes an HTML file — it has no direct CSV option.
4. 4Open the saved report in a spreadsheet application and save it as CSV. That converted file is the one MetaTradee reads.

The conversion step is not optional. MetaTrader’s own report formats are HTML and spreadsheet formats; none of them is CSV, and an HTML statement will not parse. If your file opens as a web page in a browser, or ends in .xlsx, open it in a spreadsheet application and save it as CSV first.

1. 1Open Journal → Import and choose your file.
2. 2Pick MetaTrader 4 as the source so its column names are recognised automatically.
3. 3Check the mapping. Anything auto-detected can be overridden by hand.
4. 4Review the preview — this is a dry run and writes nothing.
5. 5Confirm. The server re-validates every row before it is written.

The MetaTrader 4 mapping recognises these trade fields. Anything the file does not contain is simply left empty rather than guessed:

• symbol
• direction
• entry price
• exit price
• quantity
• stop loss
• take profit
• commission
• swap
• fees
• opened at
• closed at
• notes

Four derived figures — gross P&L, net P&L after commission, swap and fees, the planned reward-to-risk ratio, and duration — are not taken from the file. They are computed at write time by the same code that handles a manually logged trade, so imported and manual trades reconcile exactly.

Reward-to-risk is not a realised R-multiple. It is the ratio of your target distance to your stop distance — a property of the plan, computed before the outcome is known. A realised R-multiple divides what the trade actually returned by the risk accepted at entry, and MetaTradee does not currently compute that figure. If you track it, bring it in as your own column.

• MT4 calls the instrument column "Item" rather than "Symbol"; the MT4 mapping recognises both.
• MT4 reports size in "Lots", which is mapped to quantity.
• MT4 uses "Open Time" and "Close Time" explicitly, which map straight through.
• MT4 is always hedging-style, so each ticket is its own row — one row per trade, which maps cleanly.

• No automatic or scheduled sync — every import is a file you upload
• Only CSV and JSON statements parse; HTML and PDF exports do not
• Import is a paid feature, starting on Trader at $19 per month
• Open positions are not tracked live; the journal records trades, not a live account
• Backtesting is not available on any plan — trade replay of recorded sessions is

The file will not upload. Check the extension: an HTML statement is the usual culprit. Re-export as CSV.

Columns landed in the wrong fields. The mapping step is editable — reassign any column by hand before previewing. Auto-detection is a starting point, not a decision.

Some rows were rejected. Rejected rows are listed with their row number and the reason. They are never silently dropped, so a partial import tells you precisely what did not make it.

I imported the same period twice. Duplicates are detected by content hash against both existing trades and other rows in the same file, and are flagged in the preview before anything is written.

Dates or numbers look wrong. The parser handles MetaTrader’s YYYY.MM.DD HH:MM:SS format and locale-formatted numbers such as 1.234,56. If a value still looks off, the preview will show it before it is committed — that is what the dry run is for.