Inventory the EA before migration
- Platform: MT4/MQL4 or MT5/MQL5, terminal build and broker account server.
- Workspace: symbols, timeframes, input parameters and required chart templates.
- Dependencies: indicators, approved libraries, external connections and license activation.
- Operations: when the EA should run, what logs indicate health and how it is restarted.
Confirm requirements with the EA developer. A Windows VPS and the built-in MetaQuotes virtual-hosting service are different environments; in particular, MetaQuotes documents restrictions on DLL calls in its built-in service. Check compatibility with the environment you actually intend to use.
Permissions should be deliberate
Check the platform’s automated-trading controls and the EA’s individual settings. Enable only the privileges the program needs and obtain software from a trusted source. An unexplained library or network permission is a reason to consult the developer before installation.
Use a demo account to verify that the intended program is attached, initialized and behaving as expected. Check Experts and Journal output instead of assuming an icon on the chart proves the system is operating correctly.
Measure the active workload
An EA that scans many symbols or performs complex calculations can demand more resources than a simpler program. Include the charts and other terminals running at the same time when sampling CPU, memory and disk activity.
A terminal count alone does not set capacity. Keep strategy testing and batch analysis separate in your brief, and observe a representative trading period before requesting a resource upgrade.
Avoid duplicate live instances
- Back up the working configuration and prepare a demo copy on the destination VPS.
- Record which terminal and account are meant to run each EA.
- Test remote disconnection, reconnection and a planned restart.
- During changeover, stop the old live instance before starting the replacement unless intentional parallel operation has been explicitly designed.
- Review logs and connection state after the switch; retain the rollback files and procedure.