Separate a client from the accounts they use
Keep a stable client identity in the business systems and distinct references for each trading account. Do not assume that the same visible account number or instrument name identifies the same object across environments. Record the platform, server context and account reference wherever a workflow needs that distinction.
Define which services are shared and which remain platform-specific. A shared CRM may coordinate client operations while separate connectors, configuration schedules and support procedures serve the two environments. The actual integration permissions must support the proposed division.
Use a cross-platform operations map
| Process | Shared concern | Platform-specific check |
|---|---|---|
| Client onboarding | Approved client identity and communication | Correct platform and account configuration |
| Support | One case reference and ownership route | Account context and platform-specific investigation |
| Reporting | Consistent business definitions | Source records and reconciliation for each environment |
| Configuration change | A coordinated approval process | Separate implementation and validation evidence |
The matrix does not imply automatic balance, position or history synchronisation. Any workflow that changes financial or trading state requires its own supported method, authority and reconciliation design.
Exercise confusing cases deliberately
- A client has one account on each platform and contacts support without naming it.
- A CRM action reaches one environment while the other is unavailable.
- A symbol is renamed in one platform but remains unchanged in the other.
- A report combines records whose meanings or timing conventions differ.
Resolve these cases before launch. The goal is to prevent an operator or integration from selecting the wrong account merely because two records look familiar. Include platform context in the tools staff actually use.
Keep change and migration decisions explicit
If coexistence is temporary, document what must be true before either environment is retired. If it is an ongoing service, plan maintenance, monitoring and recovery for both. A successful test on one platform does not establish readiness on the other.
Review the MT4 White Label and MT5 White Label scopes separately, then define the shared operating layer. The handover should contain a client/account map, connector inventory and clear escalation ownership for each platform.