Pineify logo

Code migration guide

thinkScript to NinjaScript converter

thinkScript series and plots can be rebuilt inside a NinjaScript Indicator, while AddOrder strategy logic needs a NinjaTrader Strategy with explicit lifecycle, Calculate mode, warm-up, and managed order behavior.

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 thinkorswim 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
LifecycleDeclarative expressions are evaluated over chart data; studies, strategies, scans, and watchlist columns have different contexts.OnStateChange configures lifecycle states and OnBarUpdate handles bar-driven calculations at the selected Calculate frequency.Choose when each thinkorswim calculation should run in NinjaTrader 8; matching syntax alone does not preserve timing.
Market data and historyDefinitions and plots form time series and access prior values with bracket indexing or recursive definitions.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 outputStudies use def, plot, painting, and built-in study functions to render chart analysis.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 positionsStrategies use AddOrder to add simulated orders to charts; platform conditional orders are a separate workflow.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 validationPaste into thinkScript Editor, save it as the correct study or strategy, add it to a chart, and inspect plots or the strategy report.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: thinkScript 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.

thinkScript source fragment
def fast = Average(close, 10);
def slow = Average(close, 20);
plot longSignal = fast crosses above slow;
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 a thinkScript study or strategy definition.

  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 Indicator or Strategy and configure its defaults in OnStateChange.
  • Rewrite recursive definitions and aggregation references with NinjaScript Series and added data streams.
  • Separate thinkScript simulated orders from NinjaTrader orders that can become live when a Strategy runs in realtime.

Limitations

What the draft cannot prove

  • thinkorswim 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 a thinkorswim study to a NinjaTrader Indicator.
  • Rebuild a thinkScript strategy for NinjaTrader Strategy Analyzer.
  • Convert plots and drawing logic into NinjaScript chart output.

FAQ

thinkScript 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