After migration finishes, there are steps to take before vRealize Operations Manager begins to fully monitor imported resources or to integrate with the systems to which it can connect.

After migration, vRealize Operations Manager begins monitoring imported resources to which it can connect. However, configuration settings from a source adapter might not be migrated. You must verify adapter configuration settings at the target and make adjustments if you want to monitor resources the same way as before.

After migration, the target vRealize Operations Manager deployment cannot collect if the data source connection requires authentication. You must confirm certificates for collections to start. The one exception is when you migrate vCenter Server adapters from vApp vCenter Operations Manager sources.

If the target deployment has remote collector nodes, you must reconfigure migrated vCenter Server adapters by selecting the vRealize Operations Manager remote collector node from the Collector drop-down menu.

Less data might appear after migration. Metric data from 5.x should appear in vRealize Operations Manager as expected. Data might be missing, however, because the 5.x metrics were collected using full profile mode, but vRealize Operations Manager is now collecting using a default policy that does not include the full settings from 5.x full profile mode. To collect the full set of metrics going forward, you must create and apply a new policy or expand the collection scope of the default policy.

The migrated vCenter Operations Manager email plug-in requires server authentication, so you must verify the email server certificate at the vRealize Operations Manager target before the migrated plug-in will work.

The new vRealize Operations Manager plug-in for vSphere overrides the previous plug-in. If you need to go back to the version 5.x plug-in, access the admin UI of vCenter Operations Manager 5.x, and update the vCenter Server registration.

After migration, vCenter Server adapters start collecting. However, you must re-register vCenter Server adapters so that vCenter Server users can log in to vRealize Operations Manager, and vCenter Server clients can link to vRealize Operations Manager.

When a migration source includes unregistered vCenter adapter instances, after a migration, those adapter instances appear in the list of solutions on the target. You are free to delete the extra vCenter adapter instances from the Solutions page.