MetaTrader files that matter during a server move
For most migrations, the important data is inside the terminal data folder, not just the program folder on the desktop. If you copy only `terminal64.exe`, your templates and EA settings will usually stay behind.
- Templates: chart layouts saved as `.tpl` files.
- Presets: EA or indicator input sets saved as `.set` files.
- Expert Advisors and indicators: the `Experts`, `Indicators`, `Libraries` and `Include` folders under `MQL4` or `MQL5`.
- Profiles: groups of open charts, symbols and attached tools.
- Files and logs: optional, but useful if your EA reads CSV, JSON or local config files.
MT4 and MT5 use the same migration idea
Open MetaTrader on the old server and use File → Open Data Folder. That avoids guessing the roaming profile path and ensures you export the correct terminal instance.
- MT4: usually copy `MQL4`, `templates`, `profiles` and any supporting files.
- MT5: usually copy `MQL5`, `Profiles`, `Templates` and `Files` if your robot reads local data.
- Multiple terminals: repeat for each broker instance because each installation can use a different data folder hash.
That process works whether you are moving to a Windows VPS for MetaTrader or to a dedicated MetaTrader server.
What each MetaTrader item does after the move
| Item | Typical folder | Why it matters | Common mistake |
|---|---|---|---|
| Templates | `templates` or `Templates` | Restores chart colors, indicator stack and visual layout. | Copying profiles only and wondering why charts open blank. |
| Presets | Usually inside `MQL4` or `MQL5` subfolders, or a custom storage folder | Restores exact EA inputs without manual re-entry. | Forgetting `.set` files and attaching the EA with default settings. |
| EAs and indicators | `MQL4` or `MQL5` | Required for attached robots and custom tools to load. | Copying only compiled `.ex4` or `.ex5` files while missing libraries or includes. |
| Profiles | `profiles` or `Profiles` | Reopens the same chart groups after restart. | Transferring templates but not the profile that references them. |
| Files | `Files`, `Common\Files` or EA-specific folders | Needed if the strategy reads external data, licenses or exported reports. | Ignoring file-based dependencies and thinking the EA itself is broken. |
Step-by-step transfer checklist
This is the safe sequence for moving an active MetaTrader environment to a new server with minimal confusion.
Freeze the old setup
Pause live trading, note broker account numbers, and record which terminals, charts and EAs are running on the old machine.
Open the real data folder
Inside each terminal, click File → Open Data Folder. Copy the actual terminal data contents instead of guessing folders from memory.
Export the key folders
Back up `Profiles`, `Templates`, `MQL4` or `MQL5`, and any EA-specific `Files` or preset directories to a ZIP archive.
Install MetaTrader on the new server
Install the same platform version and broker terminal first, then launch once so the new data folder structure exists.
Replace or merge the folders
Close MetaTrader, copy your saved content into the new data folder, then reopen the terminal and compile or refresh if needed.
Verify before going live
Check account login, symbols, presets, DLL permissions, AutoTrading, VPS time sync and whether every chart loads the correct robot.
Pre-live validation after the copy
- Open every required chart and confirm the intended EA is attached.
- Load your saved `.set` file if the EA does not retain the expected inputs.
- Enable AutoTrading and review each EA property window for DLL or import permissions.
- Confirm the terminal is logged into the right broker account and server.
- Review the Experts and Journal tabs for missing file, indicator or permission errors.
- Run a short dry check on demo or with trading disabled before returning the account to normal operation.
If templates or EAs do not appear
- Template missing: you likely copied the wrong template folder or restored it into the wrong terminal instance.
- EA not loading: check whether the custom indicator, library or include file that it depends on was also copied.
- Preset not found: save the `.set` file again from the old terminal and import it manually into the EA inputs window.
- Robot shows a smiley but does nothing: review trading hours, broker permissions, market watch symbols and AutoTrading status.
- File read error: inspect `Files` and `Common\Files` because some EAs read from shared folders outside the chart folder structure.
When a normal VPS is not enough for the new setup
A simple migration can turn into a workload upgrade. If you are moving more terminals, more charts or more backtesting tasks than before, it may be better to change server class during the transfer.
1 to 5 live terminals
A Windows VPS is usually fine when you run a small number of MT4 or MT5 terminals with moderate EA load and no heavy optimization.
See VPS optionsMany terminals or CPU-heavy EAs
If the new server will host many charts, copy trading, PAMM workflows or demanding robots, dedicated CPU and RAM headroom are usually safer.
Compare dedicated serversMT5 optimization and remote agents
If the move also includes Strategy Tester agents or large optimization batches, use infrastructure designed for MT5 backtesting instead of forcing it onto a small trading VPS.
Explore MT5 backtest farmUseful Winservers.NET pages while planning the move
Windows VPS for MetaTrader
For small to medium live trading setups that need stable Windows RDP access.
Open VPS pageDedicated server for MetaTrader
For more terminals, higher CPU load and fewer shared-resource limits.
Open dedicated pageMT5 backtest farm
For users who combine live trading migration with MT5 optimization or remote agents.
Open backtest farm pagePOW EA VPS
If your migration target is a dedicated environment for POW EA or similar EA-first workflows.
Open POW EA VPS pageMetaTrader FAQ
Useful if you need clarifications on platform setup, terminals and common hosting questions.
Open MT4/MT5 FAQQuestions traders ask before moving MetaTrader
Do I need to copy the whole MetaTrader installation folder?
No. The most important part is the terminal data folder opened from File → Open Data Folder. That folder usually contains the templates, profiles, EAs, indicators and presets that matter during the transfer.
Where are MetaTrader preset files stored?
Preset files are usually saved as `.set` files inside the terminal data structure or in a folder chosen by the user during export. If you rely on saved EA inputs, back up those `.set` files explicitly instead of assuming they are embedded in the EA.
Why did my EA transfer but not start trading on the new server?
The usual reasons are disabled AutoTrading, missing custom indicators or libraries, missing file dependencies, different broker symbols, or EA settings that were not restored from the original preset file.
Can I move several MT4 or MT5 terminals to one server?
Yes, but server sizing matters. A few live terminals usually fit well on a MetaTrader VPS, while larger multi-terminal setups often work better on a dedicated trading server with more CPU and RAM headroom.
Need help moving your MetaTrader environment to a new server?
We can help you choose between a VPS, a dedicated MetaTrader server or an MT5 backtesting setup, then verify the migration path for your charts, presets and EAs.
