Monaxa MT4: The MQL4 Legacy Question
Only one thing keeps MetaTrader 4 alive on a new account: code written for it. This page is about that code — what does not survive a move, and what the migration actually costs.
Open an FxPro account →On a new Monaxa account, MetaTrader 4 is worth installing for one reason: MQL4 code that has to keep running. Compiled .ex4 advisors do not run on MetaTrader 5, MQL4 and MQL5 are different languages, and position handling differs between the terminals. Without that dependency the question does not arise.
Who still has a reason to install MT4 here
- Expert advisors and custom indicators compiled as .ex4 files run on MetaTrader 4 only; MetaTrader 5 loads the .ex5 format and will not read an .ex4 binary
- MQL4 and MQL5 are different languages with different event models, so migrating an advisor means rewriting it and re-testing the result, not recompiling it
- Hedging behaviour differs: MetaTrader 4 keeps every position separate, while MetaTrader 5 may run netting depending on how the account is configured — logic written around one can behave differently under the other
- Rented or vendor-locked advisors licensed for MetaTrader 4 usually cannot be moved at all without a new licence from their author
- Monaxa lists MetaTrader 4 across Standard, Pro, Zero and Cent, as published on monaxa.com and read on 15 September 2026, so the legacy question is the only one that decides this
Nothing in the MQL4 question is specific to Malaysia — the terminals are MetaQuotes software and behave the same at any broker offering them. What a Malaysian reader should note is the hour the code will run: with Malaysia on MYT (UTC+8) and no daylight saving, an advisor tuned to the London and New York overlap will be trading through the Malaysian evening and night.
That matters for the migration decision too. Re-testing a ported advisor means watching it during the session it was written for, which here is not a working-hours task.
What it is and who it is for: what MT4 gives up
Strip away habit and the older terminal keeps exactly one advantage: the body of MQL4 code written for it over the years. Strategy libraries, custom indicators, third-party advisors bought or rented — none of it moves across on its own.
That is a genuine asset for someone who owns it and worth nothing at all to someone who does not. A reader without MQL4 code in play is choosing between two terminals that reach the same instruments on the same account types at this broker, so the choice answers itself on the code alone.
The two terminals are separate products rather than versions of one: MetaTrader 4 and MetaTrader 5 ship different languages, and that is the whole of the migration problem.
What does not survive a move to MetaTrader 5
Compiled advisors first. An .ex4 file is a MetaTrader 4 binary; MetaTrader 5 loads .ex5 and will not read it. Without the MQL4 source, the advisor stops there.
Then the source itself. MQL4 and MQL5 differ in their event model, their order functions and their handling of positions, so porting is a rewrite followed by fresh testing rather than a recompile. And position handling can differ too: MetaTrader 4 keeps every position separate, while MetaTrader 5 may net them depending on account configuration — logic built on one behaves differently under the other.
Rented or vendor-locked advisors are the hardest case: a licence issued for MetaTrader 4 usually does not extend to a rewritten MetaTrader 5 build, and the author decides, not the trader.
How MT4 credentials relate to the portal
A MetaTrader terminal connects with a trading login issued for the account, not with the browser portal password. That is how the platform works wherever it is offered: entering a portal password into the terminal produces an authorisation failure, and that failure reads exactly like a blocked account without being one.
Resetting the portal password leaves the terminal login untouched, and the reverse holds too. When a sign-in fails, establish which of the two systems is refusing it before resetting anything — that single step settles the question.
What the migration actually costs
Count it in three parts before deciding. The rewrite itself, which scales with how much of the advisor depends on order-handling functions rather than on maths. The re-testing, which cannot be skipped because the behaviour has changed. And the licence, where one applies.
Against that, weigh what staying costs: the comparison is between two separate products, not two versions of one, so keeping MetaTrader 4 means keeping a separate codebase alive alongside it. Monaxa lists both terminals across all four of its account types, as published on monaxa.com and read on 15 September 2026, so nothing about the broker forces the decision either way — the full comparison is on the MT5 page.
MT4 against MT5 on a Monaxa account
| Item | MetaTrader 4 | MetaTrader 5 |
|---|---|---|
| Compiled program format | .ex4 | .ex5 |
| Language | MQL4 | MQL5 |
| Account types listed | 4 (Standard, Pro, Zero, Cent) | 4 (Standard, Pro, Zero, Cent) |
| Asset classes reachable | 6 | 6 |
| Terminal credentials | Separate from the client portal | Separate from the client portal |
Published by the broker on monaxa.com and read on 15 September 2026; confirm current terms before trading. CFDs carry a high risk of losing money rapidly due to leverage.