StrategyQuant, FTMO Data, Custom Project Guide

Learn to manage data and symbols for backtesting in StrategyQuant using FTMO data on M1 timeframe for major forex pairs like EUR/USD, USD/JPY.

Published · Updated · Methodology: Technical Indicators

Part of: Algorithmic & Automated Trading

  • Methodology: Technical Indicators
  • Content type: educational
  • Timeframes: M1
  • Markets: USD JPY, USD CHF, EUR USD, USD CAD, NZD USD, AUD USD

Indicators used

  • StrategyQuant

Source video

Decoded from: Use FTMO Data in StrategyQuant Like a Pro (Custom Project Guide) by No Nonsense Trader — watch the original

Key timestamps:

  • 0:15 - Introduction to changing data and symbols
  • 0:50 - Renaming a project symbol
  • 1:50 - Modifying symbols and applying default settings
  • 2:20 - Adjusting slippage after applying default settings
  • 3:45 - How to switch broker profiles for data download (e.g., FTMO)
  • 4:50 - Renaming symbols to reflect new broker data
  • 5:40 - Warning about adjusting data timeframes for different currency pairs

Strategy overview

Before a generated strategy means anything, the data underneath it has to resemble the account that will actually trade it — which is the entire subject of this entry, and why it looks unlike the strategies around it. The lone "indicator" field names StrategyQuant itself rather than anything plotted on a chart, and the M1 timeframe is not a trading horizon but the resolution of the feed being wired in: one-minute bars are the raw material from which every coarser bar and every simulated fill is built. The source is No Nonsense Trader's walkthrough "Use FTMO Data in StrategyQuant Like a Pro (Custom Project Guide)", which stays entirely in the plumbing — renaming a project symbol, modifying symbols and applying default settings, switching the broker profile used for downloads, and renaming symbols again so they carry the new provider's identity.

Two details in that sequence carry more weight than their runtime suggests. The first is ordering: the video separates "apply default settings" from "adjust slippage" for a reason, because defaults land on top of whatever per-symbol cost assumptions were there before. A project can end up correctly pointed at the right feed while still simulating fills under a cost model nobody re-checked — the data is right and the results are still flattered. The second is the renaming, which reads as housekeeping and is really provenance: a symbol name is often the only label a databank carries about where its bars came from, and once results from two feeds sit in one project under the same name, there is no way afterwards to say which strategy was validated against which broker.

It is worth being clear about the boundary of what this closes. Matching the data of the firm that will evaluate you narrows the gap in spread, symbol conventions, session boundaries and server time — the things that decide whether a backtest resembles the arena — but the rest of a prop-firm evaluation lives in account rules rather than in price history, and no data import speaks to those. This entry is a configuration walkthrough rather than a trading method: it contains no entry or exit logic, and nothing was extracted from it.

Topics

strategyquant · ftmo data · custom project guide · forex strategy · m1 strategy · backtesting strategy · technical indicators · minor currency pairs trading · trading strategy · pine script

Frequently asked questions

Why use a specific broker's data in StrategyQuant instead of generic data?

Because spreads, symbol specifications, session boundaries and server time differ between providers, and all four feed directly into how a backtest fills orders. Testing on data from the broker or firm that will host the account removes one layer of mismatch between the simulation and the environment the strategy will actually meet.

Does the M1 timeframe mean this is a one-minute strategy?

No. Here M1 describes the resolution of the imported data rather than a trading horizon. One-minute bars are the base from which higher timeframes and fill simulation are constructed, which is why quality at that resolution matters even for strategies that trade far more slowly.

Why rename symbols after switching to a different broker's data?

Because the symbol name is the label that travels with every result built from it. Without distinct names, strategies tested on different feeds end up indistinguishable inside the same project, and the question "which data was this validated on?" becomes unanswerable after the fact.

Does using a prop firm's data make a strategy more likely to pass its evaluation?

It addresses only the data and cost side of the problem — drawdown ceilings, daily loss limits and trading restrictions are account rules, not properties of a price feed. Strategy Decoder catalogues setup and tooling sources like this one alongside the strategies it decodes, because how a strategy is tested is part of what its results mean.

About this strategy page

This trading strategy was decoded by Strategy Decoder's AI from a public YouTube trading video and turned into a structured, reviewable specification. In the interactive app this page shows the full entry and exit logic, risk management settings, the indicators involved with their parameters, AlgoWizard-compatible logic and a Pine Script export ready for TradingView backtesting — plus an automated backtest verdict when one has been computed for this strategy.

Strategy Decoder catalogs 2,229 decoded strategies. Each one is extracted with confidence scoring, cross-linked to the indicators it uses, and kept up to date as new videos are processed daily. Load this page with JavaScript enabled to use the interactive tools, or start from the strategy explorer to filter by methodology, market and timeframe.

Other versions of this strategy

More decoded strategies