Set Up a Trade Copier for Multiple Prop Firm Accounts
A multi-account trade copier needs more than connected terminals. First establish which source may send which instructions to each receiver. Then calculate the receiver’s exposure and prove how the software handles acknowledgements, errors and reconnection. Copying an order does not guarantee the same fill, result or programme permission.
1. Record the permitted account topology
For every connection, record the account owner, firm, programme and phase, platform, source account, receiver account, software version, and dated permission. Keep the actual account identifiers privately. A copier licence or technical connection does not authorize a prohibited source, account manager or strategy.
Checked 16 October 2026: FTMO applies allocation limits per trader or strategy, including substantially similar copied trading; extra registrations do not bypass them. FundedNext’s general rule limits permitted VPS copying to the trader’s own Challenge Accounts and excludes external cloud copiers. Its Instant-specific FAQ allows own Instant-to-Instant copying, while the general page also contains broader funded-account wording. Resolve that official inconsistency for the exact product before connecting it. Neither source permits copying across different owners.
The5ers’ terms, sections 10 and 11, restrict copying and require prior written approval for user-owned or user-developed automation; third-party-owned or developed software is prohibited. FXIFY’s copy policy distinguishes direction and programme, excludes several products and requires approval for an external source. Do not infer blanket approval from “EAs allowed”.
2. Choose the runtime and map the contract
A local-terminal copier needs its required terminals and connection running on a suitable PC or VPS. A provider-hosted copier has different dependencies and must itself be permitted. Neither architecture guarantees uptime or a fixed execution speed. Confirm the exact MT4/MT5 bridge, broker build and netting/hedging behaviour in the vendor documentation. Do not assume cross-platform support from the product category.
Map symbol suffixes to the actual instrument, not just a similar name. Check contract size, profit currency, tick size, minimum volume, volume step, allowed orders and stop distances. Establish which source identifier the copier uses to filter manual and EA orders. A magic number is not a universal cross-platform connection protocol. Prevent the same strategy being executed both directly and through the copier, and prevent receiver-to-source loops.
3. Calculate each receiver’s cash risk
Fictional example: both accounts are USD, with the same EURUSD contract and executable stop distance. A source with current equity of $100,000 uses 0.10 lots. An equity-ratio multiplier for a receiver with current equity of $50,000 gives 0.05 lots. That preserves the planned risk percentage only when the cash loss per lot, stop, currency conversion and costs are equivalent. Margin availability alone does not establish affordable risk.
Instead, start with each receiver’s cash budget and current daily/total loss headroom. Estimate loss at the proposed entry and stop in its account currency; MetaQuotes’ OrderCalcProfit describes this estimate for MT5. Reserve costs and adverse execution separately. Round volume down to the permitted grid. If the resulting volume is below the minimum, skip the instruction rather than silently increasing risk. A stop request cannot cap every gap loss.
4. Run an acceptance worksheet
Use permitted demo or test accounts first, with the relevant platform and contract specifications. Passing these cases is evidence about that tested configuration, not approval for another account.
| Case | Record on every receiver |
|---|---|
| Open and amend | Source event, receiver acknowledgement, volume, actual fill, accepted SL/TP. |
| Partial and full close | Actual remaining volume, rounding and final position state. |
| Rejected order | Return code, reason and whether retry can create a duplicate. |
| Lost connection and restart | Existing-position reconciliation, missed exits and stale-entry policy. |
| Risk or programme block | Which new actions stop and how existing exposure is handled. |
Keep requested and filled prices separately. A latency observation is not a pip-loss formula. Test whether protective orders are accepted by the receiver; a source-side stop does not prove receiver-side protection. Do not replay old entries automatically after reconnection. Reconcile actual positions before resuming.
5. Keep access, rules and product roles explicit
Follow the vendor’s least-privilege instructions. Do not enable DLL imports or share trading credentials merely because a generic guide says to. Read-only access cannot place receiver orders. Never rotate IPs, randomize order timing or alter identifiers to disguise prohibited copying. Use accurate records and the firm’s stated network policy.
The EA Hub contains customer-operated MetaTrader software; it is not proof that a copier bridge, risk monitor or news filter is included in every file. Only the separate JPTC Algo service is hosted by JPTC. The company-published broker-statement figures do not validate this copier setup or establish a challenge-pass rate. Recheck the configuration and written programme rules whenever software, account phase or provider changes.
Do I need a VPS?
Does proportional lot sizing preserve account risk?
What happens if a receiver misses an exit?
Can changing IPs or entry times make copying permitted?
Does a successful demo test prove compliance?
Review the JPTC EA Hub
EA software with version-specific documentation and account-level risk controls. Review the selected programme’s current automation rules and test the chosen version; software does not guarantee compliance, a pass or a payout.
See the EA Hub