Risk Disclosure

Futures and forex trading contains substantial risk and is not for every investor. An investor could potentially lose all or more than the initial investment. Risk capital is money that can be lost without jeopardizing one’s financial security or lifestyle. Only risk capital should be used for trading and only those with sufficient risk capital should consider trading. Past performance is not necessarily indicative of future results.

Hypothetical Performance Disclosure

Hypothetical performance results have many inherent limitations, some of which are described below. No representation is being made that any account will or is likely to achieve profits or losses similar to those shown; in fact, there are frequently sharp differences between hypothetical performance results and the actual results subsequently achieved by any particular trading program. One of the limitations of hypothetical performance results is that they are generally prepared with the benefit of hindsight. In addition, hypothetical trading does not involve financial risk, and no hypothetical trading record can completely account for the impact of financial risk of actual trading. for example, the ability to withstand losses or to adhere to a particular trading program despite trading losses are material points that can also adversely affect actual trading results. There are numerous other factors related to the markets in general or to the implementation of any specific trading program that cannot be fully accounted for in the preparation of hypothetical performance results and all which can adversely affect trading results.

Journalit
Journalit

Getting Started

WelcomeWhat's NewInstallationQuick StartAuthentication

Core Features

Home ViewDashboardAccount ManagementManual EntryTrade NotesSetupsReview SystemLayout BuilderSession ModeTrade ImportTrade LogNavigation SidebarSettings
Trade Sync Guides
Broker Export Guides
Interactive BrokersTradovateTradeZeroTradingView Paper TradingFX ReplayBybitHyperliquidBlofinSierra ChartMotiveWaveATASTrading TechnologiesRithmicMetaTrader HTMLTopstepXDeepCharts
DownloadSign In
Docs/Broker Export Guides/Rithmic

Rithmic Trade History Export Guide

Continue with Journalit

Trading platformsCompare direct sync and supported imports.CSV trade importImport broker exports into your journal.Obsidian pluginUse Journalit inside your vault.Trading journal templateSee the default vault structure.MetaTrader journalUse MT4 sync or import MetaTrader statements.

Trading Technologies

Previous Page

MetaTrader HTML

Next Page

On this page

OverviewWhat Journalit ExpectsExport Trades From RithmicOpen Order HistorySelect The Right Account And FilterMake The Required Columns VisibleExport The CsvImport The Original FileQuick Validation Before ImportPlatform NotesTroubleshootingNext Steps

Export Rithmic trades for Journalit from R | Trader Pro Order History as CSV. This guide shows the required visible columns because Rithmic only exports what is currently shown in the grid.

Bottom line

Export from Order History, filter for completed or filled rows, make sure the required columns are visible first, and then save the CSV unchanged.

Last verified

Export path and validation guidance last reviewed in June 2026. Rithmic layouts can vary by introducing broker or prop-firm setup, so confirm the visible columns before every first import.

Overview

Order History source

Journalit expects execution-level export data from R | Trader Pro's Order History view.

Completed rows only

Use completed or filled rows rather than working, cancelled, or unrelated order states.

Visible columns matter

If a required field is hidden in the grid at export time, it will not be present in the CSV.

Manual mapping fallback

If your Rithmic export column names differ, use manual mapping and validate a small date range before importing a full history.

What Journalit expects

Correct screen
Correct row type
Required columns
Expected file type
Support mode
Do not use

Most common mistake

If the preview is empty or key values are missing, check the visible columns first. In Rithmic, hidden columns are not exported.

Export trades from Rithmic

Open Order History

Open R | Trader Pro and navigate to Order History.

Select the right account and filter

Choose the account you want to export and filter the grid so it shows Completed or Filled rows for the date range you want.

Do not rely on working or cancelled-only rows for Journalit imports.

Make the required columns visible

Open the grid's Add/Remove Columns control and ensure these fields are visible before export.

Minimum required visible columns:

  • Buy/Sell or Side
  • Symbol
  • Qty Filled
  • Avg Fill Price
  • Update Time, Update Time (PDT), or Fill Time

Recommended optional columns:

  • Status
  • Account
  • Order Number
  • Commission Fill Rate or Commission
  • Remarks or Position Disposition

Export the CSV

Use the available Export or Clipboard action to create the CSV file from that prepared grid.

Import the original file

Upload the CSV into Journalit without editing it first.

Quick validation before import

Completed fills included

The grid was filtered to filled or completed rows rather than inactive order states.

Required columns visible

Buy/Sell or Side, Symbol, Qty Filled, Avg Fill Price, and a fill/update timestamp were all visible before export.

Expected date range

The export covers the actual trading window you want to reconstruct in Journalit.

Unedited CSV

You are importing the original export rather than a file that was cleaned up in a spreadsheet first.

Platform notes

Troubleshooting

Next steps

Import the Rithmic file

Continue to the Trade Import guide to map, preview, and import the exported order-history file into Journalit.

Trade import for your trading journal

See how broker exports become mapped, validated, and imported into Journalit.

Obsidian trading journal workflow

See how imported trades become notes, screenshots, dashboards, and reviews in your own vault.

All broker export guides

Compare supported broker export paths and choose the right file before importing.