Inventory the MT4 applications you need to retain
A larger MT4 environment is often built over time: several broker terminals, older Expert Advisors, custom indicators and external services. Before choosing a replacement host, map what is currently working and which component owns each dependency.
Record installation paths, data folders, broker builds and activation constraints. An EA using an external library or machine-bound licence needs a compatibility check on the new server. Keep the existing installation recoverable until the migration is accepted.
Prioritise the busiest MT4 calculations
The relevant processor choice depends on the program. Inspect per-core use during the periods that matter for the strategy and compare it with the responsiveness of the terminal. Adding many cores does not automatically resolve one busy calculation thread.
| Observation | Dedicated-server decision |
|---|---|
| Recurring peak on one core | Review processor behaviour and isolate the responsible program. |
| Many independent active instances | Review aggregate CPU demand and spread application groups deliberately. |
| Sustained memory pressure | Increase capacity or reduce simultaneous background tasks. |
| Large journal or history growth | Plan usable storage and a retention routine. |
| Repeated reconnects at low CPU load | Investigate endpoints and routing before changing hardware. |
Move accounts in controlled groups
- Group the terminals by broker, strategy dependencies and operating owner.
- Prepare a test copy of the first group on the proposed server.
- Verify charts, program permissions and the Experts and Journal output.
- Schedule a cutover and stop the source group before enabling its replacement.
- Observe the transferred group before moving the next one.
Group migration makes failures easier to locate and reduces the chance that two copies of an automated process remain active. Use the MT4 requirements guide to capture the evidence behind the server specification.
Record the maintenance runbook
Write down how to disconnect, how to perform a planned restart and who checks the terminal estate afterwards. Record where configuration backups are kept and how a failed application is restored. A server reboot, an operating-system sign-out and an RDP disconnect must not be treated as the same event.
For a broker-side platform project, use MT4 White Label infrastructure. For smaller workspaces, compare MT4 VPS hosting before choosing physical hardware.