How to Import OANDA Trades into PipJournal

Importing historical trades is the fastest way to get real data into your journal without re-entering every position by hand. This guide walks beginner-to-intermediate OANDA traders through exporting their transaction history, cleaning the file, importing into PipJournal, and tagging trades for analysis — start to finish in under 15 minutes.

Step 1: Export Your Trade History from OANDA

Log into your OANDA fxTrade account at fxtrade.oanda.com. Navigate to My Account → Statement. Set your desired date range — OANDA allows a maximum of 180 days per export. Select Transaction History (not the account statement PDF), then choose CSV as the format and click Download.

The file will contain columns including Transaction ID, Date/Time, Type, Instrument, Units, Price, Realized P/L, Balance, and Financing. Keep all columns intact. Do not open the file in Excel and save — this can corrupt date formatting. If you need to inspect the file, use a plain-text editor or Google Sheets with “import as text” enabled.

For accounts older than 180 days, repeat the export in multiple batches (e.g., Jan–Jun, Jul–Dec) and import each file separately. PipJournal deduplicates by Transaction ID, so overlapping date ranges will not create duplicate trades.

Step 2: Format the CSV for Import

Open the CSV in a text editor and scan the first and last 5 rows. OANDA sometimes appends a footer row with account totals — delete any row where the Type column reads Balance, Deposit, or Withdrawal. These are funding events, not trades, and will cause import errors if left in.

Confirm that the Date/Time column uses the format YYYY-MM-DD HH:MM:SS (e.g., 2026-04-15 14:32:07). If OANDA has exported in a regional format (DD/MM/YYYY), use Find and Replace in a text editor to normalize it before importing. Check that Units values are positive for buys and negative for sells — OANDA uses signed units to indicate direction, which PipJournal reads correctly.

Save the file with UTF-8 encoding. File size is typically 10–50 KB per 180-day window, well within PipJournal’s 10 MB upload limit.

Step 3: Import the File into PipJournal

In PipJournal, go to Trades → Import → Broker Import. Select OANDA from the broker list. Click Upload CSV and select your prepared file.

PipJournal’s OANDA parser automatically maps the following fields:

OANDA Column	PipJournal Field
Instrument	Currency Pair
Units	Lot Size (converted)
Price	Entry / Exit Price
Realized P/L	Net P&L (account currency)
Date/Time	Open / Close Timestamp
Financing	Swap / Rollover

Click Preview Import to see the first 10 trades before committing. Confirm that pair names (e.g., EUR_USD) have resolved correctly and that lot sizes look right — OANDA records units (100,000 units = 1 standard lot), and PipJournal converts to lots automatically. Click Confirm Import to finalize.

Step 4: Verify Imported Trades

After import, run a spot-check against your OANDA account statement. Pick 3 closed trades at random and compare:

• Entry and exit price — should match to the pip (4th decimal for majors, 2nd for JPY pairs)
• Net P&L — should match OANDA’s Realized P/L column within $0.01 (rounding from pip conversion)
• Duration — verify open and close timestamps match your OANDA statement

If P&L figures are off by more than 2 pips’ worth, check whether your OANDA account is denominated in a non-USD currency (GBP, EUR, AUD base accounts are common). PipJournal uses the exchange rate embedded in the OANDA export to convert, but you may need to set your account base currency in Settings → Account for the conversion to apply correctly.

Step 5: Tag and Categorize Your Trades

Raw imported trades have no tags — they’re just price data. Before running any analysis, spend 10–20 minutes tagging your trades. At minimum, apply:

• Session tag: London, New York, Asian, or Overlap (use the open/close timestamp to determine)
• Setup tag: Your strategy name or pattern (e.g., breakout, trend-pullback, range-fade)
• Result tag: plan-followed or deviated — even a rough classification surfaces discipline patterns

Use PipJournal’s bulk-edit feature to tag multiple trades at once — select trades by date range or pair, then apply a tag to the entire selection. This cuts tagging time from 30 minutes to under 5 minutes for a 90-day import.

Once tagged, check the weekly trade review process to build a consistent review habit around your new data.

Pro Tips

• Export OANDA data every Sunday before the weekly candle closes — this keeps your journal current without large catch-up imports.
• If you trade multiple OANDA accounts (live + demo, or multiple live accounts), import them into separate PipJournal workspaces to keep analytics clean.
• OANDA’s financing charges accumulate daily on overnight positions. Review your imported swap costs in PipJournal’s cost-analysis view — traders who hold positions 3+ days often find swap is eroding 10–20% of gross P&L.
• For position sizing analysis, confirm your average lot size in PipJournal matches your OANDA risk log — discrepancies usually mean you imported units instead of lots (check broker settings).
• After import, sort trades by session and compare your win rate per session. Most OANDA retail traders discover their worst session immediately — usually Asian session overtrading.

Common Mistakes to Avoid

1. Opening the CSV in Excel before importing. Excel auto-formats date columns and truncates leading zeros in instrument codes, corrupting the file. Always use a plain-text editor to inspect the raw export.

2. Importing without setting your account base currency. If your OANDA account is in GBP and you leave PipJournal’s currency setting at USD, every P&L figure will be off by the GBP/USD rate — roughly 20–25% currently. Set your base currency in Settings first.

3. Skipping the verification step. Importing 180 days of trades and trusting the totals without spot-checking means any parsing error compounds silently. Verify at least 3 trades manually before drawing conclusions from the analytics.

4. Ignoring financing rows. Deleting all non-trade rows is correct, but some traders accidentally delete legitimate trade rows with unusual Type values. Only delete rows where Type is Deposit, Withdrawal, Balance, or Interest — leave Trade and Close Trade rows intact.

5. Importing duplicate date ranges. If you export Jan–Jun and then export Jan–Dec, the Jan–Jun trades will be duplicated unless PipJournal’s deduplication catches them by Transaction ID. Always note your last import date and start your next export from that date.

How PipJournal Helps

PipJournal’s OANDA importer handles the full transaction lifecycle — entries, partial closes, rollovers, and swap charges — so nothing falls through the cracks. Once your trades are in, the analytics dashboard breaks down performance by currency pair, session, and setup tag, making it possible to identify which OANDA instruments are actually profitable for your strategy. The trade review workflow then gives you a structured process to act on those insights weekly. For traders building a complete picture of their edge, the trading edge measurement guide shows how to use PipJournal’s data to calculate expectancy and R-multiple distribution from real trade history.