MetaTrader 5 is the workhorse of prop-firm forex, which means most copiers get built on top of it — and most of the ways copiers quietly go wrong are MT5-specific. The setup is easy. The pitfalls are where accounts get lost.
MT5 copier options: EA, terminal, and broker-side
There are three broad ways to mirror trades between MT5 accounts, and they trade off convenience against reliability differently.
| Approach | How it works | Main weakness |
|---|---|---|
| Terminal-to-terminal | A local copier app reads the master terminal and pushes orders to slave terminals on the same machine. | Every terminal must stay open and logged in; one crash stops the fleet. |
| Expert Advisor (EA) | A publisher EA on the master chart and a receiver EA on each slave chart relay fills between terminals. | Still terminal-bound and chart-bound; needs a VPS to stay alive. |
| Broker-side relay | A server-side connection mirrors fills without a chart or a running terminal. | Requires an integration that speaks to the broker directly. |
The first two keep the copier tied to a running MetaTrader instance — close the terminal, kill the copier. A broker-side relay is the exception: Shibiki’s MT5 integration mirrors master fills to each slave through a broker-side path, so the copy keeps flowing with every chart closed, and because the relay lives at the broker it can refuse an oversized order at the source instead of after it fills.
Symbol suffix mismatches between brokers
The pitfall that catches every new MT5 copier operator is the symbol suffix. Brokers name the same instrument differently — EURUSD on one broker is EURUSD.r, EURUSD-ECN, or EURUSDm on another. A copier that blindly forwards the master’s symbol string sends an order for an instrument the slave broker has never heard of, and the copy silently fails.
Because prop accounts often live at different brokers, this bites hard the moment your master and slaves aren’t on the identical feed:
- Map symbols explicitly between master and each slave rather than assuming the strings match.
- Test every instrument you trade, not just your main pair — suffixes can differ per asset class within the same broker.
- Watch for missing instruments: a slave broker may not list an exotic or an index CFD at all, in which case that leg should be filtered, not force-sent.
A single unmapped suffix means one account silently stops copying while you believe the whole fleet is in sync — the worst kind of failure, because nothing errors on the screen you’re watching.
Lot rounding and minimum-volume limits
Once symbols map, the next trap is volume. Every MT5 symbol has a minimum lot, a lot step, and a maximum, and they aren’t identical across brokers. When your copier scales a master position down for a smaller slave account, the result rarely lands exactly on the slave’s allowed step — so it gets rounded.
That rounding matters more than it looks:
- Round up past the intended size and the slave account carries more risk than you sized for, eating into a tighter drawdown.
- Round down to the minimum lot and a small account may be forced into a position larger than its risk budget allows, because the broker won’t accept anything smaller.
- Hit a symbol’s minimum volume and an account that should have taken a fractional position takes a full minimum lot — or skips the trade entirely.
Before you deploy, run each account’s intended size through a lot size calculator against that broker’s actual step and minimum, so you know how the copy will round before it costs you drawdown. Firms differ here too — FTMO and FundingPips may run different brokers with different volume specs, so confirm the contract details per account rather than assuming they match.
Latency: local terminal vs VPS
Copying introduces a gap between the master fill and the slave fill, and on MT5 that gap is dominated by where your terminals run. A copier running on your home laptop has to route the master’s fill out to the internet and back to each slave broker — tens or hundreds of milliseconds, worse if your connection hiccups. For a scalping strategy, that slippage between master and slave can turn a winning master trade into a losing copy.
- Run terminal- and EA-based copiers on a VPS close to the broker’s servers to cut the round trip.
- Keep the master and slaves on the same VPS where possible so the hop between them is local.
- Recognize that a broker-side relay sidesteps most of this — with no local terminal in the loop, there’s no laptop-to-cloud round trip to lose ticks to.
Latency you can’t eliminate, you should at least measure: a copier that consistently fills slaves a few ticks worse than the master is quietly taxing every trade.
Enforcing risk limits at the MT5 broker
The deepest pitfall isn’t mechanical, it’s structural. A copier that only watches can’t stop anything. If your master over-sizes or a symbol maps wrong, a client-side copier faithfully forwards the mistake to every account before you can react — and on a fleet of prop accounts, that’s several breaches in seconds.
The durable fix is to enforce limits at the broker, not in a script you’re hoping stays running. When the risk check lives on the broker side, an oversized or out-of-rule order is refused at the source, on each account independently, whether or not your terminal is open.
That’s the model Shibiki is built on: it copies one strategy across your MT5 prop accounts, auto-journals every fill on every account into a single record — correctly de-duplicating one decision copied many times so your sample size stays honest — and computes live edge health with a Wilson confidence interval on those de-duplicated trades. Crucially, it pushes hard risk limits enforced at the broker per account, so a suffix mismatch, a rounding surprise, or a fat-fingered master can’t cascade into a fleet-wide breach while you’re looking at one chart. Map your symbols, tame your lots, and let the broker hold the line.
Related: MT5 integration · Lot size calculator · FTMO