Excel & Native Portfolio

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.

Your choice here also flips the on-screen Format switch, so the table and your exports stay in the same language.

Either way you get a real .xlsx with one row per enabled strategy, a metadata block, the standing hypothetical-performance disclosure above the table (a forwarded file full of backtested performance must carry the same disclosure the app shows), and — once the portfolio's analytics have computed — a second sheet, Portfolio Metrics, with the portfolio-level KPI block.

The two formats write different strategy tables:

• CashFlow Engine format — 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.
• ROPS format — the community's own table, sorted by MAR: Entry Time · Strategy (the ROPS name) · Contracts · Trading Days · P&L Total · P&L (Formatted) · Final Value (reconciled to your configured account size) · CAGR % · Max DD % · MAR Ratio · Avg Margin Required (theo) · Premium Collected (theo) · Strategy Type · EMA · Side · Premium ($) · Stop Loss %. Theoretical dollar figures are sized by your contract counts.

Either way 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 Engine'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.

Daily Log & Trade Log CSV

Both logs under the Analytics charts export separately, each via a CSV button in its own header:

• Daily Log CSV — one row per trading day: date, equity_usd, pnl_usd, pnl_pct, drawdown_pct, torq (the day's TORQ gamma-index reading, empty when unavailable).
• Trade Log CSV — one row per trade, including the columns the on-screen table hides for width: opened_at, closed_at, strategy, structure, legs, contracts, premium, pnl_usd, pnl_pct, margin_req_usd, funds_at_close_usd, stop_loss_pct, reason, origin.

Unlike the Excel export, these are raw files: plain numbers rather than formatted strings, percentages as fractions, full ISO timestamps, and chronological order — built to be read by a spreadsheet or a pandas.read_csv() rather than to be looked at. Full column meanings are in Daily Log & Trade Log.