From MT5 Grey Label to White Label: What Moving Up Costs and How to Budget for It
Many buyers start on a grey label and plan to move up. Few budget the move. This guide lists the cost lines of a migration so the upgrade does not surprise you.
Decide whether you need to move
Moving up costs money and attention, so check that the trigger is real: limits reached, access you cannot get or integrations you cannot add. Compare options in white label versus grey label.
The cost lines
- The white label setup itself.
- Migration work for accounts, balances and history.
- Re-connecting CRM, payment and liquidity integrations.
- Testing and parallel running of both environments.
- Client communication and extra support.
- Staff training on new tools.
Price these before you commit.
Ask the new provider what they will do
Ask whether they will migrate data, how they handle balances and positions, and what responsibility they take if something goes wrong. Make sure the plan includes a rollback route.
Check your exit from the grey label
Read your current agreement for notice periods, data export and overlap. A badly timed exit can mean paying twice or losing access early.
Build a migration budget
Total the cost lines, add a contingency and compare with the benefit you expect. For the platform costs themselves, see the white label cost breakdown.
Negotiate the move early
If you expect to upgrade, ask your current provider and prospective providers about migration support before you sign anything. Some will include assistance or discounts; others will charge separately.
Knowing this early shapes your choice of both platforms, and it keeps the upgrade from becoming a surprise bill.
A migration budget table
A migration has its own budget. Build it before you decide.
| Line | Source | Estimate | Notes |
|---|---|---|---|
| New platform setup | New provider | ||
| Integration rebuild | Vendors | ||
| Data export and import | Both providers | ||
| Reconciliation | You and provider | ||
| Parallel running | Both providers | ||
| Client communication | You | ||
| Contingency |
Add the cost of your own staff time. It is often the largest hidden line.
A worked example of timing the conversation
A buyer who plans to move in a year starts talking to potential white label providers early. Early conversations produce better prices, more patience and time to run a pilot. The buyer also reads the current contract and finds a notice period that would have caused trouble if ignored.
Starting early turned the migration into a project instead of an emergency.
Questions for the new provider
- What will you do, and what will I need to do?
- How do you move accounts, balances and history?
- What is the timeline and what does it depend on?
- What is the cost, and what could change it?
- What happens if a check fails?
Get the answers in writing and compare providers using the same questions.
Check the exit from the grey label
Read the current contract for notice periods, fees and data export rights. Ask the current provider for a transition plan. Negotiating a smooth exit is easier while the relationship is still good. See our migration quote guide.
The value of a pilot environment
If possible, ask the new provider for a pilot environment where you can test configuration, integrations and reports before the real move. A pilot costs a little and finds many issues. Ask whether pilot time is included in the price.
Use the pilot to rehearse reconciliation with a copy of your data. A rehearsal is the best way to find out how long the real move will take.
Pricing contingencies
Ask the new provider to state a contingency for the migration, both in time and in cost. A provider who gives none is either very confident or has not thought about problems. A modest contingency, clearly explained, is more credible.
Keeping clients informed
Budget for the communication work: emails, notices, a FAQ and extra support during the move. Plan messages in advance and test them. Clients forgive planned maintenance and are less forgiving of surprises.
Choosing the new provider with migration in mind
When you compare white label providers, add migration questions to your list. Ask how many migrations from grey labels they have done, what data they can import, how long it typically takes and what went wrong in past projects. Ask for a reference who has moved from a grey label to them.
A provider with migration experience can foresee problems and will price the work more realistically. A provider with none may be learning at your expense.
Timing and risk
Choose a cut-over time that minimises risk: a quiet period, outside major market events and with your team available. Allow a freeze period before the cut-over during which you avoid changes. Prepare a rollback plan in case checks fail.
Ask the new provider how it would handle a failed cut-over. A calm, specific answer suggests experience.
A decision memo for the move
Write a short memo for your partners that covers why you are considering a migration, the options you compared, the cost and timeline of each, the risks and your recommendation. Include what you would do if you did nothing for another year.
Partners are more willing to support a migration when they see that the alternatives were considered and that the plan includes checks and contingencies. The memo also helps you stay focused when providers push you towards a quick decision.
Frequently asked questions
How much does migrating cost?
It depends on volumes and complexity. Build a budget with the rows above and add contingency.
When should I start planning?
As soon as limits or control become constraints, well before you reach them.
Will clients be affected?
Possibly. Plan communication and support.
Can I negotiate the move?
Yes. Ask both providers about support and fees.