Pineify logo

Code migration guide

MQL4 to NinjaScript converter

Moving MQL4 to NinjaScript requires assigning MT4 callback work to NinjaTrader lifecycle states, converting shift-based price access to bars-ago Series, and replacing OrderSend ticket logic with a Strategy order approach.

Open the NinjaScript Coding AgentReview NinjaTrader AI Coding Agent

Generate a NinjaScript draft, then compile it in NinjaScript Editor and test it in NinjaTrader 8.

Conversion map

What changes between MetaTrader 4 and NinjaTrader 8

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
LifecycleExpert Advisors and indicators respond to predefined callbacks such as OnInit, OnTick, and OnCalculate.OnStateChange configures lifecycle states and OnBarUpdate handles bar-driven calculations at the selected Calculate frequency.Choose when each MetaTrader 4 calculation should run in NinjaTrader 8; matching syntax alone does not preserve timing.
Market data and historyPrice series use terminal arrays and shift-based access; indicators commonly expose calculated values through buffers.Series use bars-ago indexing such as Close[0]; multi-series scripts must route work with BarsInProgress.Recheck bar indexing, warm-up requirements, timeframe requests, and behavior on an unfinished bar.
Indicators and chart outputCustom indicators bind buffers, while built-in indicator functions can return values directly for a requested shift.Indicator classes configure plots and update their Series values inside the NinjaScript lifecycle.Map calculations before recreating plots, labels, colors, and platform-specific drawing objects.
Orders and positionsClassic trade functions such as OrderSend work with order tickets, lots, prices, stops, and a shared order pool.Strategies can use managed methods such as EnterLong and ExitLong or opt into lower-level unmanaged handling.Define fill timing, sizing, pyramiding or hedging, stops, and position ownership for the target platform.
Native validationCompile the .mq4 file in MetaEditor, attach it in MetaTrader 4, and test the correct EA or indicator artifact.Compile in NinjaScript Editor, load the Indicator or Strategy, and test strategies with Strategy Analyzer before runtime use.Treat generated NinjaScript as a draft until it passes the target editor, chart, and backtest workflow.

Code example

Moving-average cross: MQL4 to NinjaScript

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.

MQL4 source fragment
double fast0 = iMA(NULL, 0, 10, 0, MODE_SMA, PRICE_CLOSE, 0);
double fast1 = iMA(NULL, 0, 10, 0, MODE_SMA, PRICE_CLOSE, 1);
double slow0 = iMA(NULL, 0, 20, 0, MODE_SMA, PRICE_CLOSE, 0);
double slow1 = iMA(NULL, 0, 20, 0, MODE_SMA, PRICE_CLOSE, 1);
bool longSignal = fast1 <= slow1 && fast0 > slow0;
NinjaScript target fragment
protected override void OnBarUpdate()
{
    if (CurrentBar < 20) return;
    bool longSignal = CrossAbove(SMA(10), SMA(20), 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 an .mq4 Expert Advisor or custom indicator.

  2. 2

    Choose the target artifact

    Decide whether the result is a C# NinjaScript Indicator or Strategy class. This choice controls lifecycle methods and available APIs.

  3. 3

    Rewrite through target APIs

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

  4. 4

    Validate behavior natively

    Compile in NinjaScript Editor, load the Indicator or Strategy, and test strategies with Strategy Analyzer before runtime use.

Manual decisions

Decisions code replacement cannot make

  • Choose a NinjaScript Indicator or Strategy and configure it in OnStateChange.
  • Match each MQL4 timeframe request with a NinjaScript data series and BarsInProgress branch.
  • Translate MT4 orders, stops, and magic numbers into managed signals or a deliberate unmanaged design.

Limitations

What the draft cannot prove

  • MetaTrader 4 and NinjaTrader 8 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 NinjaTrader 8.
  • Pineify can generate and revise a NinjaScript draft, but the target platform remains the authority for compilation, loading, backtesting, and runtime behavior.

Use cases

When this conversion is useful

  • Port an MQL4 Expert Advisor to a NinjaTrader Strategy.
  • Rebuild an MT4 indicator as a NinjaScript Indicator.
  • Move shift-based MT4 signals into NinjaTrader series and analysis tools.

FAQ

MQL4 to NinjaScript questions

Official references

Build the NinjaScript draft with its native model in view

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

Open the NinjaScript Coding AgentProduct details