Skip to content
Guides
FROpen Studio

Export and manage

Export to cTrader

Check the package and its settings, then observe behaviour in a demo environment.

3 min read · 6 sections
Contents of this guide

Select the version to export

Export a strategy you have reviewed. Check its name, symbol, horizon, protections and selected version. An older backtest does not automatically describe a version changed since that test.

Keep a note of important values before downloading. Use it to compare settings presented after importing on the target platform.

Generate, review and download

  1. Save the rules and controls you want to retain.
  2. Open Code or the available export area.
  3. Generate code and review compilation status when offered.
  4. Read warnings and preview limitations.
  5. Download the format actually offered in the interface.
  6. Retain the file with its version and reference settings.

Available actions and formats depend on your account options. A strategy-data export and a cTrader file serve different purposes; read the action label carefully.

Understand the file’s purpose

ItemPurposeCheck
C# source when offeredReview and prepare strategy codeVersion, parameters and compilation
Strategy or configuration fileRetain project information in the supplied formatIntended use indicated by Pulsix
Package offered for the target platformFollow the appropriate import workflowIncluded content and instructions

Changing a filename extension does not convert one format into another. Use the correct file and the instructions appropriate to your platform version.

Check settings in cTrader

Open the file using the appropriate cTrader workflow, then inspect available parameters before starting it. Compare periods, size, stop, target and sessions with your notes.

Only values actually exposed by the file can appear as its adjustable parameters. A value mentioned in a conversation or written as a constant is not automatically an interface input.

Text
After-import record:
File name and version:
Symbol and timeframe:
Indicator periods:
Size and volume or risk unit:
Stop and target, including units:
Sessions and timezone:
Expected parameters that are absent:

Observe in a demonstration environment

Before live use, observe behaviour with a demo account and identified settings. Inspect several signals, volumes and exits. Read platform messages when an order is not accepted.

Data, quotes, costs, market availability and execution prices can differ from a backtest. Investigate differences rather than assuming an exact reproduction of the historical report.

Investigate discrepancies and updates

When behaviour differs from your intention, first check the file version and active instance settings. Then compare a specific operation: context, time, direction, volume and expected exit.

See Review cTrader code for compilation and parameters, or Troubleshooting to prepare a useful issue report.

Search the guides