On this page 6 sections
Importing a CSV file is easy.
Importing external tick history correctly is more interesting.
The difference is everything surrounding the prices:
- What symbol specification are you using?
- Which time zone are the ticks in?
- What clock does your broker use?
- Does that offset change with daylight saving time?
- Are the resulting candles aligned with the broker you intend to simulate?
MetaTrader 5 gives you the tools for a manual workflow.
TickArk's Broker-Aware workflow is designed to automate the parts where mistakes are easiest to make.
Part 1 — The standard manual MT5 method
MetaTrader 5 imports external price history into custom symbols.
You do not overwrite your broker's server-side symbol.
Step 1: Connect to the broker you want to model
Open the MT5 terminal for the broker whose trading environment you want to approximate.
This matters because the existing broker symbol provides a useful specification template.
Step 2: Open the Symbols window
From Market Watch, open Symbols and find the broker instrument you want to use as the reference.
For example:
XAUUSD
Step 3: Create a custom symbol
Choose Create Custom Symbol.
MetaTrader can copy properties from an existing symbol.
Use the broker's own instrument as the source.
Give the custom symbol a unique name such as:
XAUUSD_HIST
Do not reuse the exact broker symbol name.
Step 4: Review the specification
Copying the original instrument is much safer than starting from an empty generic symbol.
Relevant properties can include:
- digits,
- point size,
- tick size,
- contract size,
- chart mode,
- profit currency,
- margin currency,
- calculation method,
- quoting sessions,
- trading sessions.
These parameters can affect strategy-test behaviour.
Step 5: Prepare your historical ticks
Your imported dataset should have a consistent timestamp order and the required price fields.
For quote data, Bid and Ask are particularly important.
Do not assume that the source time zone automatically matches your broker.
Step 6: Import the tick file
Select your custom symbol and open its Ticks section.
Choose the import function and load the historical file.
MetaTrader provides a Shift option that can move imported timestamps by a specified number of hours.
This is useful for straightforward fixed-offset conversions.
It is also where a common problem begins.
The DST problem
Suppose your historical source is stored against a fixed global reference clock.
Your broker, however, operates on a server convention whose UTC offset changes during the year.
A single static +2 or +3 assumption across the entire history can create incorrect candle boundaries around the transition.
That can alter:
- H1 bars,
- H4 bars,
- daily candles,
- session filters,
- indicator calculations,
- time-based EA logic.
The tick prices themselves may be valid while the clock interpretation is wrong.
This is one of the hardest mistakes to notice visually across years of history.
Step 7: Verify the resulting symbol
Do not stop because MT5 accepted the file.
Check:
- beginning and end of history,
- tick count,
- several ordinary trading days,
- weekend boundaries,
- known market closures,
- dates around daylight-saving transitions,
- resulting M1/H1/D1 candles.
Then use Every tick based on real ticks in the Strategy Tester.
Part 2 — TickArk Broker-Aware MT5 Import
TickArk approaches the workflow from the opposite direction.
Instead of asking the user to manually decide what a generic export should look like, TickArk starts with the target broker environment.
1. TickArk connects to the target MT5 environment
The selected broker symbol becomes the reference.
TickArk reads the symbol information required to prepare a compatible historical testing symbol rather than assuming that every XAUUSD, EURUSD or index CFD has the same specification.
2. The export is adapted to the broker symbol
The goal is to preserve the historical market data while aligning the custom symbol with relevant characteristics of the target broker instrument.
This removes much of the repetitive manual configuration.
3. Time mapping is treated as a data problem
TickArk does not reduce historical time alignment to a blind “pick GMT+2 or GMT+3” choice.
The workflow uses broker data to determine and validate how historical ticks should map into the target MT5 server-time environment.
4. DST transition periods receive explicit verification
This is an important part of the process.
TickArk checks candles produced from the tick history against broker candles around days when time conventions change.
Why?
Because those are precisely the dates on which a permanently fixed offset can appear correct for months and then become wrong.
The system can therefore validate the mapping against observable broker candle structure instead of trusting a single global offset assumption.
5. The result is prepared for MT5 testing
The result is a custom historical-data environment prepared around the selected broker symbol.
The purpose is not to claim that an independent historical feed becomes identical to the broker's proprietary historical tick stream.
It does not.
The purpose is to make the transformation broker-aware:
- broker-aware symbol configuration,
- broker-aware time mapping,
- broker-aware DST validation.
That is a fundamentally different objective from simply exporting a generic CSV.
Manual import or Broker-Aware import?
Manual import remains valuable.
It gives advanced users complete control and is supported directly by MetaTrader 5.
For occasional experiments, it may be all you need.
Broker-Aware import becomes attractive when you:
- work with long histories,
- maintain multiple brokers or terminals,
- import many symbols,
- want reproducibility,
- do not want to manually maintain timezone/DST assumptions,
- need consistent research environments.
Automation matters most when it removes decisions that are easy to get subtly wrong.
The important principle
Historical data does not exist independently of the environment in which you test it.
Prices are one layer.
Symbol specification, sessions and time are another.
A robust import workflow needs to care about both.
PRIMARY SOURCES