Migration from previous ERA version

If you want to upgrade/migrate from an older generation of ESET Remote Administrator 5 to ESET Remote Administrator 6, you can use our Migration Tool which can make the upgrade process easier. The Migration Tool is a standalone application in form of a wizard that provides straightforward migration of ERA 4.x / 5.x data into an intermediate database which allows for the data to be imported into ERA 6.x.

validation-status-icon-warning IMPORTANT: Migration Tool version must match ESET Remote Administrator version you're going to migrate to. To find out what version of Migration Tool you need see this Knowledgebase article.

validation-status-icon-error WARNING: When the ERA 6.x Agent is installed on a client using 5.x or earlier endpoint products, the Remote administration setting for that client is automatically changed to localhost / 2225. As a result, the client will no longer connect to your ERA 5.x server after Agent is installed.

Download appropriate version of ESET Remote Administrator Migration Tool.

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

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

Configuration of your old ERA server is not being migrated.

Parametric groups are not migrated.

You can migrate policies with Migration Tool 6.2.x and newer. However, there are some specifics to policy migration:

Only policies from upper ERA server are migrated.

Only policy definitions are migrated, policy relations are not being migrated.

You will need to assign migrated policies to appropriate groups manually after the migration.

Hierarchy of policies is omitted. In case there is an override flag in your old ERA, this flag is converted to a force in ERA 6 policy for that same setting.

If there are settings for multiple products in a single policy in old ERA, an individual policy for each product will be created in ERA 6.

validation-status-icon-infoNOTE: After the migration, we recommend you to check items (Computers, Static Groups, Policies, etc.) to make sure these are in place and that the result of migration meets the expectations. In case there are some discrepancies, an intervention is needed, such as creating policies manually.

validation-status-icon-infoNOTE: If an error occurs during the migration process, it is written in migration.log file located in the same folder as Migration Tool. If you have read-only access to this folder, then a log window will open instead. Same thing happens should there be not enough disk space, that means the log file is not created and you will only see results in the log window.



The following are migration scenarios which should guide you through the migration process itself:

Migration scenario 1 - Migration to ERA 6.x running on a different computer than ERA 4.x / 5.x.

Migration scenario 2 - Migration to ESET Remote Administrator 6.x running on the same computer as ERA 4.x / 5.x.

Migration scenario 3 - Migration to ERA 6.x where endpoints connect to old ERA 4.x / 5.x until the ERA Agent is deployed by ERA 6.x.