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 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.
You need a clean export before Journalit can import anything reliably. These guides focus on the exact export path for each broker or platform, plus the mistakes that usually break imports.
Best default
Export as CSV when the platform gives you a choice. If it only supports Excel or a supported HTML statement workflow, Journalit can handle that as well.
If your platform has demo, live, futures, or sub-accounts, export from the exact account you want to analyse.
Closed-trade history is usually more useful than raw fills if the platform offers both.
Do not rename or clean up the file before import unless a guide explicitly tells you to.
It is easier to filter inside Journalit than to re-export because your first file was incomplete.
These are the guides most likely to solve the first search people make when they are trying to move broker history into Journalit.
Use the exact Interactive Brokers Flex Query CSV settings Journalit expects, including Orders, not Executions.
Export futures trade history from the TopstepX Trades module before importing into Journalit.
Export Bybit Trade History as CSV instead of Closed P&L or the wrong account-statement view.
Export Hyperliquid Trade History as CSV and avoid losing older trades to the 10,000-row limit.
Use the Orders report export rather than the incompatible Performance report.
Export the Paper Trading Order History CSV instead of another TradingView dataset.
Export completed orders from R | Trader Pro with the visible columns Journalit needs.
Use Flex Query CSV exports for stocks, options, futures, and forex history.
Export futures trade history from the Trades module as CSV.
Export futures trade history from the Orders tab.
Export stock trade history in CSV format.
Download Paper Trading order history from TradingView.
Export trade history from the Analytics page in CSV format.
Export Bybit trade history or transaction history with the correct source.
Export Hyperliquid perpetual trade history with the correct wallet and tab.
Export futures trade history for import into Journalit.
Generate a Trade Activity Log export with the required fields.
Use the execution export and preserve the workbook structure.
Export the original Excel workbook Journalit expects.
Export TT fills data with a complete history range.
Use R|Trader Pro completed-order export.
Export closed futures trades from Strategy Report Trade List as CSV.
Download the Terminal account export and import the original trades.csv execution history.
Export an English HTML statement from MetaTrader 4 or MetaTrader 5 and import the original report with the dedicated adapter.
Some exports use local time, others use exchange time. Keep that in mind when validating imported trades.
Manual edits often change number formats, timestamps, or delimiters without you noticing.
If you are migrating multiple brokers, import them separately first so validation is easier.
Store the original export somewhere safe in case you need to re-import or troubleshoot later.
Use the broker guide first if your platform is listed. If your broker is not listed, Journalit can still import many CSV-style files through manual mapping, but unsupported broker formats may need cleanup or a new adapter.
Import a small date range before migrating years of history, then compare the imported trades against the source export.
If your broker is not listed, start from a simple CSV shape and map the columns manually.
Remove balances, repeated headers, and report noise before mapping unsupported CSV files.
If a supported workflow is missing or a broker changed its export screen, ask in Discord before guessing with a large import.
See how broker exports become mapped, validated, and imported into Journalit.
Map your export correctly, preview the data, and import it into Journalit.
See how imported trades become notes, screenshots, dashboards, and reviews in your own vault.
Ask in Discord if your platform is not listed yet or if the export changed.
