After running a migration assessment on your vRealize Automation 7 source environment, you can migrate individual subscriptions to vRealize Automation 8.

The subscriptions results of your migration assessment are listed on the Migration > Subscriptions tab. All assessed subscriptions are listed with their status:

  • Ready - Subscription is ready for migration. No action is needed for migration readiness.
  • Ready with warnings - Subscription is ready but needs review. Remediate any issues that might impact migration.
  • Not ready - Subscription is not ready for migration. Review details of the subscription in your source environment and correct areas needing attention.
  • Assessing - Subscription is still being assessed for migration readiness.
  • Assessment failed - The assessment failed, retry assessment.

If applicable, after modifying any subscriptions listed as not ready or ready with warnings, select the subscription and click Update to update its status in the assessment results table. The assessment report also flags which subscription conditions are not supported. Before you can migrated these subscriptions, you must correct the unsupported conditions and reassess the subscription.

The Subscriptions Migration page displays which subscriptions were assessed during migration assessment along with their migration readiness. From this page you can choose to update or migrate selected subscriptions. Clicking update just refreshes the assessment on selected subscriptions. It is useful when changes to source subscriptions were made after the last migration assessment.

After clicking migrate, the migrate window opens with a list of the selected subscriptions. Clicking Migrate confirms the selected subscriptions and begins migration.

To migrate subscriptions, select one or more subscriptions with a ready or ready with warnings status and click migrate.
Note: Before you can migrate a subscription, you must have at least one migrated business group in vRealize Automation 8 first. If a subscription has dependencies on vRO workflows, it will fail to migrate until these dependencies are migrated first.

After migrating, you can click the subscription name to view its assessment and migration results and status:

  • Migrating - Subscription is being migrated.
  • Migrated - Migration is complete and successful. You can view and use the migrated subscription in your vRealize Automation 8 environment.
  • Failed - The migration failed. Review the subscription in your source environment, modify as needed, retry migration.
  • Excluded - Subscription that was listed as Not ready was migrated but its not ready items were not migrated and are listed as excluded.
Migrated subscriptions are listed in Cloud Assembly > Extensibility. On the Extensibility tab, when you open a migrated subscription, the associated conditions and IDs are listed.
Note: If a vRealize Automation 7 subscription contains an "or" condition, the subscription is migrated into two vRealize Automation 8 subscriptions in which both send the event to the same workflow.
You can roll back previously migrated subscriptions by selecting the migrated subscription and clicking rollback.
Note: If you modify any migrated items and then rollback, all edits post-migration are deleted.