Excel & Native Portfolio
The Excel export's contents and naming options, and the Native Engine Portfolio JSON — the round-trippable file that moves portfolios between accounts.
Export to Excel
Choosing Export to Excel first asks for a naming convention:
- CashFlow Engine (default) — descriptive names like
Iron Condor · 50-wide · $2.25 · 11:59. - Rob's format (ROPS) — the compact community nomenclature (e.g.
600-M-95-200-00: premium ×100, gate, stop-loss, width), sorted by MAR.
Either way you get a real .xlsx with one row per enabled strategy and
these columns:
Strategy · Name · Family · Entry · Width · Stop Loss % · Premium $ · Contracts · MAR · CAGR % · Max DD % · Win % · Sharpe · Sortino · Total P/L $ · Margin/Contract $ · Total Margin $ · % of Margin
That's the full picture: identity, parameters, your sizing, the metrics, and the capital footprint — enough to reconstruct the reasoning behind the portfolio without opening the app.
Native Engine Portfolio
Native Engine Portfolio downloads {name}.cfe-portfolio.json — the
Workbench's own interchange format and the only one that round-trips.
What's inside (and preserved on re-import):
- portfolio name and account size
- every strategy with its contract count, enabled/disabled state, and your alias if you renamed it
- your column layout for the composition table
What to know:
- Import lives in the Builder header; the imported portfolio arrives unsaved so you review before committing.
- Strategies from your own private uploads don't transfer to another account — they're skipped on import with a note. Database strategies transfer 1:1.
- The parser rejects OptionsApp files with a clear message — that format is a one-way execution hand-off, not a portfolio container.
Use Native for backups before big experiments, for moving between your own devices, and for sharing a construction with someone who can then inspect it with their own account size and judgment — which beats sharing a screenshot of an equity curve every day of the week.