MetaTrader 4
Select the local MT4 terminal, run the read-only Forgalis bridge Expert Advisor and read history from the active account loaded in that terminal.
Read the MetaTrader import guideBroker and platform imports
Bring supported broker history into one local review workflow.
Forgalis TradingJournal supports user-triggered, read-only history workflows through MetaTrader 4, MetaTrader 5 and cTrader, plus supported file imports when a direct platform workflow is not the right source.
Imports run when you choose to fetch or import history. FTJ does not place, modify, copy or close trades.
Four supported routes
Use the workflow that matches how your history is available.
The four routes do not expose identical fields or require the same setup. They all lead into the same FTJ journal and review structure after import.
MetaTrader 5
Select the local MT5 terminal, keep the intended account active and use the bundled bridge to preview and import the history available to FTJ.
Read the MetaTrader import guidecTrader OAuth
Sign in through cTrader’s authorisation page, link the intended account, preview the history exposed by the platform and import selected executions.
Read the focused cTrader guideFile import
Import a supported broker or platform export with the cTrader template or custom column mapping. The current supported file format is CSV.
Compare the setup
Each source has a different connection boundary.
Choose based on the platform and records you actually use, not on the assumption that every source behaves like a cloud account connection.
| Source | How FTJ reads it | What you do | Important boundary |
|---|---|---|---|
| MetaTrader 4 | A read-only Expert Advisor bridge reads the selected local terminal. | Open the intended account, load the required history, run the current bridge and fetch from FTJ. | The selected terminal, active account, bridge version and locally available history determine what FTJ can read. |
| MetaTrader 5 | The bundled local bridge reads the selected MT5 terminal and active account. | Open the intended account, ensure its history is available and fetch or preview it from FTJ. | History, symbol specifications and fields depend on what the local platform exposes. |
| cTrader | Browser-based OAuth authorisation and cTrader history retrieval. | Authorise access, link the account, preview rows and import selected executions. | Internet is required for authorisation and fetching. Available fields depend on cTrader data. |
| File import | FTJ reads a supported local file through the cTrader template or custom mapping. | Select the destination account and map the required fields when using a custom export. | Import depends on supported data such as symbol, direction, entry details and quantity or lots. |
Platform-level compatibility
Start with the platform and history source, not a long broker list.
The MT4 and MT5 workflows read the active account from the selected local terminal. Broker, company and server information comes from the platform rather than a short public list of individually integrated brokers.
- Compatible MT4 and MT5 accounts can be read through their local terminals.
- cTrader accounts use authorised platform access rather than a broker password stored in FTJ.
- Contract size and quantity information is validated where it is needed for safe normalisation.
- Available fields, history depth and unusual symbol specifications still depend on the source.
Read-only and user-triggered
Import history without turning FTJ into an execution platform.
FTJ separates the source of the execution record from the place where you trade. You decide when to read, preview and import history into the journal.
- No order placement, modification, copying or closing through FTJ.
- Preview and select broker executions before persisting them to the journal.
- Link each external account to the correct local FTJ journal account.
- Re-fetching uses source identifiers and fallback matching to avoid intentional duplicates where possible.
What the source can contribute
Import the facts that exist, then add the review context that does not.
FTJ cannot safely reconstruct values missing from the source. Imported fields vary, but the journal structure around the resulting trade remains consistent.
Execution facts
Depending on the source, records may include symbol, side, quantity, price, timestamps and broker identifiers.
Costs and outcomes
Where supplied, FTJ can retain realised P/L, commission or fees, swap and available conversion information.
Your review context
Add screenshots, notes and reusable review fields after import so the execution record explains more than the result alone.
Platform-specific follow-up
Use the focused guide for the platform workflow you need.
The broad imports page remains the starting point. The MetaTrader guide explains local-terminal selection, bridge setup and history boundaries, while the cTrader guide covers browser authorisation and cTrader history retrieval.
Read the MetaTrader 4 and 5 guide Read the focused cTrader guideTest the workflow with your source
Import a small sample before moving your full review process.
The free Demo lets you test supported imports with documented trade-count limits. Use representative records, verify the resulting fields and decide from the actual journal workflow.