Pineify logo

Code migration guide

cTrader to MQL5 converter

A cTrader cBot can become an MQL5 Expert Advisor after C# Robot events, typed indicators, position labels, and volume units are redesigned for MQL5 events, handles, and the selected MT5 account position mode.

Open the MQL5 Coding AgentReview MQL5 AI Coding Agent

Generate an MQL5 draft, then compile it in MetaEditor 5 and test the target account mode in MetaTrader 5.

Conversion map

What changes between cTrader and MetaTrader 5

The migration is a model translation. Use this map to decide where the source behavior belongs before writing target syntax.

Source and target platform conversion map
ConcernSource modelTarget modelMigration decision
LifecycleRobots use lifecycle methods including OnStart, OnTick, OnBar, OnStop, and OnException; indicators calculate by index.Programs respond to typed events such as OnInit, OnTick, OnTradeTransaction, and OnCalculate.Choose when each cTrader calculation should run in MetaTrader 5; matching syntax alone does not preserve timing.
Market data and historyBars and DataSeries expose typed C# collections, while multi-timeframe data is requested explicitly.Timeseries and indicator values are commonly copied into arrays; built-in indicators return handles read with CopyBuffer.Recheck bar indexing, warm-up requirements, timeframe requests, and behavior on an unfinished bar.
Indicators and chart outputIndicator classes expose output series and use the cTrader Algo indicators API.Indicator handles, buffers, plots, and OnCalculate separate setup from repeated calculation.Map calculations before recreating plots, labels, colors, and platform-specific drawing objects.
Orders and positionsRobot methods submit and manage trades through Symbol, Positions, PendingOrders, and volume measured in units.Trade requests and CTrade operate with orders, deals, and account-dependent position models.Define fill timing, sizing, pyramiding or hedging, stops, and position ownership for the target platform.
Native validationBuild the C# project in cTrader Algo, resolve build output, attach it to the intended symbol, and run a cTrader backtest.Compile the .mq5 file in MetaEditor 5, load it in MetaTrader 5, and use Strategy Tester for the intended artifact.Treat generated MQL5 as a draft until it passes the target editor, chart, and backtest workflow.

Code example

Moving-average cross: cTrader C# to MQL5

These fragments show where the same signal starts in each API. They are not complete standalone programs; lifecycle setup, inputs, plots, and order handling still depend on the selected artifact.

cTrader C# source fragment
var fast = Indicators.SimpleMovingAverage(Bars.ClosePrices, 10);
var slow = Indicators.SimpleMovingAverage(Bars.ClosePrices, 20);
bool longSignal = fast.Result.Last(2) <= slow.Result.Last(2)
    && fast.Result.Last(1) > slow.Result.Last(1);
MQL5 target fragment
double fast[2], slow[2];
CopyBuffer(fastHandle, 0, 0, 2, fast);
CopyBuffer(slowHandle, 0, 0, 2, slow);
bool longSignal = fast[0] <= slow[0] && fast[1] > slow[1];

Workflow

A four-step migration path

Keep generation, target-platform validation, and behavior comparison as separate stages.

  1. 1

    Inventory the source behavior

    Separate calculations, plots, alerts, orders, external dependencies, and assumptions in a C# cBot or custom indicator project.

  2. 2

    Choose the target artifact

    Decide whether the result is an .mq5 Expert Advisor or custom indicator. This choice controls lifecycle methods and available APIs.

  3. 3

    Rewrite through target APIs

    Translate state, series, indicators, drawings, and orders into MetaTrader 5 concepts instead of replacing function names.

  4. 4

    Validate behavior natively

    Compile the .mq5 file in MetaEditor 5, load it in MetaTrader 5, and use Strategy Tester for the intended artifact.

Manual decisions

Decisions code replacement cannot make

  • Map cBot labels and Positions queries to MQL5 magic numbers, comments, and position selection.
  • Convert C# volume units and Symbol rules to MT5 lots, steps, stops, and filling modes.
  • Replace cTrader indicator instances with MQL5 handles whose buffers are copied and released explicitly.

Limitations

What the draft cannot prove

  • cTrader and MetaTrader 5 do not share one execution, data, or order model, so behavior can change even when both versions compile.
  • Broker, symbol, session, timezone, history, and fill settings can change signals and backtest results on MetaTrader 5.
  • Pineify can generate and revise a MQL5 draft, but the target platform remains the authority for compilation, loading, backtesting, and runtime behavior.

Use cases

When this conversion is useful

  • Port a cBot to an MT5 Expert Advisor.
  • Rebuild a cTrader indicator as an MQL5 custom indicator.
  • Move shared C# signal logic into MT5-native trading and test infrastructure.

FAQ

cTrader C# to MQL5 questions

Official references

Build the MQL5 draft with its native model in view

Bring the complete source and your artifact, timing, data, and order requirements. Validate the result in MetaTrader 5.

Open the MQL5 Coding AgentProduct details