An MT4 to MT5 migration for brokers moves client accounts, balances, history, groups, symbols and integrations from a MetaTrader 4 server to MetaTrader 5, usually over a planned weekend cutover. The business side decides account types (hedging or netting), trading conditions, the cutover model, client and IB communication, and how Expert Advisors are handled. MetaQuotes no longer sells MT4 licences.
Why are brokers migrating from MT4 to MT5 in 2026?
Brokers are migrating because MT4 has no future capacity: MetaQuotes says “The MetaTrader 4 trading platform licenses are no longer available for purchase”, and it focuses development on MetaTrader 5. When MetaQuotes stopped selling MT4 to new clients in January 2018, Finance Magnates reported that existing brokers “will not be able to expand their operations on the platform, as no new servers will be issued in any capacity.” Existing MT4 licensees kept support and, according to the same report, MetaQuotes addressed the continuation of security updates and bug fixes.
So MT4 still runs, but it cannot grow. A broker that wants another server, a new entity or multi-asset products such as exchange-traded instruments has to plan for MT5. Each extra year on two platforms means two sets of licences, duplicated integrations and staff time spent supporting both.
This page covers the business plan for a migration. The step-by-step technical list for your IT team is on our separate MT4 to MT5 migration checklist, and our MT4 vs MT5 white label guide compares the platforms for brokers who are not yet decided.
“The MetaTrader 4 trading platform licenses are no longer available for purchase.”
What changes for the broker’s business when you move to MT5?
Moving to MT5 changes your account model, product range, integrations and reporting, not just the server. Most of these changes are opportunities, but each one is a decision someone in the business must make before the technical team can configure anything.
| Area | On MT4 | On MT5 | Decision for the business |
|---|---|---|---|
| Position accounting | One model: multiple positions per symbol | Hedging (MT4-like) or netting, chosen per account group | Which groups get hedging, which netting |
| Products | Mainly forex and CFDs | Multi-asset, including exchange instruments where your licence and liquidity allow | Whether to add products at the same time or later |
| Order types and execution | Familiar MT4 set | Adds stop limit orders and fills through multiple deals | Update contract specifications and client guides |
| Integrations | MT4 Manager API, bridges, CRM plug-ins | MT5 Manager API, Web API, gateways and new bridge connections | Which vendors must re-certify, at what cost |
| Automated trading | MQL4 Expert Advisors and indicators | MQL5; MQL4 programs need conversion | Whether you support conversion for clients |
| Reports and statements | MT4 report formats | MT5 report formats and history structure | What finance, compliance and IBs need to see |
What migrates from MT4 to MT5, and what does not?
Accounts, balances, credit, closed trade history and group and symbol settings can be migrated with the right tools; passwords, client-installed Expert Advisors and some integrations cannot simply be copied. Open positions and pending orders can be moved, but many brokers ask clients to close them or move them under controlled conditions to avoid disputes. The table gives the business view; your technical team will work from the migration checklist.
| Item | How it usually moves | Business decision |
|---|---|---|
| Client accounts and balances | Migrated by tool or script | New account numbers or kept where possible |
| Credit and bonuses | Migrated with rules | Whether to carry over, convert or close |
| Closed trade history | Migrated or archived and available on request | How much history clients and regulators need online |
| Open positions | Migrated at the cutover price, or closed by clients beforehand | Policy for prices, swaps and complaints |
| Pending orders | Recreated or cancelled | Whether clients must re-place them |
| Passwords | Usually not migrated; clients receive new MT5 credentials | How credentials are delivered securely |
| Expert Advisors and custom indicators | Not compatible; need MQL5 versions | Whether you offer help or only notice |
| IB structure and commissions | Rebuilt in the CRM and linked to new accounts | Check every IB’s payout before and after |
Hedging or netting: which account type should migrated clients get?
Migrated forex clients should normally get hedging accounts, because hedging mode on MT5 behaves like MT4 and keeps multiple positions in the same symbol, including opposite ones. MetaQuotes introduced the hedging system in March 2016 for exactly this reason, noting that it would be familiar to MT4 traders. Netting accounts merge all deals in a symbol into one position, which suits exchange instruments but surprises an MT4 client who opens a second trade and sees the first one change.
You can still offer netting for new products, such as exchange-traded instruments, in separate groups. Decide the default for each group before configuration, write it into account type descriptions, and make sure your copy trading, PAMM and bridge settings use the same mode as the accounts they serve.
“Since the new system is similar to the one used in MetaTrader 4, it will be familiar to traders.”
Who should own the decisions in an MT4 to MT5 migration?
A migration needs one accountable owner on the broker side, usually the COO or head of operations, and named decision-makers for dealing, finance, compliance, support and partners. When nobody owns trading conditions or IB rules, the technical team waits, and the cutover weekend slips.
Migration owner
Signs off the plan, the cutover date and the go or no-go decision; chairs the daily call in the final week.
Dealing and risk
Approves groups, symbols, leverage, swaps and routing on MT5, and the handling of open positions at cutover.
Finance
Reconciles balances, credit and IB commissions before and after; approves any one-off adjustments.
Compliance
Approves client notices, new account terms and any change in disclosures or risk warnings.
Support and partners
Prepares scripts and FAQs, briefs IBs and staffs the help desk for the first days after cutover.
Technology provider
Builds MT5, migrates data, reconnects integrations, runs rehearsals and the cutover itself.
How should you plan the migration timeline?
Plan the migration as a sequence of audit, build, rehearsal, communication and a single cutover weekend, then a short stabilisation period before MT4 is switched off. The length depends on the number of accounts, groups and integrations, and above all on how quickly the business decisions above are made. We give a dated plan after the audit rather than a generic figure.
Real migrations follow this pattern. Earn, a broker that moved its MT4 accounts to MT5 in 2025, scheduled two separate weekends, 20–21 and 27–28 September 2025, one per MT4 server, with each server temporarily unavailable during its window.
- AuditList every group, symbol, account type, plug-in, bridge, report and integration on MT4, plus balances, credit and IB structures.
- DecideAccount types, trading conditions, cutover model, open-position policy, EA support and client communication plan.
- Build MT5Configure groups and symbols, connect liquidity, CRM, payments and front ends to MT5, and recertify third-party tools.
- RehearseRun at least one full trial migration on copied data and reconcile every balance and IB figure against MT4.
- CommunicateSend client and IB notices, publish FAQs and guides, and brief support well before the cutover.
- Cut overFreeze MT4 trading at the agreed time, migrate, reconcile, test, and open MT5 before the market opens.
- Stabilise and closeKeep MT4 read-only for statements for an agreed period, handle tickets, then decommission.
Should you cut over in one weekend, by group, or run MT4 and MT5 in parallel?
Most brokers are best served by a single planned cutover, or a small number of cutovers by server or group, rather than a long parallel run. Parallel running sounds safer but doubles licence costs, splits liquidity and support, and lets clients delay indefinitely. A phased move by server, as Earn did, keeps each weekend manageable.
One-weekend cutover
Everyone moves at once. Clean and fast, but the rehearsal must be good and support must be ready for a busy Monday.
Phased by server or group
Each server or group moves on its own weekend. Lower risk per step, longer overall, some temporary dual running.
Opt-in parallel run
Clients choose when to move within a window. Gentle for clients, expensive and slow for the broker; set a hard end date.
How should you tell clients and introducing brokers about the migration?
Tell clients and introducing brokers early, in plain language, with the dates, what they need to do and what will not change. A good notice covers when the old server will be unavailable, how new login details arrive, what happens to open positions, pending orders and history, whether trading conditions change, and what to do about Expert Advisors.
Earn’s notice is a useful real example: it told clients that open positions, balances and history would be transferred, that “You do not need to take any steps to complete the migration”, and that MT4 Expert Advisors would need adapting. Send at least two notices, one well ahead and one shortly before the weekend, plus a confirmation once MT5 is open. Brief IBs separately with their own dates and a check of their commission set-up, because they will answer many client questions for you.
“MT4 EAs are not compatible with MT5.”
What happens to clients’ Expert Advisors and indicators?
Clients’ Expert Advisors and custom indicators written in MQL4 will not run on MT5 and need to be converted or rewritten in MQL5. MetaQuotes’ own MQL5 documentation states that existing MQL4 indicators and strategies “should be converted to MQL5” to be used in MetaTrader 5. Conversion is not automatic because MT5 uses a different trading model and indicator handling.
Decide your policy before you announce the migration. Some brokers only inform clients and point them to the MQL5 marketplace and freelancers; others help their largest algorithmic clients or IBs convert key tools. Either way, say it clearly in the notice and do not imply compatibility.
How do liquidity, CRM and payments move to MT5?
Liquidity, CRM and payments move by reconnecting each system to the new MT5 server and re-testing the full client flow, from registration and deposit to trade, withdrawal and IB payout. Bridges and gateways need MT5 versions and new routing rules; the CRM needs to create MT5 accounts and sync balances through the MT5 Manager API; and payment flows must credit the right MT5 accounts.
This is often the moment to fix what never worked well on MT4. Our liquidity integration page covers bridges and routing, the broker CRM page shows how account sync and IB commissions work on MT5, and the MT5 Manager API guide explains the interface most integrations use. Front ends move too: a branded WebTrader and apps connected to MT5 give clients a consistent experience from day one.
How much does an MT4 to MT5 migration cost?
Migration cost depends on the number of accounts, servers and integrations, on how many third-party tools must be re-certified for MT5, and on whether you are moving to your own MT5 licence or into a provider’s environment. Very few vendors publish a figure, and the ones that do usually price a single tool rather than the whole project, so a published number tells you little about your own budget. We do not publish prices on this site either: message us with your server count and integrations and we will send current figures for your set-up.
If you are moving to your own MT5 licence, the platform fee comes from MetaQuotes, not from us. In the applications we handle, MetaQuotes charges a monthly fee that depends on the tier chosen (Entry, Standard or Enterprise), and when the Entry tier is chosen it asks for three months to be paid upfront. MetaQuotes’ order page lists the capacities as 1,000 real accounts for Entry, 25,000 for Standard and 200,000 for Enterprise, which matters for a migration: count your active MT4 accounts before you pick a tier. MetaQuotes does not publish its prices, so ask us for the figures we are currently seeing.
Budget also for the less visible items: re-certification of bridges and plug-ins, a period of overlapping licences while MT4 stays read-only, extra support staff around cutover and any EA conversion help you offer. If you already have a migration quote, send it to us on WhatsApp and we will tell you what it leaves out.
| Cost driver | Why it matters | What to ask the provider |
|---|---|---|
| Number of servers and groups | Each server is usually its own cutover, and each group needs MT5 settings | Is the quote per server, per group or for the whole project? |
| Accounts and history volume | More accounts mean longer rehearsals and reconciliation | How many trial migrations are included? |
| Integrations to reconnect | Bridges, CRM, payments and reporting all need MT5 versions | Which integrations are in scope, and which are your vendors’ cost? |
| Target environment | Own MT5 licence, white label or grey label change who pays the platform fee | Is the platform fee in the quote or billed separately? |
| Overlap period | MT4 often stays read-only for statements after cutover | How long is the overlap, and who bears its licence cost? |
| Client support around cutover | The first trading days generate the most tickets | Is cutover-weekend and Monday support included? |
| EA conversion policy | Helping clients convert MQL4 tools takes developer time | Is any conversion help included, or quoted per tool? |
What should a migration quote include?
A complete migration quote names every system that moves, every rehearsal, the cutover itself and the support afterwards, and it says clearly which costs belong to third parties. Most disagreements we see after a migration come from quotes that priced the data transfer and left the rest to “to be agreed”.
Compare quotes line by line rather than by the bottom figure. One provider may include two rehearsals and cutover support; another may include one rehearsal and bill support by the hour. Ask each provider to fill in the same list, and treat any blank line as a cost you will pay later.
- Audit of the MT4 set-up: groups, symbols, plug-ins, reports and integrations.
- MT5 configuration: groups, symbols, trading conditions, hedging or netting per group.
- Data migration method for accounts, balances, credit and history, with the number of trial runs.
- Reconnection of liquidity, CRM, payments and front ends, and who pays third-party vendors.
- Cutover weekend staffing, the go or no-go point and the rollback plan.
- Post-cutover support period and how tickets are handled.
- Whether the MetaQuotes or provider platform fee is included or billed separately.
- Decommissioning of MT4 and how long statements stay available.
What are the business risks of a migration, and how do you contain them?
The main business risks are balance or commission errors, clients unable to log in on Monday, disputes over open positions, and an IB network that feels ignored. Each can be contained with preparation rather than technology.
- Reconcile every balance, credit and IB figure between MT4 and MT5 in rehearsal and again at cutover, with finance signing off.
- Set a written go or no-go point on the cutover weekend and a rollback plan that reopens MT4 if reconciliation fails.
- Freeze changes to groups, symbols and IB rules in the weeks before cutover.
- Publish the open-position policy in advance and log every position moved, with prices and swaps.
- Staff support and IB managers heavily for the first trading days and track ticket volume hourly.
- Keep MT4 statements available, read-only, for the period your compliance team requires.
How does FXUP run an MT4 to MT5 migration?
We run the technical side and support the business decisions: audit of your MT4 set-up, MT5 configuration on your own server, an MT5 white label or an MT5 grey label, data migration, reconnection of liquidity, CRM and payments, rehearsals and the cutover itself. If you do not yet have MT5, the MT5 licence guide explains the direct route; as a consulting firm we also handle the MetaQuotes requirements and application for clients, for a fee. For the CRM, we have our own and also work with partner CRMs, and we propose whichever fits your IB structure and integrations. FXUP is an independent firm and is not affiliated with MetaQuotes.
After the audit you receive a written plan with dates, owners and the decisions we need from you, linked to the item-level migration checklist. Clients can test the new front end in advance on the WebTrader demo and the mobile app demo, which run on a real MT5 demo environment.
Questions buyers ask
Is MetaQuotes discontinuing MT4?
Can MT4 accounts and history be transferred to MT5?
Do client passwords migrate?
What happens to open positions during migration?
Do MT4 Expert Advisors work on MT5?
Does MT5 support hedging like MT4?
How long does a broker migration take?
Can I run MT4 and MT5 in parallel?
How much does migration cost?
Where is the technical checklist?
Not covered here? Ask us on WhatsApp, message @FXUPCK on Telegram or write to [email protected].
Sources
- MetaQuotes — MetaTrader 4 platform for brokers (accessed October 2026)
- Finance Magnates — MetaQuotes will no longer offer MT4 trading platform (12 January 2018) (accessed October 2026)
- MQL5.com — MetaTrader 5 features hedging position accounting system (accessed October 2026)
- MetaQuotes — Buy MetaTrader 5 platform licence (accessed October 2026)
- MQL5.com — Migrating from MQL4 to MQL5 (accessed October 2026)
- Earn — Important notice: migration of MT4 accounts to MT5 (accessed October 2026)
FXUP is an independent consulting and technology firm and is not affiliated with MetaQuotes Ltd. MetaTrader 4 and MetaTrader 5 are trademarks of MetaQuotes Ltd. This page is general information, not legal, tax or investment advice; regulatory requirements depend on the jurisdiction and change over time. FXUP does not publish prices; contact us for current figures for your setup.