The role that vCenter Operations Manager plays in your enterprise affects whether you should migrate, or import, your older deployment to vRealize Operations Manager or configure the clean, newly installed deployment from the beginning.

For some users, it is simpler to deploy vRealize Operations Manager, configure the product from the beginning, and monitor the environment. Other users might have integrated vCenter Operations Manager tightly into their business operations and want to migrate as much of their older setup as possible.

If any of the following conditions are true, you are probably a good candidate for configuration and data migration rather than newly configuring vRealize Operations Manager.

vCenter Operations Manager is an essential tool for monitoring your environment performance and health, and you act on the alerts that it generates.

You actively use vCenter Operations Manager for capacity planning in the following ways:

You reallocate resources.

You add resources when objects are stressed.

You reclaim waste that vCenter Operations Manager identifies in the object pool.

You run what if scenarios for determining future capacity.

You use or share capacity planning reports with others.

You have a company requirement to retain monitoring data, and vCenter Operations Manager is the application that you use for that purpose.

You transmit vCenter Operations Manager data such as raw metrics, alerts, reports, or notifications to other production systems.

Migration provides an option to only import the vCenter Operations Manager configuration, without historical data. If any of the following conditions are true, you might be a good candidate for configuration-only migration rather than newly configuring vRealize Operations Manager.

You invested in the configuration and customization of your vCenter Operations Manager deployment and want to save those configurations in vRealize Operations Manager. Examples include the following configurations:

Policy settings


Hard thresholds and key performance indicators (KPIs)

Custom groups

Features have changed from vCenter Operations Manager to vRealize Operations Manager, but you have reviewed which features are migrated and are satisfied that a migration will import what you need.

Remember that migration to a vRealize Operations Manager target deployment is side-by-side. If a migration does not produce the result you want, you can delete the target deployment and try again. vCenter Operations Manager 5.x remains available to monitor your environment until you decide otherwise. A migration does not shut down version 5.x.