Pineify logo

Code migration guide

NinjaScript to MQL4 converter

A NinjaScript Indicator or Strategy can be moved to MQL4 after lifecycle states and Series are flattened into MT4 callbacks and buffers, with managed NinjaTrader orders rebuilt as classic ticket operations.

Open the MQL4 Coding AgentReview MQL4 AI Coding Agent

Generate an MQL4 draft, then compile it in MetaEditor and test it in MetaTrader 4.

Conversion map

What changes between NinjaTrader 8 and MetaTrader 4

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

Code example

Moving-average cross: NinjaScript to MQL4

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.

NinjaScript source fragment
protected override void OnBarUpdate()
{
    if (CurrentBar < 20) return;
    bool longSignal = CrossAbove(SMA(10), SMA(20), 1);
}
MQL4 target 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;

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# NinjaScript Indicator or Strategy class.

  2. 2

    Choose the target artifact

    Decide whether the result is an .mq4 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 4 concepts instead of replacing function names.

  4. 4

    Validate behavior natively

    Compile the .mq4 file in MetaEditor, attach it in MetaTrader 4, and test the correct EA or indicator artifact.

Manual decisions

Decisions code replacement cannot make

  • Map setup, historical processing, realtime work, and cleanup to the smaller MQL4 callback model.
  • Convert BarsInProgress and bars-ago series into explicit MT4 symbol, timeframe, and shift requests.
  • Replace managed signal relationships and OCO rules with order tickets and manual coordination.

Limitations

What the draft cannot prove

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

Use cases

When this conversion is useful

  • Port a NinjaTrader Strategy to an MT4 Expert Advisor.
  • Rebuild a NinjaScript Indicator with MQL4 buffers.
  • Move signal logic to MT4 while documenting lifecycle and order-model reductions.

FAQ

NinjaScript to MQL4 questions

Official references

Build the MQL4 draft with its native model in view

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

Open the MQL4 Coding AgentProduct details