How to Copy Trades Between Two Different Brokers
By the TradeAon team · Published · Updated · 7 min read
Copy trading is a powerful mechanism that allows traders to mirror the exact trades from one primary account to one or more secondary accounts automatically. While copying trades within the same broker is relatively straightforward, the real challenge and utility come from copying trades across two completely different brokers, or even different platforms like MetaTrader 4, MetaTrader 5, and cTrader. This guide explores the mechanics of cross-broker copy trading, explaining the master/slave concept, volume mapping, symbol resolution, and how to set up a robust system that syncs your trades seamlessly.
- A Master/Slave architecture defines the flow of trades: the master executes the strategy, while slave accounts replicate those actions in real-time.
- Copying across brokers requires sophisticated symbol mapping to account for differences in asset naming conventions (e.g., GOLD vs. XAUUSD).
- Volume mapping strategies—such as proportional, fixed lot, or multipliers—are critical to managing risk when account balances differ significantly.
- TradeAon synchronizes not just entries, but also Stop-Loss (SL), Take-Profit (TP), and partial closures across disparate platforms.
The Master/Slave Concept Explained
At the core of any copy trading system is the relationship between the master account (the sender) and the slave account (the receiver). The master account is where the trading strategy is natively executed. This execution can be driven by a human trader clicking buttons manually, a TradingView webhook triggering an entry based on chart indicators, or an algorithmic Expert Advisor (EA) running a complex quantitative strategy continuously.
The slave account, on the other hand, exists purely to listen for these execution events and replicate them in real-time. When a trade is opened on the master, the copy trading software instantly captures the details of that trade—symbol, direction, entry price, stop-loss, and take-profit—and transmits a matching order to the slave account. This architecture allows a single successful strategy to be distributed across multiple portfolios simultaneously without requiring the trader to log into multiple terminals.
Why Copy Across Different Brokers?
You might wonder why a trader would complicate their setup by using multiple brokers instead of keeping all funds under one roof. The reality is that different brokers offer drastically different trading conditions that cater to specific needs.
For example, one broker might offer exceptionally low spreads and near-zero commissions for major forex pairs like EURUSD, making it the ideal environment for a high-frequency scalping master account. However, that same broker might have terrible margin requirements for indices. Another broker might offer favorable conditions for trading gold or exotic pairs. By utilizing cross-broker copy trading, you can execute your primary strategy in the optimal environment while distributing the execution across other brokerage accounts to diversify broker risk.
Furthermore, bridging platforms like MT4, MT5, and cTrader breaks down the walled gardens of trading infrastructure. If your proprietary EA only runs on MT4, but you want to manage funds in a modern cTrader environment, cross-platform copy trading serves as the perfect bridge. This provides redundancy, avoids single points of failure, and opens up opportunities with proprietary trading firms that mandate specific platforms.
Navigating Symbol Remapping
One of the most persistent headaches in cross-broker trading is that brokers do not use a universal naming standard for financial instruments. For instance, the spot price of gold might be labeled as XAUUSD on your master broker, but your slave broker might list it as GOLD, XAUUSD.pro, XAUUSD.raw, or even XAU/USD.
If the copy trading system rigidly attempts to execute a trade on XAUUSD when the broker only recognizes GOLD, the trade will simply fail to execute, potentially leaving your portfolio unhedged or missing out on a major market move. This is where intelligent symbol remapping becomes essential.
TradeAon incorporates an automatic symbol mapping system designed to seamlessly translate these variants. The routing engine recognizes standard financial assets and maps them across the various broker suffixes (like .m, .pro, .raw) automatically. This means that when the master executes a trade on standard XAUUSD, the system dynamically translates the instruction to XAUUSD.pro for a slave account connected to a broker requiring that specific suffix, entirely behind the scenes.
Volume Mapping and Position Sizing
Arguably the most critical aspect of copying trades is determining how the trade size (lot size) is translated from the master to the slave. If the master account operates with a $100,000 balance and the slave has only $1,000, copying a standard 1.0 lot trade directly would instantly over-leverage the slave account, risking an immediate margin call.
To safely bridge accounts of different sizes, TradeAon supports multiple volume mapping modes:
- Proportional (Equity-Based): This mode scales the trade size based on the relative account balances. If the slave account is exactly 10% the size of the master, it will automatically take 10% of the volume. This maintains identical risk profiles across accounts.
- Fixed Lot: This forces the slave to always execute a specific, pre-defined size, regardless of the master's lot size. This is particularly useful when you want strict, uniform risk per trade, often utilized in prop firm challenges.
- Lot Multiplier: In this setup, the slave simply multiplies the master's lot size by a defined factor (e.g., 0.5x). A 2.0 lot trade on the master becomes a 1.0 lot trade on the slave.
Those descriptions are the shape of the idea; the useful part is what each one actually computes, because the same master trade produces very different slave sizes depending on which you pick. The table below runs one identical trade — the master opens 1.00 lot, the master account holds $100,000 and the slave holds $10,000 — through all five modes:
| Mode | What it keeps equal | What you set | Slave gets |
|---|---|---|---|
| Multiply (default) | The master’s lot size, scaled by a factor you choose. Risk stays proportional to the master, not to the slave account. | A multiplier, e.g. 1.0 | 1.00 lot |
| Fixed | Nothing — every copied trade is the same size no matter what the master did. | The lot size, e.g. 0.10 | 0.10 lot |
| Balance ratio | The percentage of the account at risk. This is what most people mean by “the same risk on both accounts”. | A multiplier, usually 1.0 | 0.10 lot 1.00 × ($10,000 ÷ $100,000) |
| Percent | Position size as a share of the slave balance. The master’s own size is ignored entirely. | A percentage, e.g. 10 | 1.00 lot |
| Dynamic equity | A fixed amount of equity backing each lot, so size grows and shrinks with the account. | Equity per lot, e.g. $5,000 | 2.00 lot $10,000 ÷ $5,000 |
Three details matter more than the arithmetic. Fixed mode and partial closes fight each other — if every copy is 0.10 lot regardless of the master, there is no meaningful way to mirror “the master closed 40% of its position”. The three balance-aware modes need a balance to work from, and when the slave account has not reported one yet the copy falls back to the broker minimum of 0.01 lot instead of copying the master’s raw size — a deliberately timid failure, because the alternative is a small account taking a large account’s position. And every computed size is clamped to between 0.01 and 100 lots, so a percentage typed with an extra zero is capped rather than sent to your broker as-is.
Syncing Stop-Loss, Take-Profit, and Partial Closes
Opening a position is only the beginning of a trade's lifecycle; managing the exit is equally critical. In cross-broker copy trading, Stop-Loss (SL) and Take-Profit (TP) levels must be synchronized perfectly to ensure the slave account mirrors the master's risk management accurately.
When the master account modifies a stop-loss to break even or trails it behind price action, the slave account must immediately reflect that change. Furthermore, partial closures—such as closing half the position to secure initial profits—are notoriously difficult to synchronize across different platforms due to how MetaTrader handles order tickets.
TradeAon keeps partial closes proportional: if the master closes exactly 50% of its volume, the slave closes 50% of its proportionally mapped volume, keeping the risk exposures aligned across both platforms.
Step-by-Step Setup Guide
Setting up a cross-broker copy trading environment requires precision, but the process is straightforward once you understand the architecture. Here is how to configure it effectively using TradeAon:
- Register Both Accounts: First, you need to connect both the master and slave accounts to the automation service. Within your TradeAon dashboard, you will generate a license key (starting with
whk_). You must paste this key into the EA running on both the master's MetaTrader terminal and the slave's MetaTrader terminal. A cTrader account is connected a different way: you authorise it once through cTrader's OAuth flow in the dashboard, and there is no key to paste and no terminal to keep running. - Create a Copy Pair: In the TradeAon dashboard, navigate to the copy trading section. Here, you will designate which account acts as the master and which acts as the slave. The Starter plan allows 2 copy pairs, and each extra pair is an add-on, so one master can fan out to several slave accounts at once.
- Configure Volume Mapping: Select your preferred volume mapping strategy—Fixed Lot, Proportional, or Multiplier. Carefully set these parameters based on the slave's account equity and the maximum leverage allowed by the receiving broker.
- Test the Connection: Always verify the connection before deploying significant capital. Execute a micro trade (e.g., 0.01 lot) on the master account and confirm that it appears correctly on the slave account. Verify that the symbol, volume, SL, and TP have all mapped correctly.
Latency Expectations and Pitfalls
In automated trading, milliseconds can make the difference between a profitable execution and a losing one. Cross-broker copying naturally introduces network latency into the equation. The master executes the trade, the broker confirms it, the EA sends a payload to the TradeAon server, the server processes and routes it, and finally, the slave EA executes it on the second broker.
While this entire process typically happens in sub-second timeframes, it is heavily dependent on the physical location of your VPS relative to the broker's trade servers. High latency can lead to slippage, where the slave account receives a worse entry price than the master due to market movement during the delay.
To minimize latency and slippage, it is highly recommended to host your MetaTrader terminals on a Virtual Private Server (VPS) located in the same data center region (such as London or New York) as your broker's execution servers. Avoiding overloaded consumer-grade internet connections is key to maintaining a robust automation pipeline.