How to Map Mini Contracts to Micro Contracts Across 20 Prop Accounts in NinjaTrader

Cross-instrument copying is where the trade copier goes from "useful" to "operationally essential." The leader trades 1 NQ contract — the full-size E-mini Nasdaq. But some follower accounts are $25K funded accounts where 1 NQ represents 67% of the drawdown cushion at $1,500 risk per contract on an 8-tick stop. Those accounts need MNQ. Other follower accounts are $100K funded accounts where 1 NQ is appropriate. Some might need ES instead of NQ for a specific firm's instrument restrictions.

Managing that complexity manually — mentally converting the leader's NQ trade to the right instrument and size for each follower at the moment of entry — doesn't work at 20 accounts. The copier handles it, if it's configured correctly.

The Tick Value Foundation

Every correct cross-instrument ratio calculation starts here. You can't map instruments without knowing their tick values:

The NQ:MNQ ratio is exactly 10:1. 1 NQ = 10 MNQ in dollar terms. 1 ES = 10 MES. These are fixed relationships — they don't change. Every cross-instrument calculation involving these pairs starts from this 10:1 base.

Pure Instrument Substitution (Same Size Class, Different Instrument)

If the leader trades 1 NQ and a follower needs to receive MNQ at the same dollar risk, the configuration is: instrument = MNQ, ratio = 10. The follower receives 10 MNQ for every 1 NQ the leader trades.

In Copilink's per-account configuration:

1. In the follower account settings, set "Instrument Override" to MNQ (if the account can't trade NQ, or you prefer MNQ for that account)
2. Set ratio to 10 (to maintain dollar equivalence with 1 NQ leader)
3. Verify the mapping in the account's configuration summary: "Leader: 1 NQ → Follower: 10 MNQ"

If the follower should trade at half the dollar risk of the leader (smaller account): ratio = 5. That follower receives 5 MNQ for every 1 NQ — exactly 0.5× the dollar risk. Quarter size: ratio = 2.5, which rounds to either 2 or 3 MNQ depending on rounding configuration.

Cross-Index Mapping (NQ to ES or ES to NQ)

Trading the leader in NQ but needing followers in ES is a different problem — the instruments have different tick values and don't share a clean 10:1 ratio. To map NQ→ES, you need to calculate the dollar-equivalent ratio:

NQ tick value: $5.00. ES tick value: $12.50.

To equalize dollar risk per tick: Leader 1 NQ ($5.00/tick) → Follower X ES ($12.50/tick per contract)

Solve: $5.00 = X × $12.50 → X = 0.4 ES contracts.

Since 0.4 ES contracts isn't a valid order, round to the nearest practical equivalent: 4 MES contracts (4 × $1.25/tick = $5.00/tick). Exact match.

Leader 1 NQ = Follower 4 MES for tick-value equivalence. The configuration: instrument = MES, ratio = 4.

This level of cross-index mapping is advanced — most multi-account traders stick to the same index across all accounts and vary only between the full contract and its micro equivalent. Cross-index mapping is worth the complexity for specific scenarios: a firm that doesn't allow NQ but allows ES, or a portfolio construction decision to diversify across indices.

The 20-Account Configuration Strategy

With 20 follower accounts, you don't want to configure each one completely independently — too many settings to maintain, too many things to accidentally misconfigure. The practical approach:

Create account groups by profile. Group accounts by: instrument (NQ, MNQ, ES, MES), ratio tier (full size, half size, quarter size), and firm (Apex, Topstep, Tradeify). Each group shares most configuration settings, varying only in the per-account risk parameters (daily loss limit dollar amounts, consistency threshold calculations).

Configuration template approach: Configure one account from each group type fully. Duplicate the configuration to other accounts in the same group. Adjust only the account-specific identifiers (account number, firm) and risk parameters (specific dollar thresholds that vary by account size).

Verification checklist before session start: Each day, verify the active configuration for a sample of accounts from each group. Full configuration audit monthly using the monthly operations checklist. The daily check catches configuration drift (a parameter accidentally changed, an account that was reconfigured and didn't get reverted). The monthly audit catches systemic issues.