Migration scenario 2

This scenario covers migration to ESET Security Management Center 7.x running on the same computer as ERA 5.x. Back up all ERA data (using the ESET Maintenance tool) and stop ERA services in the operating system before the migration of any data.

Watch our Knowledgebase instructional video, or visit our Knowledgebase article for illustrated step-by-step instructions to complete installation using the All-in-one installer.

1.Download and run the ESET Remote Administrator Migration Tool.

Install Microsoft Visual C++ 2017 x86, it is required for Migration Tool to work properly. You can find it in the .zip file containing the Migration Tool.

Run the Migration Tool as Administrator, locally on your old ERA 5.x sever. It is not possible to run Migration Tool from a remote machine.

2.Selects the Export option to save the data from ERA 5.x to an intermediate database file. Migration wizard is able to transfer specific data only:


3.Select a save folder for the intermediate database.


4.The wizard displays the status of archival of the ERA 5.x database.


5.All data is exported to an intermediate database.



After the successful data export and before ESMC 7.x deployment, ERA 5.x must be uninstalled. We recommend to restart the machine prior to continue with installation of ESMC 7.x.

6.When new ESMC 7.x is installed, import the exported database using the Migration tool. Administrator is prompted to enter the IP address of the machine (that was displayed for ESMC Console in the Installation successful screen) into the Host field, the administrator password configured during installation.


7.Select the saved database file.


8. If server settings do not allow the import of specific data, the ESET Remote Administrator Migration tool lets you choose whether you want to change settings in ESMC 7.x for specific components.

Each of the components is then imported. An import (migration) log is available for each component. After the import is complete, the Migration tool will display the results of the import process.




If you selected to migrate users, their passwords are reset and replaced with randomly generated passwords. These passwords can be exported in the .CSV format.

9. You can use the Migration Tool to generate a script that can be used to preconfigure ESET Management Agents on client machines. This script is a small executable .bat file distributable to client computers.


We recommend that you review migrated settings and data to make sure that import was successful. After checking, use this script to deploy the ESET Management Agent on a small group of computers to check if they are connecting to the server correctly.

After the successful connection of the test group, you can deploy the Agent to the remaining computers (either manually or using an AD synchronization task to add the computers in Web Console and then deploy the Agent to them).



If any of the migration steps fail, you should roll back changes for ESMC 7.x, set the computers to connect to ERA 5.x, recover the backup data from ERA 5.x and contact ESET customer care.