BlueprintUpdated
Exports & Integrations
The Export menu in the Portfolio Builder: Native Engine Portfolio files, Excel workbooks, and OptionsApp-compatible export — plus what each is for.
A portfolio that lives only inside an analytics tool doesn't trade. The Export dropdown in the Portfolio Builder's header turns the construction you settled on into files.
The three exports
| Export | Produces | Use it for |
|---|---|---|
| Native Engine Portfolio | A .cfe-portfolio.json file | Sharing and backup. The only format that round-trips: import it back and you get the same portfolio — strategies, contract counts, on/off states, aliases, account size. |
| Export to Excel | An .xlsx workbook | Offline analysis, record-keeping, or as an entry template. One row per enabled strategy with parameters, sizing and metrics. |
| Export to OptionsApp | An OptionsApp-compatible .json config | Setting up automated execution through your own OptionsApp + broker setup. One-way: it can't be re-imported. |
Two ground rules that apply to all exports:
- Exports include enabled strategies only (the Native format additionally remembers your disabled rows so the round-trip is lossless).
- Exporting is available once the portfolio has at least one enabled strategy.
The import counterparts
Exports are half the story — the Workbench also ingests:
- Native Engine Portfolio files import via the Builder's Import button (see Saving, loading & sharing).
- Your own backtest and live-trade data import via the Import page in the left nav — covered in Importing your data.
Detail pages
- Excel & Native Portfolio — formats, file contents, and the round-trip rules.
- OptionsApp export — what the file contains, how iron condors are split, and the validation acknowledgment.