How to Back Up MT4 and MT5 Profiles Before Moving to a VPS
Move your MetaTrader setup without losing charts, templates, presets, or Expert Advisor files.
The safest way to move MT4 or MT5 to a VPS is to back up the full MetaTrader data folder before you copy anything to the new server. That keeps your profiles, templates, indicators, EA files, and custom presets together and avoids rebuilding your trading workspace by hand.
Quick answer
Close MetaTrader, open File → Open Data Folder, copy the whole data folder to a backup archive, and separately note your broker logins, server names, and any EA license details before you start the VPS migration.
Why backup first
A VPS move is easy to reverse only if you keep the full trading workspace
Many traders think a VPS move only means reinstalling the terminal and logging in again. In practice, the risk is losing small but important parts of the setup: chart profiles, saved template layouts, .set files, custom indicators, Expert Advisor folders, log paths, and any files your EA reads from MQL4/Files or MQL5/Files.
If you run only one or two terminals, a standard Windows VPS for MetaTrader is usually enough. If you plan to run many terminals or heavier automation, look at a dedicated server for MetaTrader. If your main workload is research and optimization, a separate MT5 backtest farm is the better fit.
Backup table
What to copy before moving MT4 or MT5 to a VPS
Use this checklist before you uninstall anything or connect to the new server. If in doubt, copy more rather than less.
| Item | Where to find it | Why it matters | Recommended action |
|---|---|---|---|
| Profiles and chart layouts | profiles | Restores open charts, symbol groups, and workspace structure. | Copy the folder as-is. |
| Templates | templates or template files in the data folder | Keeps your indicators, colors, and chart formatting. | Copy all template files. |
| Expert Advisors, indicators, scripts | MQL4 or MQL5 | Required for the terminal to load your trading logic. | Copy the full MQL folder, not just individual EAs. |
| Presets and strategy files | Commonly inside MQL4/Presets or MQL5/Profiles | Preserves input values so you do not rebuild settings by memory. | Export and copy every .set file you still use. |
| EA support files | MQL4/Files or MQL5/Files | Some EAs store state, reports, or CSV inputs there. | Copy the full folder and verify permissions after the move. |
| Broker logins and server names | Manual note outside MetaTrader | Saved passwords may not migrate cleanly or may be re-entered for security reasons. | Record account number, broker server, and password separately. |
Practical setup
Practical checklist before the VPS migration starts
This is the minimum process for a clean move. It works for discretionary setups, EA terminals, and most broker installations.
Close every MT4 and MT5 terminal
Do not copy files while the terminal is still open. MetaTrader can still be writing logs, config files, and profile changes.
Open the real data folder
Inside each terminal, use File → Open Data Folder. That is safer than guessing the location from memory.
Create one backup archive per terminal
Zip the complete data folder and label it by broker, account type, and platform so you know what belongs where.
Export presets you still trust
Open the EA inputs and save current settings to .set files. This is useful even if the folder backup is complete.
Write down credentials and licenses
Keep broker login details, investor passwords, VPS credentials, and any third-party EA activation notes outside the platform.
Restore on the VPS, then test before going live
After you copy the backup to the new Windows server, reopen the terminal, log in, check charts, and confirm EAs load without errors.
Migration details
A simple restore workflow that avoids most MT4 and MT5 migration issues
On the new VPS, install the same platform version if possible, open its data folder, and compare the folder layout before you paste the backup. For most setups, you should copy your backed-up data folder contents into the matching data folder on the VPS and then restart MetaTrader.
After the first launch, verify the basics in this order: charts load, templates appear, custom indicators are visible, EAs attach correctly, and preset files can be loaded. If you run multiple broker terminals, restore and test them one by one instead of changing every instance at the same time.
Useful pages while planning the move
Troubleshooting
Common mistakes after restoring MetaTrader on a VPS
Charts open but the layout is wrong
This usually means the profile or template files were not copied to the correct data folder.
- Reopen the terminal data folder from inside MetaTrader.
- Check whether you restored to the same MT4 or MT5 instance.
- Confirm the profiles and template files are present.
EAs or indicators are missing
The MQL tree may be incomplete, or the terminal may need a restart and recompilation.
- Verify the full MQL4 or MQL5 folder was copied.
- Restart the terminal after restoring files.
- Open MetaEditor if a custom file needs to compile again.
Saved logins do not work
Some credentials may need to be entered again for security reasons or broker-side validation.
- Use the broker server name you wrote down before the move.
- Re-enter the main password manually.
- Check whether the broker blocks the old session after the new login.
The VPS works, but the terminal feels overloaded
The migration succeeded, but the server size may be too small for the real workload.
- Reduce chart count and unused indicators first.
- Move heavy multi-terminal loads to a larger plan.
- Use dedicated hardware if the setup keeps growing.
Decision support
When a normal VPS is not enough for your MetaTrader setup
Keep using a VPS when the workload is straightforward
- One to five MT4 or MT5 terminals
- Standard EA workloads and 24/5 uptime needs
- RDP access is enough and CPU load stays moderate
Choose dedicated or backtesting infrastructure for heavier jobs
- Many terminals, copy trading, or team access
- POW EA or resource-hungry Expert Advisors
- Optimization and research better suited to an MT5 backtest farm
FAQ
Frequently asked questions
What is the safest way to back up MT4 or MT5 before moving to a VPS?
The safest method is to close the terminal, open File to Open Data Folder, and copy the entire data folder before you move anything to the VPS. Also save your current preset files and keep broker login details in a separate note.
Should I back up only the Expert Advisors or the whole MetaTrader data folder?
Back up the whole data folder, not only the Expert Advisors. Profiles, templates, indicators, presets, and support files can be just as important as the EA files themselves during a VPS migration.
Do saved broker passwords always transfer to the new VPS?
No. Some saved logins may need to be entered again after the move, so record your broker server name, account number, and passwords before restoring the terminal on the VPS.
When should I use a dedicated server instead of a normal MetaTrader VPS?
Use a dedicated server when you run many terminals, heavier Expert Advisors, copy trading workloads, or need more isolated CPU and memory resources than a standard VPS usually provides.
Need help moving MT4 or MT5 to a Windows VPS?
Tell us how many terminals, brokers, and EAs you run. We can point you to the right VPS, dedicated server, or backtesting setup before you migrate.
