How to Import FBS Trades into PipJournal

FBS is one of the largest retail forex brokers by client count, particularly popular in Southeast Asia, Africa, and the Middle East. If you trade on FBS and want to turn your raw trade history into actionable analytics, you need to get that data into a journaling system. This guide walks you through exporting your FBS trade history and importing it into PipJournal — from the correct export settings to verifying your data after import.

This guide is written for beginner to intermediate traders who are setting up their journaling workflow for the first time.

Step 1: Export Your Trade History from FBS

FBS accounts run on either MetaTrader 4 or MetaTrader 5 depending on your account type. Standard and Cent accounts use MT4; ECN and Zero Spread accounts use MT5. The export process is nearly identical on both platforms.

In MetaTrader 4:

1. Open MT4 and click the Terminal tab at the bottom (Ctrl+T if hidden).
2. Select the Account History tab.
3. Right-click anywhere in the history panel and choose All History to load your complete record.
4. Right-click again and select Save as Report — choose Detailed Report for the most complete data.
5. Save the file as an .htm or .html file to your desktop.

In MetaTrader 5:

1. Open MT5 and go to View > Terminal (Ctrl+T).
2. Click the History tab.
3. Right-click and set the date range to cover all your trades.
4. Right-click again and select Save as Report in HTML format.

If you prefer to export from the FBS Personal Area, log in at the FBS website, navigate to My Accounts > Trade History, filter by date range, and download the CSV export. The CSV format is also accepted by PipJournal.

Step 2: Prepare the Export File

Before uploading, spend 60 seconds verifying the file to avoid a partial import.

Open the exported file and confirm:

• The date range covers the full period you want to analyze. A common mistake is exporting only the last 3 months when you have 2 years of data.
• The file includes closed trades only — open and pending orders are not importable.
• The account currency is visible in the report header. If your FBS account is in EUR or another currency, note this so you can verify P&L conversion after import.
• The file size is reasonable — an account with 500 trades should produce an HTML file of roughly 200-500 KB. A suspiciously small file usually means the date filter was too narrow.

If you trade multiple FBS accounts (e.g., a Standard account and an ECN account), export each separately and import them one at a time in PipJournal.

Step 3: Import the File into PipJournal

1. Log into PipJournal and go to Settings > Import Trades or click Import from the main dashboard.
2. Select MetaTrader 4 or MetaTrader 5 as the broker/platform — FBS does not have a dedicated importer since it uses standard MT platforms.
3. Upload your .htm, .html, or .csv file.
4. PipJournal will parse the file and display a preview showing the number of trades detected, the date range, and the total P&L. Verify these numbers match your FBS statement before confirming.
5. Click Confirm Import to commit the trades to your journal.

For CSV imports from the FBS Personal Area, you may be prompted to map column headers (symbol, open time, close time, lots, open price, close price, profit). Match each column to the correct field — this only needs to be done once per format.

Step 4: Verify and Tag Your Trades

After import, run a quick accuracy check:

• Compare the total net P&L in PipJournal against your FBS account statement for the same period. A difference of more than 1-2% likely indicates a currency conversion discrepancy or a missing trade.
• Check that lot sizes are correct. FBS Cent accounts report lots in cent lots (1 cent lot = 0.01 standard lot), which can inflate position sizes if not interpreted correctly.
• Confirm pair symbols are recognized. FBS uses standard forex naming (EURUSD, GBPJPY) so mapping should be automatic.

Once accuracy is confirmed, start tagging. Apply setup type tags to each trade — even a simple tag like “breakout” or “reversal” immediately unlocks filtered analytics. Add session labels (London, New York, Asian) to identify which sessions produce your best results.

Pro Tips

• FBS Cent accounts report profits in cents, not dollars. A trade showing “+1500” profit is $15.00, not $1,500. PipJournal handles this automatically if you select the correct account type during import, but always verify.
• If you use FBS Copy Trading and also place manual trades, export and import only the manual trades. Copy trades have different risk profiles and will distort your personal analytics if mixed in.
• Set up a recurring monthly export habit — export on the 1st of each month covering the prior month. This keeps your journal current without requiring a full re-import every time.
• The MT4 “Detailed Report” format is preferable to “Statement” because it includes individual trade comments, which you can use to carry over notes from your platform.
• After your first import, use entry timing analysis immediately — FBS records open and close times with second-level precision, which gives PipJournal enough data to show your performance by hour of day.

Common Mistakes to Avoid

1. Exporting only recent history. Selecting “Last 3 months” when setting up your journal means you lose years of baseline data. Always select “All History” on your first import to establish a complete baseline.

2. Importing Cent account lots as standard lots. If your Cent account shows lot sizes like “100” for what is actually a 1-lot equivalent, your position sizing analytics will be wrong. Confirm with FBS support which lot unit your account uses before importing.

3. Not separating multiple accounts. Mixing a demo account import with a live account import produces meaningless analytics. Keep each account as a separate journal or use PipJournal’s account filtering to view them independently.

4. Skipping the post-import verification step. Assuming the import is correct without checking P&L totals means errors silently corrupt your analytics. A 5-minute check against your broker statement prevents this.

5. Tagging trades weeks after import. Waiting to tag defeats the purpose of journaling. Tag each trade immediately after import while the context is still fresh — at minimum, add the setup type and whether the trade followed your rules.

How PipJournal Helps

PipJournal’s MT4 and MT5 importers handle FBS trade history with no manual data entry — lots, pips, P&L, open/close times, and currency pairs are all parsed automatically. Once imported, the analytics dashboard breaks down your performance by pair, session, setup type, and day of week, so you can see exactly which conditions produce your best results on FBS markets. The tagging system lets you filter any metric by setup label — useful for traders running multiple strategies across FBS’s different account types. For traders building a structured review process, PipJournal’s weekly review workflow pairs naturally with a monthly FBS export routine.