ThinkOrSwim exports are reliable when you pull the right panel. Go to Monitor, then Activity and Positions, then account statement or filled orders, and export CSV for the exact date range you need.
Before importing, open the file and confirm key columns exist. You need symbol, side, quantity, fill price, and execution time. If the platform exports options legs separately, keep those rows intact and let your journal group strategies where supported.
Common import issue number one is timezone mismatch. ThinkOrSwim can export local time while your journal may assume UTC or account timezone. If your intraday review looks shifted, adjust timezone settings before deeper analysis.
Common issue number two is duplicate partial fills. Avoid manually deleting these unless you are sure they are true duplicates. Most of the time they represent actual execution fragments and should be retained.
For daily workflow speed, use screenshot logging for single trades and CSV for weekly backfill. This hybrid method keeps your journal current and still gives complete history.
Fast alternative when you only need to log one trade
If your columns do not map automatically, create a saved import preset once. After that, each future upload usually takes less than a minute.
If you are switching from ThinkOrSwim to futures-focused platforms, review Tradovate import and Rithmic import. For setup discipline, pair imports with revenge trading controls.
Practical Workflow for How to Import Trades from ThinkOrSwim (Step by Step)
Start each session by opening Dashboard > Journal > Log Trade and writing one sentence for your primary setup before the bell. For example, if you trade NQ, note that you only take A+ opening range breakouts between 9:30 AM and 10:30 AM ET with a max daily loss of $600. This tiny pre-commitment prevents random clicks when volatility spikes. After the session, compare each executed trade to the sentence you wrote before the open and score rule compliance out of 10. This section is specific to How to Import Trades from ThinkOrSwim (Step by Step) (import-trades-thinkorswim) with a unique review angle.
When you review execution quality, use fixed dollar examples so mistakes are obvious. A two-contract ES trade with a 4-point stop risks $400, while the same structure in NQ can risk $320 to $400 depending on stop width and fill quality. If slippage adds 1.25 points on NQ during a fast CPI candle, that is another $50 per contract, which materially changes your expectancy. Journaling those numbers helps you decide whether to reduce size on high-impact news days like FOMC or Non-Farm Payrolls. This section is specific to How to Import Trades from ThinkOrSwim (Step by Step) (import-trades-thinkorswim) with a unique review angle.
A useful end-of-day note should include setup, context, and behavior. Example: "SPY level break at 523.40 failed after reclaim, exited early for -0.6R because breadth diverged and I hesitated on stop movement." That one line is much better than writing "bad trade" because it identifies the exact decision point. Over 20 trades, these details show whether losses come from strategy edge decay or from avoidable execution errors. This section is specific to How to Import Trades from ThinkOrSwim (Step by Step) (import-trades-thinkorswim) with a unique review angle.
Build one weekly review block every Saturday: 1) filter by ticker, 2) filter by setup, 3) filter by time-of-day, and 4) rank your top three mistakes by frequency. A trader might discover that TSLA breakout longs after 11:30 AM ET have a 34% win rate while the same setup in the first hour wins 57% with better R multiples. That leads to a precise rule update: stop trading late-session breakouts unless they align with higher-timeframe trend and volume expansion. Review-driven constraints like this usually improve consistency faster than adding new indicators. This section is specific to How to Import Trades from ThinkOrSwim (Step by Step) (import-trades-thinkorswim) with a unique review angle.
For prop-firm style risk management, track both gross and take-home results. If one trade makes $900 gross across three copied accounts with an 85/15 split, your net is $765 before commissions and platform fees. If fees total $27 and slippage costs another $18, actual take-home is $720, not $900. Keeping those numbers in your journal prevents false confidence and makes payout planning realistic. This section is specific to How to Import Trades from ThinkOrSwim (Step by Step) (import-trades-thinkorswim) with a unique review angle.
Use scenario journaling after emotional trades. Example: after a -$350 stop-out on ES, you immediately re-enter without a new signal and lose another -$420; label it explicitly as revenge behavior and tag the trigger ("anger after first loss"). Then write the prevention rule in plain language: "After any full stop on ES, wait 10 minutes and require a fresh structure break plus volume confirmation." Turning emotional errors into written if/then rules is one of the highest-ROI improvements for discretionary traders. This section is specific to How to Import Trades from ThinkOrSwim (Step by Step) (import-trades-thinkorswim) with a unique review angle.
Add a short process audit every month using concrete metrics: win rate, average R, median hold time, and compliance score. Suppose your win rate stays near 46%, but average R rises from 1.2R to 1.7R and compliance improves from 62% to 79%; that is real progress even if weekly P&L still feels uneven. This keeps you focused on controllable behaviors instead of reacting to short-term variance. Professional traders survive by tightening process, not by chasing perfect prediction. This section is specific to How to Import Trades from ThinkOrSwim (Step by Step) (import-trades-thinkorswim) with a unique review angle.
If you are teaching yourself a new setup, run a 20-trade sample with fixed position sizing and no parameter changes mid-sample. For example, test only SPY first-pullback longs with $150 risk per trade, 1.5R first target, and stop to breakeven after target one. Document each trade with screenshot, execution score, and one sentence on context so you can decide with evidence whether the setup belongs in your playbook. This structure reduces curve-fitting and keeps your journal honest.