Move MetaTrader 4 to a New Computer Without Losing Setup

A new computer arrives, MetaTrader 4 is downloaded again from the broker, and the terminal opens looking like a fresh installation. The charts are default. The custom indicators are gone. The preset that a strategy tester run was tuned to is not in the list.

Nothing failed. The download installed the program, and almost nothing a trader builds up over a year is stored with the program. The two live in different places on the same machine, and the second place is the one that has to be carried across.

What Actually Has to Move

Start from an inventory rather than from a folder, because the folder is what most attempts get wrong.

Four things accumulate on a working installation. Custom indicators and Expert Advisors, which arrived as files and were placed by hand or by an installer. Chart appearance, held as templates and profiles, which that page covers in full and this one hands to it.

Then saved input sets for the tester and for automated strategies, stored as preset files. And the terminal configuration itself, which is where window layout, journal settings and platform options live.

MetaQuotes splits these the other way, and its split is the one that matters for a move. Files are either immutable, meaning the program executables and the standard sounds shipped with the installer, or editable, meaning all settings and configuration files, the price history databases, the platform and expert journals, and every profile.

The immutable half is what the installer puts back. The editable half is the half nobody can reinstall, so the inventory reduces to a single instruction: reinstall the program from the broker, and carry the editable data across yourself. Anything already exported from MT4 history sits outside the problem, because the terminal no longer holds it.

Why the Installation Folder Is Not the Whole Terminal

The instinct is to copy whatever sits under Program Files, because that is where the platform was installed and it is the only location the operating system advertises. On a default Windows installation that folder holds the smaller half.

MetaQuotes documents the reason directly. From Windows Vista onward, an application installed into Program Files is not permitted to store its data there by default, so the platform runs in what the documentation calls its main mode and writes everything editable into a separate user directory instead. The same mode is used when User Account Control is switched on, and when the machine is reached over Remote Desktop.

Two consequences follow, and both bite during a migration. A copy of the program folder is a copy of files the installer would have produced anyway. And because the data lives under a specific Windows account, a second account on the same machine gets its own separate copy of everything, which is why a terminal can look empty after a login that was never used before.

The same separation explains why a platform that emulates Windows, as it does when running MT4 on a Mac, keeps its data somewhere that bears no resemblance to the visible install path.

Why the Same Build Stores Its Files in Two Different Places

The data directory sits under the roaming application data of the current Windows user, inside a MetaQuotes folder, in a subfolder named for the terminal instance. That subfolder name is the part worth understanding, because it is not a serial number and it is not random.

MetaQuotes states that the identifier is generated from the path of the directory the platform was installed into. Two installations at two different paths therefore produce two different data folders on the same machine, holding two unrelated sets of indicators and templates. Each of those folders carries a plain text file recording which installation path it belongs to, which is the only reliable way to tell them apart from the outside.

For a migration this is the whole problem in one sentence. The old machine has a data folder named after the old install path. The new machine, installed to a path that differs by so much as a broker name, generates a different one. A folder copied across under its original name is a folder the new terminal will never read.

The practical consequence is that contents move, not containers. Reach the data directory through the terminal itself on both machines, then copy what sits inside the old one into the new one.

Three Routes, and Which One Fits Your Case

Three ways exist to get from one machine to the other. They are not three flavours of the same procedure, and the one that fits depends on whether the old machine is staying available and whether this is likely to happen again.

The first is a fresh install with the data copied into it. Download the terminal from the broker, run it once so the data folder is created, then copy the editable contents from the old data folder into the new one. This is the route that works from a backup and the route that survives a change of Windows version, because nothing depends on the two machines matching. It is also the only one of the three that survives a change of operating system, to a Linux machine where the terminal is installed inside a compatibility layer rather than onto Windows directly.

The second is a wholesale copy, and it is only available if the old installation was already portable. A portable terminal keeps its data beside its program, so the folder is self-contained and a copy of it is a copy of the terminal. Where that is not how the old machine was set up, this route does not exist and attempting it produces the empty terminal described at the top of this page.

The third is to convert before moving. MetaQuotes documents a portable mode, under which the editable half is written back beside the program rather than into the user directory. It is switched on by adding a portable key to the command line that launches the terminal executable.

Switching the old installation over, letting it rebuild its data beside the program, and then copying the folder turns the second route back on. It costs a step now and removes the whole problem from every future move.

What Never Transfers and Has to Be Redone

Some of the terminal is not data at all, and no copy reaches it.

The executables are the clearest case. They belong to the broker build that installed them, they sit on the immutable side of the split, and they are meant to be downloaded again rather than carried. A copied executable also stops receiving the update the broker pushes to its own installer.

Anything that was activated rather than installed is the second case. A compiled program placed in the right folder is not the same as a program licensed to run, which is the distinction MetaEditor makes visible the moment a purchased robot refuses to open on a new machine.

The third case is the folder identity itself. The data directory name belongs to the old installation path and cannot be transplanted, which is why every route above moves contents rather than folders.

Account records are the case most often assumed and least often checked. Order history is held by the broker and reappears on login, but the depth of chart history a terminal shows is a local database that the new installation rebuilds from the server rather than from the copy.

Checking the Move Before You Retire the Old Machine

Five checks settle it, and all five have to run while the old machine is still reachable.

Reach the data directory on the new machine through the File menu rather than through Windows, and confirm the path it opens is the one the copy went into. Then load a chart and apply a template that was built on the old machine, checking that every custom indicator on it draws rather than silently going missing.

Attach an Expert Advisor and load a saved preset into it, since presets sit in their own folder and are the item most often left behind. Open the strategy tester and confirm the symbol list and the input sets are the ones expected.

Finally, place a test order on a demo account. A platform that installed correctly and connected correctly can still refuse an order for causes unconnected to the move, and knowing which MetaTrader error codes mean what is the difference between a migration fault and an ordinary rejection. Only after all five pass is the old installation safe to remove.