Robinhood made options accessible to a whole generation of traders, but it was never designed to be a record-keeping system. Once you start selling covered calls and cash-secured puts in there, the gap shows fast: the app tells you what happened today, not where a ticker's cost basis actually sits after a year of premium, assignments, and rolls. To get that picture, you need your transaction history somewhere that understands option selling — and the fastest way to move it is a CSV.
That's exactly what MyATMM's AI Import is for. Robinhood hands you a CSV of your account activity; MyATMM reads every row, decides whether each line is an option trade, a stock trade, a dividend, or a cash movement, and writes it into your portfolio — no manual data entry, no spreadsheet formulas to babysit. This walkthrough covers the whole flow: where to find the export inside Robinhood, the drag-and-drop import, stacking multiple files, how probable duplicates are handled, and the reconciliation pass that uses a one-click fix to balance your account.
The export itself is buried a little, but it's quick once you know where to look. Inside Robinhood, you're after the statements area, not the live positions screen.
Once that file is sitting in your Downloads folder, you're done on the Robinhood side. Everything from here happens inside MyATMM, and it really is as simple as dragging the file onto the page.
Here's the wrinkle worth knowing up front. Robinhood tends to limit these statement exports to roughly one month per file, and it may not let you reach all the way back to the very beginning of your account. If you've got years of activity, that means you're not pulling one tidy file — you're pulling a stack of them.
That sounds tedious, but it doesn't slow the import down at all, because MyATMM is built to swallow files one after another. You could have thirty separate monthly CSVs and just drop them in back-to-back; the system imports each one and folds it into the same portfolio. So the export limit is a Robinhood annoyance, not a MyATMM one — and as you'll see in the reconciliation step, even if you can't reach your earliest trades, there's a clean way to square the account anyway.
Inside MyATMM, the tidiest way to handle a bulk import is to aim it at a fresh portfolio. In the walkthrough, the import lands on a brand-new Robinhood portfolio — a clean slate with nothing in it yet. Starting clean means there's nothing for the import to collide with, so the counts and dollar amounts you get back reflect exactly what came out of the CSV.
With your portfolio selected, head to the Tools menu and open the Import / Export screen. You'll land on the AI Import tab, which is the starting point for every broker import — CSV or screenshot. Then it's just a matter of finding those statement files you downloaded and getting ready to drop them in.
Take the first CSV — start with the smallest if you've got a few — and drag it straight onto the upload zone. No file picker, no wizard. MyATMM does a quick read-only pre-parse and shows you the row count almost instantly; in the demo, the first file comes back at 30 rows.
When the count looks right, click Parse. That's the step that does the real work: MyATMM walks every row, identifies the transaction type, maps Robinhood's CSV columns onto its own data model, builds out your ticker list, and writes the transactions into the portfolio. A moment later the result page returns with a structured summary of what just landed.
The summary after each parse is your first real picture of what happened. It breaks the import down by transaction type, with both counts and aggregated dollar amounts:
It's a clean, at-a-glance confirmation that the file went where it was supposed to. You can see immediately whether the option and dividend counts line up with what you'd expect, and how many fresh tickers Robinhood just seeded into the portfolio.
Because Robinhood makes you export in chunks, importing back-to-back is the normal path, not the exception. After the first file lands, click to import another, drop the next CSV, and parse again — it stacks straight into the same portfolio. In the demo, a second, slightly larger file goes in right after the first.
And this is where overlap becomes a question: what happens when two monthly files share some of the same transactions? MyATMM watches for it. After each import it compares incoming rows against what's already in the portfolio and flags matches as probable duplicates rather than blindly creating a second copy. In the walkthrough, the bigger second file reports 30 probable duplicates — precisely the rows that overlapped with the first file. The summary still shows you the full breakdown of options, stocks, dividends, and ledger entries, with the duplicates called out separately so nothing is silently dropped or double-counted.
You can keep going as long as you like — import these back-to-back-to-back, as many files as you've got.
Every import is reversible and inspectable. The View Import Details screen lets you review what came in, clean up any duplicates, fix anything that looked off in the source file, or — if you grabbed the wrong CSV entirely — delete the whole batch and start over from zero. Because actions are scoped to a single import batch, you can undo a mistake without disturbing the rest of your portfolio.
There's a dedicated Import History walkthrough coming that covers this screen in full — batch timestamps, source files, duplicate management over time. For a first bulk seed, it's enough to know the safety net is there: nothing you import is permanent or unfixable.
Once everything's in, head to the dashboard and you'll likely see a reconciliation notice. Don't treat it as an error — it's the system telling you exactly what's out of balance, and on a bulk Robinhood import it's expected.
The classic example is right there in the video. The import contains sell-to-close transactions for stocks, but there are no matching buy-to-open transactions to pair them with. Why? Because you couldn't export far enough back in time to grab the original purchase. The database has the exit but not the entry, so it can't balance the position on its own.
That's all the reconciliation notice is saying: it needs the buy-to-open side to offset the sell-to-close side you imported. (Worth noting — if you'd been shorting, those opening trades would be sell-to-open rather than buy-to-open, and the same logic applies in reverse.) It's not missing every old transaction, just the specific opening legs that pair with the closes already in the system.
Here's the part that makes this painless. Rather than making you hunt down old confirmation emails or hand-enter missing trades, MyATMM gives you an Easy Fix button. Click it, and the system generates the missing buy-to-open transaction for each unmatched sell-to-close — pumping in exactly the rows it needs so the data set is balanced for those specific tickers.
Once that's done and the account is squared to zero, you've established a credible starting point. From there, tracking is purely incremental: a handful of trades on a daily or weekly basis, dropped in as you make them. Keeping the account in sync from that point is far easier than the initial seed, and you'll probably never hit the unmatched-close problem again — it's almost exclusively a one-time, bulk-historical-import thing.
The whole reason this workflow exists is that the alternative doesn't scale. Covered call tracking spreadsheets tend to break down not because the math is wrong, but because the manual data-entry burden makes them impossible to keep current. Miss one assignment or one roll and every calculation after it drifts.
Bulk import flips that. You pay a one-time cost — pull the monthly CSVs, run the imports, hit Easy Fix on the reconciliation — and after that you're only logging the few trades you actually placed this week. That's why the system stays accurate over time. If you've been wrestling with a wheel strategy spreadsheet up to now, this is the moment you stop maintaining formulas and start running a tool that actually understands how to track covered calls and cash-secured puts as a single income strategy.
After the import and the Easy Fix, your generic Robinhood export has become something purpose-built: a per-ticker view of cost basis with option premium folded in, a portfolio summary that tracks realized and unrealized P&L, and a transaction grid where every new trade adjusts the cost basis the way option sellers actually need.
For wheel strategy traders, that's where it starts paying off. Robinhood's native history doesn't connect a cash-secured put, the assignment that follows, and the covered calls you write afterward — they're just separate line items in a list. MyATMM treats them as legs of one income cycle on a single underlying, and it treats a roll as one continuous position whose cost basis moves with you rather than two unrelated trades. That's the difference between a pile of fills and an actual picture of where you stand.
Options trading involves risk and is not suitable for all investors. Past performance does not guarantee future results. This content is for educational purposes only and should not be considered financial advice. Always consult with a qualified financial advisor before making investment decisions.
Further reading: How to import Tradier CSV transactions with AI — a clean, single-file CSV import walkthrough in the same series.
MyATMM provides purpose-built cost basis tracking for option sellers, with the flexibility to track covered calls, cash-secured puts, and wheel strategy positions.
Track up to 3 tickers completely free forever. No credit card required.
Create Your Free Account TodayBuilt for covered calls, cash-secured puts, and the wheel strategy