MT5 Migration Checklist: move broker infrastructure with controlled risk.
An MT5 migration should be treated as a production change program, not a file copy. Inventory dependencies, define rollback conditions and validate pricing, execution and client access before cutover.
1. Inventory the current environment
Document server roles, access servers, groups, symbols, plugins, gateways, bridge routes, price feeds, CRM/API dependencies, DNS, certificates, monitoring and backup jobs.
2. Freeze and validate configuration
Record configuration baselines and ownership. Identify changes that must be synchronized during the migration window and define acceptance tests for quotes, orders, history and manager access.
3. Rehearse cutover and rollback
Test the target environment before production. Define DNS timing, client communication, rollback triggers, responsible engineers and a clear go/no-go checkpoint.
4. Monitor after migration
Watch latency, quote continuity, rejection rates, bridge connectivity, resource usage, access-server health and client login errors. Keep the old environment protected until acceptance is complete.