Migrate an External vRealize Orchestrator 6.x and Later to vRealize Automation 7.6

You can migrate your existing external vRealize Orchestrator server to a vRealize Orchestrator instance embedded in vRealize Automation.

Note: The migration procedure is identical for both standalone and clustered vRealize Automation environments. If you have a clustered vRealize Automation environment, perform the migration through the VAMI interface on the primary node.

Prerequisites

You can migrate your existing external vRealize Orchestrator server to a vRealize Orchestrator instance embedded in vRealize Automation.

• Note: When migrating a clustered vRealize Orchestrator environment, enter the credentials of any node from the cluster. The target vRealize Automation cluster must be in async mode for the migration to be successful.
• Upgrade or migrate your vRealize Automation to the target release. For more information, see Installing or Upgrading vRealize Automation.
• Back up your vRealize Automation environment, including any external databases.
• Stop the vRealize Orchestrator services of the external vRealize Orchestrator.
• Enable SSH access for each node in your external vRealize Orchestrator and vRealize Automation environments.
• Verify that the external vRealize Orchestrator database is accessible from the vRealize Automation environment.
• Finish all workflows in the external vRealize Orchestrator environment that are in the running or waiting for input states. Workflows in these states are marked as failed in the embedded vRealize Orchestrator environment.
• Back up the database of the external vRealize Orchestrator server.

Procedure

1. Log in to the VAMI interface of the target vRealize Automation environment as root.
   Access the VAMI interface at https:// your_automation_server_ip_or_DNS_name:5480.
2. From the Migrate tab, click the vRO subtab.
3. Enter the host name and root credentials of the source vRealize Orchestrator environment.
4. Enter the root credentials of the target vRealize Automation primary node.
5. Click Validate.
   The system performs a series of validations steps to ensure that the migration prerequisites are met.

   Note: If a migration prerequisite validation fails, review the failure and correct the problem. Click Edit Settings and retry the validation.
6. After the validation is finished, click Migrate to start the migration.
   If a migration step fails, review the failure and correct the problem. To retry the migration, revert to the pre-migration state of the target environment.

What to do next

Set up the built-in vRealize Orchestrator server. See Configure the Embedded vRealize Orchestrator Server Service.