How to Convert a Pine Script Indicator to a Strategy in TradingView

Indicator vs. Strategy: Key differences in TradingView

In TradingView, indicators and strategies serve distinct roles. Indicators compute calculations and draw plots, shapes, or tables on charts. They cannot track position size, calculate net profit, compute drawdowns, or record trade logs. Strategies, by contrast, run within TradingViews built-in broker emulator. Every signal is simulated as a simulated buy or sell order, populating the Strategy Tester tab with metrics like win rate, profit factor, maximum drawdown, and equity curves.

Step-by-step indicator to strategy conversion guide

Follow this 4-step workflow to safely convert your technical indicator code into a backtestable strategy in Pine Script v6:

• Step 1: Replace indicator() with strategy(): Declare strategy name, overlay status, starting equity, and position sizing mode.
• Step 2: Map buy and sell conditions to orders: Locate where your indicator evaluates boolean triggers (such as crossover or RSI thresholds) and replace plotshape() with strategy.entry("Long", strategy.long) and strategy.entry("Short", strategy.short).
• Step 3: Define exit rules: Add risk controls using strategy.exit() for stop-loss and take-profit targets, or strategy.close() for opposing trend reversal exits.
• Step 4: Clean up alertcondition calls: If the original indicator contained alertcondition(), delete those lines or replace them with alert() triggers. Otherwise, the Pine compiler throws CE10101 compilation errors.

Before & after code example: Moving average crossover in Pine Script v6

Here is a direct side-by-side comparison showing an indicator script converted into an executable Pine Script v6 strategy with commission and slippage controls.

//@version=6
// Converted from indicator("MA Cross") to strategy()
strategy("MA Cross Strategy [v6]", 
         overlay = true, 
         initial_capital = 10000, 
         default_qty_type = strategy.percent_of_equity, 
         default_qty_value = 15,
         commission_type = strategy.commission.percent,
         commission_value = 0.05,
         slippage = 1)

// Indicator logic preserved
fastLen = input.int(10, "Fast Length")
slowLen = input.int(30, "Slow Length")
stopPct = input.float(2.0, "Stop Loss %")

fastMa = ta.sma(close, fastLen)
slowMa = ta.sma(close, slowLen)

plot(fastMa, "Fast MA", color = color.blue)
plot(slowMa, "Slow MA", color = color.orange)

// Signal conditions
longTrigger = ta.crossover(fastMa, slowMa)
shortTrigger = ta.crossunder(fastMa, slowMa)

// Execution orders replacing plotshape()
if longTrigger
    strategy.entry("Long", strategy.long)

if shortTrigger
    strategy.entry("Short", strategy.short)

// Risk management exit
if strategy.position_size > 0
    stopPrice = strategy.position_avg_price * (1 - stopPct / 100)
    strategy.exit("Exit Long", from_entry = "Long", stop = stopPrice)

if strategy.position_size < 0
    stopPriceShort = strategy.position_avg_price * (1 + stopPct / 100)
    strategy.exit("Exit Short", from_entry = "Short", stop = stopPriceShort)

Solving common compiler errors during conversion

When converting an indicator to a strategy, the TradingView compiler frequently flags specific syntax mismatches. Understanding these compiler errors saves hours of manual debugging:

• alertcondition() not allowed: In strategy scripts, alertcondition is illegal. Remove alertcondition and rely on TradingViews built-in strategy alert options (such as "Order fills only").
• plot() inside if blocks: Just like indicators, strategies cannot call plot() or plotshape() inside conditional if blocks. Plot statements must stay in the global script scope.
• calc_on_order_fills assumptions: By default, strategies recalculate only when bars close. If your indicator relied on intra-bar wick touches, set calc_on_order_fills = true or calc_on_every_tick = true.
• Initial capital too low: If default_qty_value requires more capital than initial_capital allows, your strategy will generate zero trades.