Calculations & Buffers
Calculations are rebuilt in C#; buffers become line series, histograms keep their style, and arrows become markers. Any visual differences are agreed in advance.
MT4 → Quantower Conversion
Convert MT4 Expert Advisors & Indicators to Quantower
We rewrite MT4 Expert Advisors as Quantower strategies and MT4 indicators as Quantower indicators in C# — rebuilding positions, sizes and sessions for your Quantower connection, and checking the result against criteria agreed with you.
MT4 EA to Quantower StrategyMT4 Indicator to QuantowerMQL4 to C#Rewritten by Hand
3,000+ Projects Delivered
Fixed Scope & Price Before Work
Full C# Source Code
Checked Against Agreed Criteria
MQL4C# · Quantower
iMA(NULL, 0, 21, 0, MODE_EMA, PRICE_CLOSE, i)Core.Indicators.BuiltIn.EMA(21, PriceType.Close)SetIndexBuffer(0, EmaBuffer)AddLineSeries("EMA", Color.DodgerBlue, 2)iMA(NULL, PERIOD_H1, 21, …, shift)Symbol.GetHistory(Period.HOUR1, …)OrderSend(Symbol(), OP_BUY, lots, Ask, …)Core.Instance.PlaceOrder(… Side.Buy …)Same logic, rebuilt on Quantower’s C# API
Overview
What MT4 to Quantower Conversion Means
MT4 to Quantower conversion means rewriting MQL4 code in C# on Quantower’s API: an Expert Advisor becomes a Quantower strategy and an indicator becomes a Quantower indicator. The move can keep the same market — depending on your connection, Quantower works with forex brokers as well as futures, stock and crypto feeds — or change it. If the instrument changes, trade sizes, price distances and sessions are adapted as well.
- From
- MQL4 on MetaTrader 4
- To
- C# on Quantower’s API
- Expert Advisor
- Quantower strategy
- Indicator
- Quantower indicator
- You receive
- C# source code and everything needed to run it
- Method
- Rewritten by hand, no automatic converters
Indicators
Convert an MT4 Indicator to Quantower
Converting an MT4 indicator to Quantower means rebuilding its calculations on Quantower’s API and how it draws on the chart. We convert standard, custom and multi-timeframe indicators, as well as panels and dashboards.
iCustom Calls
Calls to other custom indicators through iCustom are rebuilt in C# as well, so we need their source too.
Other Timeframes
Data from other timeframes or symbols is loaded as separate history and keeps the original’s behaviour — from the forming bar or from confirmed bars only.
Objects & Labels
Lines, labels, boxes and panels drawn as chart objects become drawings, markers or custom painting in Quantower; the look is agreed separately.
Built-In Indicators
Calls to MT4’s built-in indicators use Quantower’s own indicators where their values match; where the platforms calculate differently, we write the calculation ourselves.
Alerts & Improvements
Alert conditions are built into the Quantower version, and new settings or functions can be added on request.
Expert Advisors
Convert an MT4 Expert Advisor to a Quantower Strategy
An MT4 Expert Advisor and a Quantower strategy automate the same kind of trading, but they track positions, size trades and react to new data differently. Converting an EA keeps its trading rules and rebuilds its trade handling for Quantower and your connection.
Entries & Exits
OrderSend, OrderModify and OrderClose logic built around tickets is rebuilt with Quantower’s trading methods — including scaling in, partial closes and exits tied to specific entries.
Positions & Connection
Position handling depends on your Quantower connection — one net position or separate positions — so it is checked and agreed, together with how the strategy runs alongside other strategies and manual trades, and what it does if a position is already open at start.
Position Sizing
Position sizes are recalculated using the target symbol’s lot size, volume limits and step, then checked against your risk rules.
Stops & Targets
Stop loss, take profit, trailing stop and breakeven are placed as protective orders your connection supports, with price distances converted for the symbol.
Instrument & Sessions
Each MT4 symbol is matched to a symbol on your Quantower connection. If the instrument changes, the strategy is adapted to its tick size, tick value and sessions.
New Bars & Ticks
Logic written to act once per bar keeps that timing, and tick-by-tick logic is rebuilt on the quote or trade events of your connection — the agreed calculation mode is kept, and signal timing is checked on the chosen data.
Results in Quantower won’t match the MT4 Strategy Tester exactly: the platforms use different data — sometimes for a different instrument — and model fills differently. We check that entries and exits follow the agreed rules.
Platform differences
MQL4 to Quantower C#: What Changes and How We Handle It
MetaTrader 4 and Quantower handle instruments, positions and code in different ways. These are the differences that decide whether a converted script behaves like the original — and what we do about each of them.
Instruments
Forex, CFDs and other symbols from your MT4 broker
Symbols from your Quantower connection — futures, crypto, stocks or forex
If the instrument changes, we agree which one replaces each MT4 symbol and adapt sizes, price distances and sessions.
Trade size
Lots, sized by the MT4 symbol’s contract
Quantity in lots, with the lot size and step set by each symbol
Sizes are recalculated with the target symbol’s lot size, volume limits and step, and checked against your risk rules.
Positions
Several separate order tickets, identified by magic number
Position handling depends on your connection — one net position or separate positions
We map each entry and its exits, and agree how the strategy works alongside other strategies, manual trades and positions already open at start.
Reading history
Price arrays counted back from the current bar
History that can be read from the newest or the oldest bar
We check the reading direction for every series, so values line up bar by bar.
Calculation
EA code runs on every tick; bar-close logic checks for a new bar
A strategy reacts to the quote, trade and bar events it subscribes to — new quotes and new trades are separate events
We keep the agreed conditions and calculation timing, and check historical and real-time behaviour separately.
Trading hours and time zone
Your MT4 broker’s server time
The session settings of your connection and the bar timestamps it provides
We compare sessions, bar timestamps and the time zone each version’s logic uses — matching chart clocks alone isn’t enough.
Backtesting
The MT4 Strategy Tester and its tick modelling
Quantower’s own backtesting and optimisation
We agree how both backtests are run, so they are compared on similar assumptions.
What may not carry over one to one
Some things depend on the platform itself: 32-bit DLLs built for MT4 can’t be loaded directly by 64-bit Quantower, so each is checked for a compatible version or another way to connect it, and replaced only where needed — .NET libraries can often be used directly; symbols your Quantower connection doesn’t provide; and real traded volume, which depends on your feed. We point these out before work starts and agree the closest Quantower equivalent with you.
Why manual
Manual vs. Automatic Conversion
A converter or an AI pass can produce C# quickly. The risk is not the tool but an unchecked result: code can compile and still trade differently, because MetaTrader and Quantower read history, size trades and track positions differently. We start from how the MT4 version behaves and rebuild it on Quantower’s API.
| Automatic conversion | Manual conversion at Nordman Algorithms | |
|---|---|---|
| Starting point | Often the MQL syntax, statement by statement | How the MT4 version behaves |
| Platform differences | Often found later, if at all | Identified before work starts and agreed with you |
| Positions and sizes | Order tickets and lots copied as they are | Rebuilt for your Quantower connection and symbol units |
Where unchecked conversions usually go wrong
- History read from the wrong endMT4 price arrays count back from the current bar, while Quantower history can be read from either end; read the wrong way, values shift or reverse.
- Sizes copied as they areA size of 0.10 copied as it is means something different when the target symbol’s lot size differs — on a futures contract or a crypto pair, for example — so it has to be recalculated.
- Tickets without a position modelMT4 logic that loops over open tickets has no direct equivalent; mapped wrongly to your connection’s positions, exits close the wrong trades.
- Bar-close logic firing on every tickLogic written to act once per bar fires many times per bar if new bars aren’t detected the same way in Quantower.
- Indicator calls without the sourceCalls to other custom indicators can’t be rebuilt without their source, and approximating them changes the signals.
- Trades at the wrong momentWhen a signal is calculated, when the order is sent and when it fills depend on the order type and settings on each platform; transferred wrongly, they shift entries and exits.
Have an MT4 EA or indicator you want in Quantower?
Send it to us — we review it and give you a fixed price and timeline before work starts.
Checking the result
How We Check the Converted Script
We run the MT4 original and the Quantower version on the same timeframe, with comparable price types, trading sessions and bar timestamps, and compare them against acceptance criteria agreed with you:
- Calculated values on selected bars
- Price type — MT4 charts are built on bid prices; we match that price type where the target instrument and connection support it, otherwise the price basis and comparison criteria are agreed before work starts
- Signal timing — on which bar a signal appears, inside the bar or after it closes
- Entry and exit conditions for strategies
- Agreed deviations — differences accepted in advance, such as visual layout or broker-specific execution
If the instrument stays the same, we compare values and signal timing directly. If it changes — say, from a forex pair to a futures contract — the data differ, so we check that the agreed rules are followed and the risk is recalculated correctly, rather than expecting identical values or trades. If something doesn’t match, we find the cause — price data, platform behaviour or the code.
What you receive
- C# source code — the full code of the strategy or indicator
- Everything needed to run it in Quantower; we help with installation if you need it
- Settings agreed with you before work starts
- Fixes for bugs and differences from the agreed specification after delivery
Process
How an MT4 to Quantower Conversion Works
Send the MQL4 code
Share the .mq4 source with its .mqh include files, the source of any custom indicators it calls and your .set file if you have one — plus a short description.
You sendSource + dependenciesReview and fixed quote
We analyse the code, agree the Quantower connection, symbol and sessions — the same market or a new one — and agree settings, acceptance criteria, price and timeline.
You getFixed price + criteriaRewrite in C#
The EA or indicator is rebuilt as a Quantower strategy or indicator, including any extra features you asked for.
We buildThe Quantower versionCheck against the criteria
The Quantower version is checked against the acceptance criteria agreed in step 2.
We checkValues, signals, tradesDelivery and support
Bugs and differences from the agreed specification are fixed after delivery.
You getSource + files to run
Scope
What Affects the Price and Timeline
Every EA and indicator is reviewed before we quote. These are the main factors.
Size of the Code
How much logic the code contains and how many parts depend on each other.
Trade Handling
For EAs: how orders, positions, stops, scaling and partial closes are managed.
Instruments & Connection
Which Quantower connection and symbols the strategy will trade — the same market or a new one.
Visual Elements
Objects, panels and dashboards drawn on the chart.
DLLs & External Libraries
Each dependency is checked: whether a .NET library can be used directly or a replacement is needed.
Only an .ex4 File?
Conversion needs the .mq4 source. Without it, recreating the EA or indicator from your description is assessed separately.
★★★★★
"I have used Nordman Algorithms to code about a dozen MT4/MT5 Expert advisors and custom indicators I have developed over the past few years and honestly I can't recommend them enough. Each project has been delivered quickly and for a fair price. …"
★★★★★
"Alexei's knowledge of C# is excellent and he was able to code to my exact requirements. Once the strategy was delivered, he was happy to make any adjustments I needed. I've enjoyed working with Alexei and I am sure we will work again."
★★★★★
"Alexei is the only one who got this project done, i have tried many before him but all of them failed. a professional programmer i can rely on very mature and excellent in communication. really patient and will revise and develop the coding to satisfaction level. …"
FAQ
MT4 to Quantower Conversion — Common Questions
No. Quantower runs C# written against its own API; MQL4 code — .mq4 or .ex4 — has to be rewritten.
Yes. The EA’s trading rules are kept and its trade handling is rebuilt for Quantower — quantity, positions, protective orders and any extra trade management — with sizing and risk agreed with you.
If your Quantower connection provides the same symbols, you don’t need to change markets — but the symbol’s specification, position size, price type, trading hours and execution rules are still checked. If you move to another market — say, futures — sizes, price distances and sessions are adapted, and how the strategy behaves there is checked against the agreed rules.
Yes. For indicators, the connection decides which symbols, history and volume data are available. For strategies, it also decides the order types, execution and position handling. We agree the connection before work starts and build for it.
On the same market, values can come close but not always match exactly: your MT4 broker and your Quantower connection provide different data, and some built-in indicators are calculated slightly differently. If the instrument changes, identical values aren’t the goal — we check that the agreed rules are followed and the risk is recalculated correctly.
Quantower has its own backtesting and optimisation, and whether a particular strategy’s logic can be reproduced on history there is checked before work starts. Results won’t match the MT4 Strategy Tester exactly: the platforms use different data and model fills differently.
Conversion needs the .mq4 source code. Without it, we can assess recreating the EA or indicator from your description, settings and examples of how it behaves — but an exact match with the original can’t be promised in advance.
Yes. Quantower indicators and strategies can be rewritten in MQL4; parts that rely on Quantower-only features are agreed before work starts.
It depends on the size of the code, the trade handling, the indicators it calls, visual elements and any DLLs. After reviewing your .mq4 code we give you a fixed price and an estimated timeline before work starts.
Send Your MQL4 Code for a Quote
Share the .mq4 source code with its include files and the custom indicators it uses, and a short description of what it does and which Quantower connection it should trade through. We will review it and give you a fixed price and timeline before work starts.
Free Technical Assessment
Fixed Price Before Work
Source Code Ownership