To export from E*TRADE: log in, open Accounts → Transactions, set your date range, then use the download arrow (top right). Since the Morgan Stanley systems merge (February 2026), third-party import guides report the file now arrives as an XLSX workbook in the Morgan Stanley layout — not the old E*TRADE CSV. (TradeLog’s 2026 guide describes a CSV-or-XLSX download under Accounts → Activity, so check which options your account shows.) If a tool or template built before 2026 rejects the file, it’s not you: the format changed underneath it.
E*TRADE’s export used to be a boring, reliable CSV. Then the Morgan Stanley integration landed and replaced it: a new file type and new column headers, according to import guides and user reports. The clicks are still easy — the surprises are in the file. Here’s the current flow, what changed, and how to keep multi-year records consistent across the break.
Key Takeaways
- Export path: Accounts → Transactions → date range → download arrow (top right).
- The break: since the February 2026 systems merge, import guides report a Morgan Stanley-style XLSX with new headers — pre-merge CSV import templates no longer match.
- The quirk (user reports): some cells may contain line breaks — check row counts after any XLSX→CSV conversion.
- The horizon: E*TRADE doesn’t publish a figure; the transaction tool’s lookback is shorter than the statement archive — check your account’s earliest available date and archive statements as you go.
Where is the export in E*TRADE?
On the Transactions page — same place as before the merge; only the file changed. The steps, on the website:
- Log in at etrade.com and open Accounts → Transactions or Accounts → Activity, the label TradeLog’s 2026 guide gives for the post-merge view (exports run per account).
- Set the date range you need.
- Click the download arrow in the top right and confirm — the file downloads immediately.
- Expect an .xlsx workbook in the post-merge layout, per current import guides. Older saved exports (pre-Feb 2026) remain valid records — they’re just in the legacy CSV format.
Keep the era boundary visible in your records: name files etrade-2025-legacy.csv vs etrade-2026-q1.xlsx and don’t merge the two formats into one sheet blindly — the columns don’t line up. One conversion pass per era, checked against a few known transactions, keeps the history trustworthy.
The 3 things that trip people up
| Trap | What happens | Fix |
|---|---|---|
| Old import templates break | Tools built for the pre-2026 CSV reject or misread the new XLSX | Look for an updated E*TRADE/Morgan Stanley import in your tool — or map the new headers once, manually |
| Line breaks inside cells (reported) | Some users report cells with line breaks, which can split a transaction across rows on conversion | Open in Sheets/Excel first and check row counts before converting |
| Assuming it’s still CSV | Scripts expecting .csv fail on the .xlsx silently | Export → open → Save As CSV yourself if a tool insists on CSV |
What’s in the file — and what to watch
One row per event — trades, dividends, interest, transfers — with dates, symbols, quantities, prices and amounts, under new header names (per import guides) — map them once against a few known transactions. The habits that keep it useful: don’t round fractional share quantities (those decimals are your cost basis), check the first and last dates in every file before archiving it, and keep taxable and retirement accounts in separate files — they live in different tax universes.
Isn’t my 1099 enough for taxes?
For filing, mostly yes. For proving, no. The consolidated 1099 covers what this broker knows for that year — but wash sales that span brokers, transferred-in basis, and any later IRS questions are yours to substantiate. Your exports are that evidence trail — and with a format break mid-history, keeping both eras cleanly labelled matters more here than at most brokers.
Using more than one platform? Our free US broker export cheat-sheet covers the export path, format and trap for 8 US platforms on one page. For the walkthroughs: Fidelity (90-day cap), Schwab (silent row limit) and Robinhood (generate-and-wait).
Keep every year’s export permanently — both the legacy CSVs and the new XLSX files. Broker interfaces and formats change without notice (this page documents exactly such a change); your saved files are the record that survives. Avex AI provides software and educational content, not investment or tax advice. Avex AI is not affiliated with or endorsed by E*TRADE or Morgan Stanley.
Because of the Morgan Stanley systems merge in February 2026: import guides report the transaction export now downloads as an XLSX workbook in a new layout. Pre-merge exports were CSV — both remain valid records, just different formats from different eras.
Templates and tools built for the pre-2026 E*TRADE CSV don’t match the new headers. Check whether your software has an updated E*TRADE/Morgan Stanley import; otherwise map the new columns once manually and save that mapping.
Check your Activity page: TradeLog’s 2026 guide describes a CSV-or-XLSX choice there. If you only get XLSX, open it in Excel or Google Sheets and Save As CSV — and verify the row count matches the number of transactions.
E*TRADE doesn’t publish a figure. The statement archive reaches back further than the transaction tool; check the earliest date your account offers and keep the PDFs as you go.
The 1099 covers filing for that broker and that year. Cross-broker wash sales, transferred cost basis and any later IRS questions need your own records — the exports are how you prove your numbers.
Sources & references
- TradeLog — Importing from CSV or XLSX, E*TRADE / Morgan Stanley (2026) (third-party guide: merge date 9 February 2026, Accounts → Activity, CSV or XLSX)
- TradeLog — Importing from a CSV file, E*TRADE Financial (legacy, pre-merge) (third-party)
- IRS — Topic 409: Capital Gains and Losses
- IRS — Publication 550: Investment Income and Expenses (wash sales)
Last verified: 31 October 2026. E*TRADE publishes no page documenting the export format, path or history limits; the file format, headers and line-break behaviour above come from third-party guides and user reports and were not reproduced on a live account.