Pineify logo

Code migration guide

NinjaScript to cTrader converter

NinjaScript and cTrader share C# syntax, but the migration still requires a new Robot or Indicator class, cTrader lifecycle methods, Bars APIs, volume units, and trade result handling.

Open the cTrader Coding AgentReview cTrader AI Coding Agent

Generate a cTrader C# draft, then build it in cTrader Algo and test it with the intended symbol and account settings.

Conversion map

What changes between NinjaTrader 8 and cTrader

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.Robots use lifecycle methods including OnStart, OnTick, OnBar, OnStop, and OnException; indicators calculate by index.Choose when each NinjaTrader 8 calculation should run in cTrader; 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.Bars and DataSeries expose typed C# collections, while multi-timeframe data is requested explicitly.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.Indicator classes expose output series and use the cTrader Algo indicators API.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.Robot methods submit and manage trades through Symbol, Positions, PendingOrders, and volume measured in units.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.Build the C# project in cTrader Algo, resolve build output, attach it to the intended symbol, and run a cTrader backtest.Treat generated cTrader C# as a draft until it passes the target editor, chart, and backtest workflow.

Code example

Moving-average cross: NinjaScript to cTrader C#

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);
}
cTrader C# target 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);

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 a C# cBot or custom indicator project. This choice controls lifecycle methods and available APIs.

  3. 3

    Rewrite through target APIs

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

  4. 4

    Validate behavior natively

    Build the C# project in cTrader Algo, resolve build output, attach it to the intended symbol, and run a cTrader backtest.

Manual decisions

Decisions code replacement cannot make

  • Map NinjaScript states and OnBarUpdate to cTrader initialization plus OnBar or OnTick behavior.
  • Replace BarsInProgress routing with explicit cTrader Bars instances for each market and timeframe.
  • Translate managed order methods and signal names into cTrader positions, labels, and protection updates.

Limitations

What the draft cannot prove

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

Use cases

When this conversion is useful

  • Move a NinjaTrader Strategy to a cTrader cBot.
  • Port a NinjaScript Indicator to a cTrader custom indicator.
  • Keep reusable C# math while rebuilding platform services and trade execution.

FAQ

NinjaScript to cTrader C# questions

Official references

Build the cTrader C# draft with its native model in view

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

Open the cTrader Coding AgentProduct details