
Map what must move
Inventory accounts, balances, group settings, integrations and reporting dependencies. Reconcile a test export against the source and document any items that cannot be transferred directly.
Rehearse the cutover
Use a representative test environment. Measure export and import duration, verify access and integrations, and identify the point after which returning to the source requires reconciliation.
Define go/no-go decisions
Record the acceptance checks, decision owner, communication plan and rollback triggers. Do not replace a written cutover plan with an informal agreement to fix problems live.
Validate after the change
Compare account counts, balances, interface states and reports. Keep the old environment protected until the agreed validation and retention requirements are satisfied.
Example: new activity after the cutover
An illustrative rehearsal includes an account action after the destination becomes active. A rollback must identify and reconcile that new activity before the source can safely resume. Record the decision point and compare the relevant account and transaction totals. This is a planning example, not evidence of a completed client migration.
PRACTICAL CHECKLIST
Cutover decisions to write down
| Before the change | Required evidence |
|---|---|
| Source baseline | Account counts, balance totals, settings and integration inventory. |
| Rehearsal | Measured export/import time and reconciliation of a representative dataset. |
| Change window | Timezone, decision owner and communications for affected teams. |
| Rollback | Triggers, access, restoration steps and post-change reconciliation duties. |
| Go/no-go | Written acceptance checks and authority to pause the cutover. |
| Post-change review | Platform, CRM, provider and reporting records match the agreed baseline. |
Before signing off
- A rollback must account for any activity after the cutover begins.
- Keep the source environment protected until acceptance and retention requirements are met.
- Assign owners for open issues and the final handover.
CONTINUE PLANNING
MT4 Integration & Migration for Brokers
Plan MT4 integrations and migration around your existing accounts, workflows and contractual platform access.
View MT4 Integration & Migration for BrokersBroker Backup & Restore Testing Guide
Test broker backups in an isolated environment. Record recovery time, recovered-data age, balances, permissions and follow-up changes to the runbook.
View Broker Backup & Restore Testing GuideMT4, MT5 & CRM API Integration
Define MT4, MT5 and CRM API integration with account identifiers, permissions, duplicate protection, retry rules, reconciliation and version ownership.
View MT4, MT5 & CRM API Integration