Broker Sync

FTJ supports read-only import of available broker account history through cTrader, MetaTrader 4 and MetaTrader 5 workflows.

Navigate to Brokers in the sidebar.

FTJ does not place, modify, copy or close trades on any broker platform.

General Workflow

Select cTrader, MT4 or MT5.
Connect to or read the active platform account.
Link the broker/platform account to an FTJ account.
Fetch or preview executions.
Select the rows to import.
Import the selected data.

Demo Mode

Connection setup and account-link management remain available.
Fetch, preview and import can start while the journal contains fewer than 20 persisted trades.
An authorised selected import is complete and is not truncated at 20 trades.
At 20 or more persisted trades, new fetch/preview/import operations are blocked.
Disconnect, sign-out, link editing/removal and connection cleanup remain available after the limit.

cTrader

Uses browser-based OAuth 2.0.
FTJ does not store the broker password.
Internet is required for authentication and fetching.
Reconnect when access expires or is revoked.

MetaTrader 4

Select the intended local terminal.exe.
Click Install MT4 Bridge for a first installation, or Update MT4 Bridge when FTJ reports that the bridge is incompatible.
FTJ writes the files to the selected terminal’s data folder at MQL4/Experts/Forgalis MT4 Bridge.
Install and Update use this same folder. Update replaces the existing ForgalisMt4Bridge.mq4 and ForgalisMt4Bridge.ex4 files and does not intentionally create a second bridge folder.
Open the same MT4 terminal with the intended account active.
Restart MT4 or refresh Expert Advisors in Navigator.
Remove any already-running ForgalisMt4Bridge from its chart and attach the current copy again.
Enable Expert Advisor execution / AutoTrading.
Load the account-history period that should be available.
Return to FTJ, click Read Active MT4 Account, link the account, fetch executions and import selected rows.

Replacing files does not update an Expert Advisor that is already running on a chart. The refresh/restart and reattachment steps are required before the new bridge version is active.

The bridge is read-only. The public ForgalisMt4Bridge.mq4 source file is included for transparency.

Manual MT4 fallback

Use Export Bridge Files when automatic installation cannot resolve the correct data folder.

Export the current bridge files from FTJ.
In MT4, choose File -> Open Data Folder.
Open MQL4/Experts/Forgalis MT4 Bridge.
Copy the exported .mq4 and .ex4 files into that folder and replace the older files.
Restart MT4 or refresh Expert Advisors.
Remove the running bridge from the chart and attach the current copy again.

If two Forgalis bridge folders are visible, use Forgalis MT4 Bridge. Confirm that the current bridge files are in that folder and attach that copy. Do not delete another folder until you have confirmed that it contains no custom or separately compiled files.

MetaTrader 5

Select the intended local terminal64.exe.
Open that same MT5 terminal with the intended account active.
Ensure the required deal/order history is available locally.
Read the active account, link it, fetch executions and import selected rows.

Bridge Compatibility

Current FTJ releases validate the MT4/MT5 bridge protocol before importing contract-size-aware data.

If FTJ reports that the bridge is old, missing a supported protocol version or newer than the app understands:

Stop the current import attempt.
For MT4, use Update MT4 Bridge and complete the refresh/restart and reattachment steps above.
For MT5, replace the bridge executable with the version included in the current FTJ package.
Retry only after the platform is running the current bridge.

Do not bypass compatibility warnings. They protect quantity and contract-size interpretation.

Linking Accounts

Link each broker/platform account to the correct FTJ account. The FTJ account base currency should match the broker deposit currency.

Demo Mode supports creating multiple FTJ accounts, but the 20-trade allowance is global across the database.

Imported Data

FTJ imports only fields exposed by the source, potentially including:

symbol, side, quantity and price;
execution time and broker identifiers;
realised P/L and conversion information;
fees and swap;
stop loss and take profit;
contract-size/quantity-normalisation information.

FTJ cannot safely reconstruct historical values the source does not expose.

Quantity and Contract Size

Trade quantity is stored in units. MT4/MT5 contract-size information helps FTJ normalise broker lots into units. Verify the resulting Position size and Lot Settings when a broker uses unusual symbol specifications.

Broker Reported and Calculated P/L

Eligible imported execution-based trades can expose:

Broker reported - use usable booked account-currency P/L supplied by the broker.
Calculated - rebuild Gross P/L from the current executions and available conversion information.

Imported fees/swap can also support separate Adjust Costs journal adjustments without replacing the original broker source values.

Duplicate Prevention

Re-fetching and re-importing the same history should not intentionally create duplicate executions or trades. FTJ uses source identifiers where available and fallback matching when needed.

History Depth

FTJ can import only the history exposed by the broker/platform. MT4 and MT5 depth depends on what is available in the selected local terminal.

Troubleshooting

Use the Status Log and include the FTJ version, platform, account type, symbol and approximate execution time in a support report. Redact tokens, licence keys and other secrets.