MT4 to MT5 Migration for Brokers: Phases, Cutover and Rollback
A practical playbook for moving a brokerage from MetaTrader 4 to MetaTrader 5 without losing accounts, positions or clients, and a short answer for traders whose broker is retiring MT4.
MT4 to MT5 migration for brokers: phases, what migrates, hedging groups, plugin rewrites, client notices, cutover weekend and rollback. Plus help for traders.
Why brokers are moving from MT4 to MT5 now
Brokers are migrating because MetaQuotes no longer sells MT4 licences and puts its development into MT5. Brokers are also starting to set fixed end dates for MT4. The developer says so directly on its broker page:
“The MetaTrader 4 trading platform licenses are no longer available for purchase. We focus our efforts on the development of MetaTrader 5, and further conceptual updates will only be released for this multi-asset platform.”— MetaQuotes, MetaTrader 4 for brokers (accessed October 2026)
The second driver is operational. In March 2026 OANDA Japan announced that it would end MT4 at the close of trading on Friday 27 November 2026. It cited tighter cybersecurity standards and said MT4 is no longer covered by MetaQuotes system maintenance. Earlier, Earn moved its MT4 Standard and MT4 NDD servers to MT5 over two weekends in September 2025. A planned migration costs much less than a forced one. TakeProfit Tech describes a broker that lost MT4 access in October 2022 and had three working days and one weekend to move accounts, history and MAM data.
MT5 also removes several hard limits of an MT4 server. The table below uses MetaQuotes' own broker comparison.
| Item | MetaTrader 5 | MetaTrader 4 | Why it matters when you migrate |
|---|---|---|---|
| Account groups | Unlimited | 512 | You can split groups by book, region or IB instead of merging them |
| Security groups | Unlimited | 32 | Cleaner symbol permissions per product line |
| Symbols | Unlimited | 1,024 | Room to add stocks, futures or CFDs after go-live |
| Orders database | Unlimited | Up to 10M orders | Long histories no longer need archiving to stay under the cap |
| Position accounting | Netting and hedging | Hedging only | You must choose the mode per group (see below) |
| Balance operation types | Balance, Credit, Correction, Charge, Bonus, Commission, Agent, Interest | Balance, Credit | Bonus, rebate and fee flows need remapping in the CRM |
| Manager API | C++, ASP.Net, PHP | C++ | Back-office integrations have to be rebuilt against the MT5 API |
What migrates from MT4 to MT5 and what has to be rebuilt
Data such as accounts, balances, open positions and closed trade history can be moved with migration tooling. Code such as server plugins, Manager API applications, EAs and indicators cannot be moved. It has to be rewritten. Configuration sits in between: you recreate it on MT5 and then check it line by line against MT4.
| MT4 item | How it reaches MT5 | Check before go-live |
|---|---|---|
| Client accounts (login, name, group, leverage) | Exported from MT4 and imported with a migration script or tool | Login numbering policy, group mapping, leverage, read-only flags |
| Balances and credit | Imported as balance and credit operations | Totals reconcile to the cent per account and per group |
| Open positions and pending orders | Re-created at the MT4 close price at cutover, or closed and reopened by agreement | Open price, volume, SL/TP, swaps carried, margin after import |
| Closed trade history | Imported as deals, or kept as an MT4 archive with statements | What clients see in MT5 history; what you keep for audits |
| Groups and symbols | Rebuilt on MT5 (different structure and settings) | Contract size, margin, swaps, sessions, commission per group |
| Server plugins | Rewritten for the MT5 Server API | Same business rules, tested on a demo server |
| Bridge / liquidity connection | MT5 gateway from your bridge vendor | Routing rules, A/B-book split, markups, failover |
| CRM, IB and reporting links | Reconnected through the MT5 Manager or Web API | Deposits, withdrawals, IB rebates, reports |
| Client EAs and indicators | Ported from MQL4 to MQL5 by the owner | Clients told early; no promise of compatibility |
The last row needs a clear line in your client notices. MQL4 and MQL5 are not compatible, so MT4 EAs and indicators do not run on MT5. MetaQuotes' own migration article warns that trading functions cannot simply be converted:
“in MQL5 the concept is different … It's possible to convert them, but the trading logic should be changed.”— MQL5.com, Migrating from MQL4 to MQL5 (accessed October 2026)
Hedging or netting: choosing the account mode for migrated clients
Put migrated MT4 forex clients on MT5 hedging accounts unless you have a clear reason not to. MT4 only supports hedging, so traders and their EAs expect several positions on the same symbol, including opposite ones. MetaTrader 5 lets the broker choose the mode:
“Two position accounting systems are supported in the trading platform: Netting and Hedging. The system used depends on the account and is set by the broker.”— MetaTrader 5 Help, Basic Principles (accessed October 2026)
In netting mode a symbol can have only one position. A buy and a sell of the same size close each other instead of opening a hedge. If you import a hedged MT4 book into netting groups, open positions merge and margin changes. Clients will see a different account from the one they left. In hedging mode, MetaTrader 5 keeps separate positions and offers a hedged-margin setting, which is closer to MT4 behaviour.
Netting suits exchange-traded instruments, so new futures or stock groups can use it after go-live. Decide the mode per group in the group-mapping sheet and test margin on imported positions before cutover.
The four migration phases, step by step
FXSUPPORT runs every MT4 to MT5 migration in four phases. Each phase ends with a validation gate and a rollback checkpoint, and MT4 stays fully working until the last gate is passed. As a guide from our projects, a single-server migration usually takes 4–6 weeks from assessment to go-live. Multi-server setups with custom plugins, bridges and many groups usually take 8–12 weeks.
- Assessment and planning. We audit the MT4 environment: server architecture, group and symbol settings, plugins, bridge and liquidity connections, CRM and IB integrations, and client data volumes. The output is a migration plan with a timeline, a risk list, a group-mapping sheet (MT4 group → MT5 group, hedging or netting) and a plugin rewrite list.
- Infrastructure setup. We build the MT5 environment to match the current setup, and improve it where the audit found problems. That covers server deployment, network configuration, security hardening, monitoring, the liquidity connection through your bridge's MT5 gateway, and data feeds. Groups, symbols, sessions, swaps and commissions are rebuilt and checked against MT4 exports.
- Data migration. Accounts, balances, history and group assignments are moved with scripts. Automated validation compares each account and group between MT4 and MT5. We run at least one full test migration on a copy of production data before the live weekend.
- Go-live and support. We coordinate the cutover: DNS and server address changes, client login delivery, and close monitoring of the new platform. After go-live, FXSUPPORT gives enhanced support for the first 30 days, then moves into normal MT5 support.
| Phase | Deliverable | Gate to pass | Rollback position |
|---|---|---|---|
| 1. Assessment | Migration plan, group map, plugin list | Broker signs off scope and dates | Nothing changed yet |
| 2. Infrastructure | MT5 servers, groups, symbols, bridge gateway | Test trades route and price correctly on demo | MT4 live; MT5 can be rebuilt |
| 3. Data migration | Rehearsal import and reconciliation report | Zero unexplained balance or position differences | MT4 live; rehearsal discarded |
| 4. Go-live | Live import, client logins, monitoring | Reconciliation plus smoke tests before market open | MT4 kept ready to reopen until the go/no-go call |
Plugins, bridges, CRM and MAM/PAMM: the parts that need code
Everything that talks to the MT4 server through an API must be rebuilt for MT5. This is usually the longest part of the project, so it starts in phase 1. MetaQuotes lists separate Manager, Gateway and Report APIs for MT5, and the MT4 versions are not drop-in replacements.
- Server plugins. Spread, swap, margin, risk or bonus plugins written for MT4 are rewritten for the MT5 Server API with the same business rules, then tested on demo. If a plugin came from a vendor, ask that vendor whether an MT5 version exists before you build your own. See MetaTrader plugin development.
- Bridge and liquidity. Your bridge needs an MT5 gateway. For example, PrimeXM describes its “MT4 Bridge and MT5 Gateway” as a server-side plugin that connects both platforms to XCore. Routing rules, markups and A/B-book settings are rebuilt and compared against MT4 fills. See forex bridge solutions and PrimeXM XCore integration.
- CRM and client portal. Deposits, withdrawals, account opening and IB rebates move to the MT5 Manager or Web API. MT5 has more balance operation types (bonus, commission, agent, interest), so it is worth remapping flows that used to be squeezed into “balance” and “credit”. See forex CRM solutions and MetaTrader API integration.
- MAM/PAMM and copy trading. Master–follower links and allocation history must be moved to the MT5 version of the module. This is the step that made the 2022 TakeProfit Tech case take a further week of manual work. See MAM/PAMM setup.
- Risk and reporting. End-of-day reports, toxic-flow lists and session or DST checks must point at the MT5 database before the first trading day. See forex risk management.
Not sure what your MT4 plugins and bridge need on MT5?
Send us your plugin list, bridge and CRM details. We will tell you what moves, what needs rewriting and how long each part takes, and send you a quote.
Request a free technical review WhatsApp TelegramClient communication: a notice timeline that works
Tell clients early, in stages, and give exact dates and times. Public notices from brokers follow a clear pattern. OANDA Japan stopped new MT4 sub-accounts first, then stopped new orders while still allowing positions to be closed, and finally switched MT4 off. Earn told clients which weekend each server would move, that open positions, balances and history would transfer automatically, that EAs would not be compatible, and that commissions would be charged half-turn on MT5.
A practical notice sequence for a broker-led migration:
- Announcement (8–12 weeks before). Why you are moving, the cutover date, which servers and account types are affected, and a link to an MT5 demo.
- Stop new MT4 accounts (6–8 weeks before). All new clients and IB sign-ups open directly on MT5.
- EA and tools notice (4–6 weeks before). Say plainly that MT4 EAs and indicators do not run on MT5, and that the client or EA vendor must supply MQL5 versions.
- Conditions notice (2–4 weeks before). List any changes to spreads, commission basis, swaps, margin or symbol names, in the form your regulator expects.
- Final reminder (1 week and 1 day before). Cutover window with time zone, what happens to open positions, and when MT5 logins arrive.
- Go-live message. MT5 login details, server name, download links and a support contact for the first trading session.
Cutover weekend and rollback plan
Run the cutover over a weekend so client trading downtime falls inside the market close. Make the go/no-go decision before Sunday's open, based on written reconciliation results. MT4 is not shut down until that decision is made, so rollback means reopening MT4 rather than rebuilding it.
Fri close MT4 set to read-only, final snapshot of accounts, positions, orders | Sat Import to MT5 -> reconcile balances, equity, positions per group | Bridge / LP gateway test trades, CRM and IB sync checks | Sun (pre-open) Smoke tests -> GO / NO-GO decision | \ GO NO-GO | | Send MT5 logins Re-enable MT4 trading, notify clients, MT4 stays read-only fix, re-schedule next weekend
Agree the rollback triggers in advance so nobody has to judge them under pressure on Sunday night:
- Any unexplained difference in balance, credit or open volume after reconciliation.
- Test orders not reaching liquidity, or prices or markups differing from MT4.
- CRM deposits and withdrawals, or IB rebate calculation, not working end to end.
- Margin levels on imported hedged positions differing from MT4 beyond an agreed tolerance.
After go-live, keep MT4 read-only for a period agreed with compliance, so old statements stay available for clients, auditors and disputes.
Big-bang cutover or parallel running?
Most brokers combine both. MT5 runs in parallel for new clients and testing, then remaining MT4 accounts move in one or more scheduled weekends. The choice depends on the size of your book, your plugin dependencies, and how many clients run EAs.
| Approach | How it works | Best for | Main risk |
|---|---|---|---|
| Big-bang weekend | All accounts and positions move in one weekend | Small or mid-size books with few plugins | Everything has to pass in one window |
| Phased by server or account type | Each MT4 server or group moves on its own weekend (as Earn did) | Brokers with several MT4 servers or account types | Two platforms to run and support for weeks |
| Parallel running, client opt-in | MT5 opens beside MT4; clients move voluntarily, then a final deadline | Books with many EA users who need time to port | Liquidity, risk and reporting split across two servers |
| Wind-down | New orders stopped on MT4, close-only period, then shutdown (as OANDA Japan did) | Large retail books with a fixed end date | Clients may leave rather than move |
If you are a trader whose broker is retiring MT4 (MT4からMT5への移行)
If your broker is closing MT4, open an MT5 account with the same broker before the deadline. Move your funds, and replace your EAs and indicators with MQL5 versions, because MT4 programs do not run on MT5. Charts, templates and profiles have to be set up again in the MT5 data folder.
For OANDA Japan clients the official dates are:
- 27 March 2026: new MT4 sub-accounts on the Tokyo server stopped.
- After trading on Friday 25 September 2026: new MT4 orders stopped. From Monday 28 September, MT4 allows closing existing positions only.
- After trading on Friday 27 November 2026: MT4 ends for demo and live accounts, and login is no longer possible.
- Tokyo-server positions and balances still open at the end are moved to MT5 Standard plan accounts on 28–29 November. New York server users continue on fxTrade or TradingView.
Each broker sets its own dates and transfer rules, so check its latest notice. FXSUPPORT does not open trading accounts or convert personal EAs for traders.
If you run a brokerage, these are the same steps your clients will go through, and your side of them is the playbook above. OANDA's staged schedule is a useful template for your own wind-down. If you need help with the server side, see forex broker solutions or contact us.
How FXSUPPORT runs an MT4 to MT5 migration
FXSUPPORT is an outsourced MetaTrader operations team. We plan the migration, build the MT5 side, move the data, run the cutover and then support the new platform. Your team keeps control of business decisions and client communication.
Platform and data
MT5 server setup and configuration, group and symbol rebuild, data migration scripts with automated validation, and backups. See MetaTrader administration.
Integrations
Plugin rewrites, Manager and Web API integrations, bridge gateways for PrimeXM XCore, oneZero Hub, Match-Trade or FIX API, data feeds, and MAM/PAMM setup.
Infrastructure
Servers in the UK and the Netherlands, monitoring, DDoS and security hardening, with a 99.9% uptime target. See MetaTrader server hosting.
After go-live
Enhanced support for the first 30 days, then ongoing MT5 support and risk operations: end-of-day reports, toxic-flow lists and session or DST checks.
You license MT5 through MetaQuotes or work through a white-label provider. MetaQuotes sells MT5 in three tiers (Entry 1,000, Standard 25,000 and Enterprise 200,000 real accounts), and its licence page says it has no access to your servers, accounts or clients' trading history. FXSUPPORT is not affiliated with MetaQuotes or with the bridge and liquidity vendors named here. They are technologies we work with. If you are still on MT4, the free technical review starts phase 1.
Frequently asked questions
How long does an MT4 to MT5 migration take for a broker?
Can open positions be moved from MT4 to MT5?
Should migrated accounts use hedging or netting on MT5?
Do MT4 server plugins work on MT5?
Do MT4 Expert Advisors run on MT5?
Can we keep client trading history?
What happens if the cutover fails?
Does our bridge or liquidity provider support MT5?
Do we need a new MT5 licence to migrate?
When does OANDA Japan end MT4?
How should we tell clients about the migration?
What does FXSUPPORT need to quote a migration?
Sources
- MetaTrader 4 for brokers — MetaQuotes (accessed 8 October 2026)
- Comparison of MetaTrader 5 and MetaTrader 4 for brokers — MetaQuotes (accessed 8 October 2026)
- Purchase MetaTrader 5 and provide services to traders — MetaQuotes (accessed 8 October 2026)
- Basic Principles: Trading Operations — MetaTrader 5 Help (accessed 8 October 2026)
- Migrating from MQL4 to MQL5 — MQL5.com (accessed 8 October 2026)
- MT4 sub-account suspension and MT4 service termination notice (Japanese) — OANDA Japan (accessed 8 October 2026)
- MT4 new-order suspension and MT4 service termination, reissued notice (Japanese) — OANDA Japan (accessed 8 October 2026)
- MT4 and MT5 compatibility (Japanese) — OANDA Japan (accessed 8 October 2026)
- Important Notice: Migration of MT4 Accounts to MT5 — Earn (accessed 8 October 2026)
- Dealing with Urgent Migration from MT4 to MT5 — TakeProfit Tech (accessed 8 October 2026)
- XCore — PrimeXM (accessed 8 October 2026)
- OANDA Japan to stop offering MT4 — FX News Group (accessed 8 October 2026)
FXSUPPORT is not affiliated with MetaQuotes Ltd. or the vendors named on this page. General information, not legal or investment advice.
Plan your MT4 to MT5 migration with FXSUPPORT
Send us your current MT4 setup (servers, groups, plugins, bridge, CRM) and we will return a migration plan with phases, risks and a quote.