Saving, loading & sharing

Portfolios are cheap — save liberally and A/B them in Compare.

Save & Save As

• Save Portfolio saves the current state: strategies with their contract counts, on/off flags and aliases, the account size, and your column layout. The header shows the last-saved time.
• Save As creates a new portfolio from the current state (default name: "…(copy)") — the duplicate flow. Use it before experiments: duplicate, hack on the copy, compare both.

Renaming

The portfolio name in the header is directly editable — click it (or the pencil), type, done. No dialog.

Load

Load opens a dialog with two sections:

• Saved portfolios — every portfolio you've saved, with strategy count, account size and save date. Deleting is a deliberate two-step: the trash icon asks for confirmation inline before anything is removed.
• Uploaded backtests — datasets you've brought in via Import. Loading one pulls all of its strategies in as a fresh, unsaved portfolio named after the dataset.

Import (shared portfolio files)

The header's Import button accepts a Native Engine Portfolio .json — the file the Export menu produces. That's how portfolios travel between accounts: export the file, send it, the other side imports it and gets the same strategies, contract counts, on/off states and aliases as an unsaved portfolio to review and save.

Two boundaries worth knowing:

• Strategies that came from someone's private uploads can't travel — they're skipped on import with a note (the database strategies all transfer).
• OptionsApp export files can't be re-imported — that format is a one-way hand-off for execution, not a portfolio container. The app rejects them with exactly that explanation.