Treat migration as a business change
A platform migration affects dealers, support, clients, reporting, integrations and finance. Create one inventory that covers account groups, symbols, contract specifications, trading sessions, commissions, swaps, margin rules, bridge mappings, plugins and downstream APIs.
Rehearse with representative accounts
A useful rehearsal uses real configuration complexity: different leverage tiers, account currencies, symbol suffixes, hedging and netting behavior where relevant, pending orders, open positions, and clients across time zones. Compare source and destination records using a signed reconciliation report.
- Freeze and export configuration versions
- Validate symbols, digits, lot sizes and margin rules
- Reconcile balances, equity, positions and pending orders
- Verify CRM, KYC, payment and reporting connections
- Agree a cutover window and client communications
- Prepare rollback criteria and decision owners
Make acceptance measurable
Define pass/fail conditions before the rehearsal: no unexplained financial differences, tested support workflows, observed market-data quality, validated execution routes, and successful operational handover. “Looks correct” is not a migration control.
A calm go-live usually comes from a disciplined rehearsal, not from trying to eliminate every issue during the cutover itself.
