A vRealize Operations Manager migration cannot import certain data and features from the source. In many cases, you can separately re-add or configure the associated feature on the target, however.


Report templates

Active or cancelled alerts, alarms, symptoms, and notification history

Global settings

Grid column sizes and sequences

Custom group to policy association

Resource to attribute package association

Resource to super metric package association

User password policies

Metric and KPI status for World resource kind

Standard email plugin notification rule:

Alert type conditions

Filter email plugin rule:

Alert type conditions

Alert subtype conditions

Collector conditions

Adapter-managed groups

In Policies:

Groups badge thresholds

Oversized virtual machines settings

Configure Alerts section

Forecast and trends

Custom group associations

Under use settings

Full profile or balanced profile collection

In vRealize Operations Manager, there is no full mode versus balanced mode, but the default policy is similar to the 5.x balanced mode. To collect the full set of metrics, you must create and apply a new policy or expand the collection scope of the default policy.

Sparkline Chart widget interactions to:

Resource Relationship

Resource Relationship (advanced)

Network Port Statistics metric data:



AWS management pack super metric formulas for the following aggregates.

Aggregate Disk I/O Average (Bytes)

Aggregate Disk I/O Average (Count)

Aggregate Network I/O Average (Bytes)

Units for some object type rules in custom groups

The following units change to an incorrect or missing unit:

Cluster total CPU capacity, GHz to MHz

Host disk space, GB to unknown

Virtual machine CPU capacity, MHz to Hz

Latitude and longitude values

After migration, when you manage resource tags that are associated with geographic location, the latitude and longitude values from the 5.x source are not migrated, and the resource location cannot be shown on the map.

Duplicate resources, regardless of how they originate

A resource cannot be migrated when the target is already monitoring it, either originally or because the resource was part of a previous migration. This condition might occur in a number of surprising ways and is key to understanding migrations as described in Best Practices when Migrating to vRealize Operations Manager.

For example, two vCenter Operations Manager custom groups might be essentially the same because all of their resource identifiers are the same, or, for custom groups that use the name as the sole resource identifier, the names are the same. When that happens, only one of the custom groups can be imported. This restriction applies even if two completely different source deployments are involved, and the custom groups are the same only by coincidence or convention.


If you prefer a source version of a custom group, you can import it if you first remove the duplicate that is already on the target.