To migrate a previous vCenter Operations Manager installation, you log in to the target and complete a one-time wizard to license the product and import the source to your new deployment.

Source Prerequisites

Review About vRealize Operations Manager Migrations through Best Practices when Migrating to vRealize Operations Manager.

Update the source vCenter Operations Manager installation to version 5.8.1 or later.

Temporarily disable dynamic thresholding (DT). You may restore DT after migration.

The DT setting is in the Custom UI under Environment > Configuration > Resource Kind Defaults.

Verify that the source is not collecting from a vCenter Server that is already being monitored by the target. If you need to temporarily disconnect a vCenter Server to meet this requirement, you may restore it after migration.

Verify that the disk that contains the vCenter Operations Manager log directory has free space. Migration requires approximately 2 GB free log space for every 20,000 resources, 1 TB of FSDB data, and run time history of 1 year.

Temporarily disable alerts so that migrated notifications do not fire immediately. You may restore alerts after migration.

When two vCenter Operations Manager sources will be migrated, and both collect from the same vCenter Server, verify that one source connects to the vCenter Server using the vCenter Server IP address, and the other source connects using FQDN.

Know the names and IP addresses of the source machines.

Know the administrator username and password of the source machines.

For sources that use Oracle or SQL Server for the database, verify that a minimum of 10 idle connections are available.

For vApp sources, verify that the vSphere UI is up and running.

For Linux and Windows sources, verify that the Custom UI is up and running.

For Linux and Windows sources, verify that the source has a minimum of 1 GB of free memory.

For Linux and Windows sources, verify that the outbound port on the source is open so that data can be transferred to the target. The default port is 6061.

For Windows sources, verify that HTTPS is enabled.

For Windows sources, verify that vCenter Operations Manager is installed under a folder path that does not contain spaces.

Target Prerequisites

Verify that network connection speed between the target and source is 100 mbps minimum.

If the target has high availability (HA) enabled, temporarily disable HA.

Take a target snapshot in case the migration does not produce the result that you want, and you need to revert the target.

Increase the data retention time to match the setting from the source.

To avoid a large number of immediate notifications, temporarily disable notifications.

Synchronize the system time setting on the target and all sources. The time zone does not need to be synchronized.

If, after starting the Import Data wizard, the wizard reports a shortage, add CPU, memory, and disk before proceeding.

If, after starting the Import Data wizard, the wizard reports any missing adapters, install the adapters before proceeding.


In a Web browser, navigate to the FQDN or IP address of the master node of the vRealize Operations Manager target.

If you configured nodes and started the cluster, the product takes you to the login page.


Enter the username admin and the password that you defined when configuring the master node, and click Login.

Because this is the first time logging in, a one-time wizard appears.


Click Import Environment and click Next.


Read and accept the End User License Agreement, and click Next.


Enter your product key, or select the option to run vRealize Operations Manager in evaluation mode.

vRealize Operations Manager does not license managed objects like vSphere does, so there is no object count when licensing the product.


If you entered a product key, click Validate License Key.


Click Next.


Enter the fully qualified domain name (FQDN) or IP address of the source from which you want to import.

For a vApp deployment, the source must be a vCenter Operations Manager UI server, not an analytics server.


Enter the admin password for the source.


Click Add Source.

vRealize Operations Manager finds and loads the security certificate for the source.


Select Accept this certificate and click OK.

vRealize Operations Manager adds the source to the list of sources from which it will import, and calculates the amount of resources that the target must have for the import to succeed. If the target does not have enough resources, you must install more disk or data nodes before proceeding.


For each source in the list, use the drop menu to select the Migration Mode.

Migration mode allows you to exclude historical data when migrating, because migrating the data significantly increases migration time as well as the free space needed on the target.


Add more sources or click Next.

A list of solutions appears, which reveals any that are present on sources but missing from the target deployment.


If the source has an adapter installed that is missing from the target, click Add Solution to add the adapter to the target.

The steps to add a solution adapter are the same during migration as when you add a new solution.


After adding solutions, click Next.


To start the migration import, click Finish.

The wizard closes, and you can monitor the progress of the migration.

While an import is in progress, do not make changes to the source inventory or resources.

The import process might take many hours to complete, especially if you chose to migrate historical data. The number of resources, number of metrics, length of history, and size of the FSDB all contribute to the time needed for migration. During internal testing, an inventory of 13,000 resources with 2.5 years of history took about 44 hours to migrate. A guideline of 1 hour per 10 GB of FSDB data is a good starting point but might be influenced by network performance or other factors.

Multiple sources are migrated in sequence. If one source migration fails, the migration continues with the next source. In addition, you can stop a migration at any time.

After the import finishes, use vRealize Operations Manager to monitor the newly imported resources. Eventually, you might also want to turn off your earlier source vCenter Operations Manager deployment.