Dukascopy is a Swiss-regulated broker known for its proprietary JForex platform and tight spreads on major pairs. If you trade through Dukascopy’s client portal or JForex desktop, your closed trade history lives inside their reporting system — not automatically in your journal. This guide shows you how to export that data and get it into PipJournal so you can run actual analysis on your trades.
This guide is written for beginner-to-intermediate traders with an active Dukascopy account. By the end, you will have your complete trade history in PipJournal with correct P&L figures ready for review.
Step 1: Log Into the Dukascopy Client Portal
Go to the Dukascopy client portal at my.dukascopy.com and sign in with your account credentials. If you trade through JForex desktop, you can also access reports directly from the platform, but the client portal gives you the cleanest CSV export.
Once logged in, locate the Reports section in the left navigation panel. This is separate from the live trading interface — it is the back-office area where account statements, transaction history, and closed position reports are stored.
If you have multiple accounts under the same login (for example, a live account and a demo account, or multiple strategy accounts), confirm you are viewing the correct account before proceeding.
Step 2: Export Your Trade History as CSV
Inside the Reports section, select Closed Positions or Trade History (the label varies slightly depending on your account type). Set the date range to cover the period you want to import. For a first-time import, start with the past 90 days to keep the file size under 5 MB.
Choose CSV as the export format. Dukascopy also offers PDF and Excel formats, but CSV is required for PipJournal’s import flow.
Click Generate or Export and save the file to your computer. A typical 3-month export for an active trader on EUR/USD (0.1–1.0 lot sizes, 20–40 trades per month) will be between 50 KB and 300 KB.
Step 3: Review and Clean the Export File
Open the CSV in any spreadsheet application. Confirm these columns are present before importing:
| Required Column | Typical Dukascopy Label |
|---|---|
| Instrument / pair | Symbol |
| Open time | Open Time |
| Close time | Close Time |
| Direction | Type (Buy/Sell) |
| Lot size | Amount (in millions or lots) |
| Open price | Open Price |
| Close price | Close Price |
| P&L | Gross P/L or Net P/L |
| Commission | Commission |
Remove any header rows, subtotal rows, or summary rows that appear below the trade list. PipJournal’s importer expects one trade per row with consistent column positions throughout the file.
Dukascopy reports lot size in millions of base currency by default (e.g., 0.1 = 100,000 units = 1 standard lot). Note this so you can confirm the mapping in the next step.
Step 4: Import the CSV into PipJournal
In PipJournal, go to Import Trades and select CSV / Custom Broker as the import type. Upload your cleaned Dukascopy CSV.
PipJournal will display a column mapping screen. Match each Dukascopy column to the correct PipJournal field:
- Set P&L Type to “Currency” (not pips) — Dukascopy reports P&L in account currency (USD, CHF, or EUR depending on your account)
- Confirm lot size units: if Dukascopy shows 0.1 and you traded 1 standard lot, set the lot multiplier to 10 so PipJournal stores it as 1.0
- Map the Commission column so PipJournal can calculate net P&L accurately
Click Preview Import. Review the first 5–10 rows to confirm that instrument names, directions, and P&L figures look correct before committing the full import.
Step 5: Verify and Tag Your Trades
After the import completes, cross-reference three metrics against your Dukascopy account statement:
- Total number of closed trades imported
- Gross P&L for the period (should match your Dukascopy statement to within a few cents due to rounding)
- Net P&L after commissions
If the totals match, your import is clean. If there is a discrepancy greater than 1%, re-check the lot size multiplier and P&L type settings.
Once verified, add setup tags to categorize your trades by strategy. Tag by session (London, New York, Asian) to see if your entry timing differs across sessions — this is often where Dukascopy traders find their edge is session-specific.
Pro Tips
- Dukascopy includes swap (rollover) charges as a separate line item in some export versions. If you see duplicate-looking rows, check whether they are swaps rather than additional trades — PipJournal has a “swap” field to store this separately.
- Export in your account’s base currency (not a converted currency) to avoid rounding errors caused by mid-session FX conversion rates.
- For JForex algorithmic strategies, each strategy generates its own order IDs. Use PipJournal’s tag field to label which strategy generated each trade batch, then filter by tag in the analytics dashboard.
- If you trade Dukascopy’s SGDFX or exotic pairs, verify that PipJournal recognizes the instrument name. You may need to manually rename exotic pairs from Dukascopy’s notation (e.g., “SGDHKD”) to the standard format.
- Run the import again after month-end to capture any late-settling swap adjustments that Dukascopy posts after the trading period closes.
Common Mistakes to Avoid
-
Importing the PDF statement instead of CSV. The PDF cannot be parsed by PipJournal’s importer. Always select CSV as the export format — the data is identical but machine-readable.
-
Misidentifying lot size units. Dukascopy reports in millions by default, so 0.01 means 10,000 units (0.1 mini lot). If you import without adjusting the multiplier, every position will appear 10x larger than it was, making P&L-per-lot metrics meaningless.
-
Skipping the column mapping review. Clicking through the mapping screen without verifying each field is the most common cause of import errors. Spend 60 seconds on the preview — it saves hours of correcting bad data later.
-
Importing overlapping date ranges. If you export January–March and then February–April, PipJournal will duplicate the February and March trades. Import sequential, non-overlapping date ranges only.
-
Ignoring the commission column. Dukascopy charges commissions on ECN accounts that can reach $35 per million (0.35 pips equivalent on a standard lot). Omitting this column inflates your apparent profit factor and makes your strategy look better than it is.
How PipJournal Helps
Once your Dukascopy trades are imported, PipJournal’s analytics dashboard automatically calculates your expectancy per trade, win rate by instrument, and average R:R across your entire history — data Dukascopy’s own reporting does not surface in a usable format. The tag filtering system lets you isolate specific setups or currency pairs and compare performance across them. PipJournal also tracks your exit timing relative to session closes, which is particularly relevant for Dukascopy traders who run strategies around the Swiss and European session opens. The one-time $179 lifetime license means you pay once and import as many Dukascopy exports as you need going forward.
People Also Ask
Does Dukascopy export MT4 or MT5 reports?
Dukascopy supports MT4 connectivity through a bridge, so if you trade via MT4 you can export the standard MT4 HTML statement instead. For native JForex accounts, use the client portal CSV export described in this guide.
What date range should I select when exporting?
Export no more than 3 months at a time to keep file sizes manageable. For a full history import, do multiple exports and import each CSV separately into PipJournal.
Why do some trades show zero P&L after import?
This usually happens when the P&L column is in account currency but PipJournal reads it as pips. Double-check the column mapping step and confirm the "P&L Type" is set to "Currency" during import.
Can I import Dukascopy PAMM or strategy trades?
Yes. PAMM sub-accounts generate the same CSV format from the client portal. Export and import each sub-account separately so PipJournal keeps the records distinct.