Can you journal with MT4 / MT5?

Yes, via history export or sync. The real issue is whether the import is reliable.

CSV or automatic sync?

CSV is fine to start. Sync is what stops you quitting when volume rises.

What about partial closes and commissions?

If the journal skips them, your R and expectancy are wrong.

Tools & comparisons

MT4 / MT5 trading journal: import and track MetaTrader trades

If you trade on MetaTrader, your MT4 or MT5 journal should not depend on typing every fill by hand. Here is how to import trades, what usually breaks, and what to demand from a tool.

L’équipe Altiora·September 18, 2026·2 min read

An MT4 or MT5 trading journal does one job: turn MetaTrader history into decisions (discipline, R, setups) without retyping every line. People keep searching how to import MetaTrader trades because that is where journaling dies.

This is not another best trading journal software roundup. It is about the MT4/MT5 pipeline: what has to work technically.

Three ways to feed the journal from MetaTrader

Manual entry. Fine for five trades a week. Beyond that, most people quit.

CSV or HTML account export. Better. You still export, map columns, and fight duplicates.

Import / automatic push. On Altiora, MetaTrader 4 and 5 feed via MT4/MT5 import; pricing describes an Expert Advisor that pushes closed trades continuously (not manual entry, and not a one-click OAuth flow like cTrader). Goal: tickets, volumes and fees in the journal without retyping. Confirm a test week (MT tickets = journal rows) before moving full history. The same logic as automated vs manual journaling applies straight to MetaTrader.

MetaTrader export in 5 steps (CSV)

In MT4/MT5, open the Terminal (Ctrl+T) → Account History tab.
Right-click → Custom period (at least the week you want to import).
Right-click → Save as Detailed Report (or Report), HTML/CSV depending on build.
Open the file and check tickets, volumes, and commissions before import.
Import into the journal (CSV upload or MT4/MT5 flow). Confirm there are no duplicate tickets.

If your tool offers an EA / automatic import, switch to it once a test week matches cleanly.

Common import mistakes

Duplicates after a re-export (same ticket twice). Partial closes split wrong, so PnL and R lie. Account currency misread. Demo and live mixed in one journal. Fees ignored: a pretty win rate that is fake.

Before you judge a strategy, check that one week of MetaTrader tickets matches the journal rows.

After import: what the journal is for

A clean import only helps if it feeds decisions. Concrete examples: equity curve and daily P&L (calendar), performance by tag/setup, emotion notes on overtrading days, checking that risk per trade matches your rule. Without that, you only moved MetaTrader history into another table.

What to require from an MT4 / MT5-ready journal

Reliable, documented import. MT4 and MT5 support if you use both. Stats in R and by setup, not only a tick table. A way to mark plan adherence (tag or yes/no note), or you only audit the market. A trial on your broker and your history (7-day trial - card required, no charge if you cancel before day 7).

Try tracking on your MetaTrader trades

To test on your MetaTrader account: create an Altiora account (7-day trial - card required, no charge if you cancel before day 7), import one week via the MT4/MT5 flow, then compare tickets and rows. Integration detail: /features.

Frequently asked questions

Can you journal with MT4 / MT5?: Yes, via history export or sync. The real issue is whether the import is reliable.
CSV or automatic sync?: CSV is fine to start. Sync is what stops you quitting when volume rises.
What about partial closes and commissions?: If the journal skips them, your R and expectancy are wrong.

About the author

L’équipe Altiora

Altiora editorial team

Altiora's editorial team brings together active traders and the product team. We write about discipline, journaling and performance analysis, grounded in how the platform actually works. We never give investment advice.