Capital.com is a CFD and forex broker with a proprietary web and mobile platform — which means it does not use MetaTrader and requires its own export workflow. This guide walks you through exporting your Capital.com trade history and importing it into PipJournal so you can start analyzing your performance data.

This guide is aimed at beginner to intermediate traders who are setting up PipJournal for the first time or migrating historical trades from Capital.com.

Step 1: Log In and Access Your Trade History

Log in to your Capital.com account at the web platform (not the mobile app — exports are only available via desktop browser).

In the main navigation, look for the Portfolio section. Under Portfolio, select History from the sub-menu. This displays all your closed positions, ordered by close date.

By default, Capital.com shows the last 30 days. You will need to adjust the date filter before exporting. Set your desired start and end dates — for a first import, use your account opening date as the start date to capture all historical trades.

Step 2: Export Your Trade History as CSV

With your date range set in the History view, look for the Download or Export button — it typically appears as a download icon in the top-right corner of the History table.

Click it and select CSV format. Capital.com will generate the file and prompt you to save it. The export includes: instrument, direction (buy/sell), open price, close price, lot size (units), open time, close time, gross P&L, swap, and net P&L — all fields PipJournal needs for a full import.

If you are importing more than 12 months of history, run multiple exports in separate date range blocks (e.g., Jan–Jun and Jul–Dec) and save each file separately.

Step 3: Review the CSV Before Importing

Open the exported file in Excel, Google Sheets, or any spreadsheet application. Perform a quick sanity check before uploading:

  • Row count: Count the number of trade rows and compare it to the closed positions count shown in Capital.com’s History view for the same date range.
  • Date range: Confirm the earliest and latest close dates in the file match your export settings.
  • P&L column: Spot-check 2-3 trades against their values in Capital.com. Net P&L in the CSV should match the “Net Profit/Loss” column in the platform.
  • No blank rows: Remove any blank rows at the top or bottom of the file that could cause parse errors during import.

Do not rename column headers — PipJournal’s Capital.com template expects the original header names from Capital.com’s export.

Step 4: Import the CSV into PipJournal

In PipJournal, go to Settings > Import Trades (or the Import button in your trade log).

Select Capital.com from the broker list. This loads the correct column mapping template for Capital.com’s CSV format. Upload your CSV file.

PipJournal will display a preview of the mapped fields — instrument, direction, open/close prices, lot size, and P&L. Review this preview to confirm fields are aligned. If you exported multiple date-range files, import them one at a time. PipJournal detects and skips duplicate trades based on trade ID and close timestamp, so re-importing an overlapping file will not create duplicates.

Step 5: Verify and Tag Your Imported Trades

After the import completes, PipJournal shows a summary: trades imported, duplicates skipped, and any rows with errors.

Cross-check the following against Capital.com:

  • Total trade count for the imported period
  • Gross P&L — sum of all net P&L values should match your account statement
  • Instrument names — Capital.com uses names like “EURUSD” and “Gold” rather than “XAUUSD”; rename non-standard instruments in PipJournal if needed for consistent filtering

Once verified, apply setup tags to your imported trades. Tagging by strategy (e.g., “breakout”, “pullback”) and session (London, New York) unlocks PipJournal’s breakdown analytics. Even retroactive tagging of 50-100 historical trades gives you meaningful edge data.

Pro Tips

  • Capital.com reports P&L in your account currency. If you trade a USD account, pip values will be in USD — no conversion needed in PipJournal. If you trade in GBP or EUR, set your account currency in PipJournal’s account settings before importing.
  • Capital.com CFD lot sizes are expressed in units (not standard lots). For a 1,000-unit EURUSD position, PipJournal will store this as 0.01 lots. Verify this conversion in the import preview.
  • For traders using Capital.com’s mobile app exclusively, switch to the desktop platform just for exports — the mobile app does not have a CSV export option.
  • If you trade indices (UK100, US500) alongside forex on Capital.com, tag them with a separate “indices” label in PipJournal. This keeps your forex-only analytics clean and accurate.
  • Schedule a monthly export from Capital.com rather than waiting until you have years of history to import. Smaller, regular imports are faster to verify.

Common Mistakes to Avoid

  1. Using the MT4/MT5 import template for Capital.com files. Capital.com does not use MetaTrader format. Selecting the wrong broker template will cause column mismatches and import failures. Always select Capital.com explicitly.

  2. Importing without checking the date range. If your CSV covers January to June but you meant January to December, you will end up with incomplete data and misleading equity curve readings. Confirm the date range in the History view before exporting.

  3. Ignoring swap costs in P&L reconciliation. Capital.com includes overnight financing fees in net P&L. If your PipJournal total looks off by a consistent amount, check whether swap is being double-counted or excluded in the import mapping. Review the how to track swap costs approach.

  4. Not tagging imported trades before analyzing. Running analytics on untagged historical imports gives you aggregate numbers with no context. Spend 20-30 minutes tagging imported trades by setup type before reading your equity curve — the insights are far more actionable.

  5. Importing all instruments into a single account without segmentation. If you trade forex, indices, and commodities on Capital.com, consider creating separate PipJournal accounts (or using tags) to segment them. Mixed-instrument analytics distort per-pip and lot-size calculations that are calibrated for forex.

How PipJournal Helps

PipJournal’s Capital.com import template handles the broker’s native CSV format without requiring manual column mapping, making the first import take under five minutes. Once trades are in, PipJournal’s analytics dashboard calculates your profit factor, win rate by session, average R:R, and drawdown metrics automatically — giving you a complete performance picture your Capital.com account history page cannot provide. The tag filtering system lets you isolate performance by setup type or instrument so you can identify exactly which trades are driving your results. PipJournal’s one-time $179 lifetime access means there are no ongoing subscription fees to justify — import your history once and use the analytics for as long as you trade.

People Also Ask

Does Capital.com export in MT4 or MT5 format?

No. Capital.com uses its own proprietary platform and exports trade history as a CSV file — not in MetaTrader format. Use PipJournal's Capital.com import template, not the MT4/MT5 importer.

How far back can I export Capital.com trade history?

Capital.com typically allows you to export up to 12 months of trade history per export. For older trades, use multiple date range exports and import them separately into PipJournal.

Why does my P&L look different after importing?

Capital.com displays P&L inclusive of overnight fees (swap costs). PipJournal may separate swap from gross P&L. Check that swap values are mapped correctly in the import settings.

Can I import CFD trades alongside forex trades?

Yes. PipJournal accepts all Capital.com instruments. Tag non-forex CFDs separately (e.g., "indices", "commodities") so your forex-specific analytics remain clean.

What should I do if some trades are missing after import?

Cross-check your CSV row count against Capital.com's closed positions count for the same date range. If rows are missing, re-export with a narrower date range and re-import the gap.

Was this article helpful?

P
Written by

PipJournal Team