Importing your data
The Import page: bring your own backtest CSVs in as first-class strategies, and live trade logs in for Reality Check.
The Import page (left nav, under Catalog) brings your own data into the Workbench. Two boxes, two destinations:
| Upload | Accepts | Becomes |
|---|---|---|
| Backtest | CSV exports from supported backtesting platforms (portfolio or single-strategy) | A strategy under the Mine scope — a first-class strategy with computed metrics |
| Live trade log | CSV / XLSX / XLS logs from supported automation platforms | Data for Reality Check (available on Overdrive at launch) |
The router is forgiving: drop an Excel file on the Backtest box and it's automatically routed to the live-log side (spreadsheet logs are the automation platforms' native export shape). Detection happens server-side, per file.
What happens to an imported backtest
Your upload becomes a Mine strategy: it appears in the Strategy Browser under the Mine scope (and inside All), gets the same per-period metrics as database strategies, and mixes freely with them in the Portfolio Builder — combined KPIs, correlation, Monte Carlo, all of it. The one boundary: Mine strategies are private to your account, so they don't travel inside shared Native Engine Portfolio files.
For thin uploads, mind the data-quality flag in the Browser: metrics computed on very few trading days are unreliable, and the table marks such rows.
Managing imports
Your imports below the upload boxes lists every dataset with its trade count and an expandable per-file strategy breakdown. Deleting a dataset removes its strategies from Mine (portfolios that used them will tell you).
Not this page
- Shared portfolio files (
.cfe-portfolio.json) import via the Portfolio Builder's own Import button — see Saving, loading & sharing. - OptionsApp files don't import anywhere — that export is one-way.