You can bring Rithmic trade activity into TradeDeck with a screenshot or a CSV file whose columns you map yourself. TradeDeck does not have a dedicated Rithmic CSV profile. A file from R Trader Pro should not be treated as a supported broker preset just because it has a CSV extension.
Choose the route that fits the records you have. Snap Trade creates a draft from an image. Custom CSV lets you connect the columns in your export to the fields in your journal. Both routes need a review against the source before you save.
Start with the right records
Keep the original export or screenshot available while you work. You need the traded contract or symbol, direction, quantity, entry price, and entry date. Closed trades also need the exit details. Check whether your file describes individual executions or already combines those executions into completed trades.
That distinction matters. A buy execution followed by a sell execution may be two parts of one trade. A completed trade row may already contain both an entry and an exit. Combining completed rows as if they were separate fills can misrepresent your trading activity.
Choose the intended trading account in TradeDeck before importing. For Custom CSV, prepare a file for one broker account at a time. The column mapper does not offer an Account target, so an account column is not a substitute for choosing the destination account. Keep copied activity from different accounts separate.
Option one: use Snap Trade
Open Snap Trade from your journal and choose a readable screenshot of the trade details. Include the symbol, side, quantity, prices, and timestamps where possible. A screenshot that only shows an account balance or daily total does not contain the details needed to reconstruct your trades.
Snap Trade can handle multiple trades in one screenshot, including scale-in and scale-out fills. That does not guarantee that every Rithmic screen layout will parse correctly. Treat the result as a draft and compare it with the original image.
Check the account, contract, direction, quantity, entry, and exit. Review any missing fields before saving. If the image is cropped, too small, or unclear, use a clearer screenshot or switch to Custom CSV. Do not fill gaps by guessing what happened.
Free includes three Snap Trades per month. Pro includes unlimited Snap Trade use. Only successful parses count toward the allowance. The draft still needs your review even when the image was parsed successfully.
Option two: map a Custom CSV
Choose your account and file
Open the CSV import flow in the journal. Choose the destination account, then select your exported CSV. If the file is not recognized as a supported broker format, use Custom CSV and review the column mapping.
Export menus and available columns can differ between trading platforms. This guide does not assume a particular R Trader Pro menu or export layout. Check the file itself before mapping it, and use the platform's documentation if you need help obtaining your records.
Connect the required fields
The mapper needs these fields to create a trade:
| TradeDeck field | What to use from your export |
|---|---|
| Symbol / Ticker | The actual traded symbol or futures contract |
| Entry Price | The execution or entry price, not a daily account total |
| Quantity / Contracts | The filled quantity or completed trade size |
| Entry Date | The timestamp for the entry or execution |
Header matching ignores case, spaces, and punctuation when suggesting a mapping. Suggestions are a starting point. Confirm that each selected column contains the right values. A column called Type may describe an order type rather than an asset class or trade direction, so it is not safe to infer its meaning from the name alone.
Map Side explicitly when your file supplies it. Check that buys and sells, or longs and shorts, appear correctly in the preview. Missing direction can fall back to quantity information and a buy default. A positive quantity by itself does not establish that the original trade was long.
Add the available details
For completed trade rows, map Exit Price and Exit Date as well. You can also map Asset Type, P&L, Fees / Commissions, and Notes. Options fields include Strike, Expiration, and Call / Put when those details are present in the file.
For futures, preserve the contract identifier and inspect the asset type and point value in the preview. Do not assume an unfamiliar symbol was recognized correctly. Compare the previewed P&L with the source and check whether fees explain any difference between gross and net results.
Confirm the time zone
Use the wizard's Time zone used by your broker export setting. Choose the zone used by the source timestamps, which may differ from the zone you use to view your journal. Timestamps with an explicit offset keep that offset.
Check an entry whose time you know before accepting the preview. Also confirm ambiguous dates against the original records. A date such as 04/05 can be read differently depending on the export's format. Do not proceed while the date or time is uncertain.
Decide whether to combine fills
If each row is an individual execution, the Combine individual fills into trades option can match buys and sells into positions. Review the resulting entries, partial exits, and remaining open quantity. The presence of that option does not mean TradeDeck has a Rithmic-specific parser.
Leave that option off when each row already describes a complete trade. If you need a worked explanation of entries and partial exits, read the FIFO matching guide. Its Tradovate column names and order-id handling apply to that format, not automatically to a custom Rithmic export.
Review before you save
The Review step shows Ready to import and Need correction counts. Read any notices about unread or rejected rows too. A smaller preview than expected may mean some source rows could not be parsed, not that all records were successfully combined.
Use Edit columns to correct a mapping. Compare direction, contracts, prices, timestamps, and open or closed status with your source. An Open result should reflect a position that actually remains open in the records you supplied. Missing exits or incomplete exports need correction before saving.
After importing, read the saved and skipped counts and inspect the journal. Do not assume every custom file has the stable identifiers needed to detect duplicates across different exports. Check existing entries before importing the same activity again, especially if you already logged it through Snap Trade.
Keep the original records until you have reconciled the result. Once the journal matches the source, add the context a broker export cannot supply: your setup, your notes, and what you want to review about the trade.