Begin with what must remain compatible
For an existing MT4 operation, list the tools, interfaces and client workflows that cannot be changed immediately. Include automated trading dependencies, reports, account groups, instrument naming and operating procedures. For a new MT5-oriented project, describe the intended markets, account model and integrations before choosing the final configuration.
The current rights and components available to your business must be confirmed in the specific platform arrangement. A public service page is not proof that a particular licence, brand option or administrative permission has been granted. Keep those details in the written scope for the selected environment.
Select a starting path
| Your starting point | Review first | Decision to resolve |
|---|---|---|
| Established MT4 workflows | MT4 White Label requirements | Which dependencies must stay and which can be replaced? |
| New MT5-oriented brokerage | MT5 White Label requirements | Which account, market and integration workflows must the first release support? |
| Change of platform | Staged migration design | What can move, what needs rebuilding and what must operate in parallel? |
| Existing dual-platform business | Parallel operation model | How are client identity, reporting and support coordinated? |
These are selection paths, not a promise that account data, positions or third-party integrations can be transferred automatically. Migration feasibility requires its own technical review.
Keep platform choice separate from the delivery package
A platform environment is one layer. Hosting, market data, execution connectivity, CRM and recovery can be included, supplied separately or operated by the brokerage. Once the platform path is selected, use the same responsibility schedule to compare implementation proposals.
- Identify the client-facing interfaces and branding included in the proposal.
- Confirm operational access for the brokerage and technical support team.
- List integrations by product and workflow, including known exclusions.
- Define the records and access needed for a future provider change.
Continue with a focused scope
Open MT4 White Label if your decision centres on MT4-specific workflows and compatibility. Open MT5 White Label for the MT5 project brief and platform scope. The MT4 versus MT5 comparison supports an unresolved platform decision.
After choosing a path, the implementation engagement can turn it into a delivery baseline, acceptance plan and handover pack. This keeps a platform-choice question distinct from the work needed to release the resulting service.