Migrate from vRA 7 to Aria Automation with OneFuse

Migration tools for OneFuse managed objects from VMware vRealize Automation 7x to VMware Aria Automation

  25 minute read  

The OneFuse Migration Tools vRealize Orchestrator Package provides examples for the user to “create” OneFuse Managed Objects via Brownfield ingest from vRealize Automation 7x VMs and apply necessary OneFuse vRA Properties on vRA8.2+ VMs (to enable future deprovisioning from vRA8+OneFuse).

Once migrated, OneFuse Managed Objects will exist and the user has the flexibility to

  1. Destroy via API without deprovisioning

    or

  2. Destroy normally within the deployment in vRA8.2+/Cloud, which then calls OneFuse to destroy and deprovision the resource.

The Migration Tools vRO Package is beneficial for the following:

  1. Customers who are currently utilizing the SovLabs Heritage Plug-in for vRealize Automation 7x to generate names, reserve IP Addresses and DNS records and more,

    and/or

  2. Those who are utilizing custom scripts to provision vRA7x VMs for names, reserving IP Addresses and DNS records and more.

    and

  3. Those who have interest in finding an efficient way to migrate to OneFuse and VMware Aria Automation 8.2+/Cloud. The Migration Tools vRO Package contains sample workflows that can be used out-of-the-box or copied then modified to fulfill requirements.

    Check back here for updates to the Migration Tools vRO Package.

The following table depicts sample workflows for OneFuse Modules in the Migration Tools vRO Package:

OneFuse Module / Feature Migration Tools vRO Package Minimum Version
Ansible Tower 1.4.0 Build 11297897
DNS Module 1.4.0 Build 11032329
IPAM Module 1.4.0 Build 11032329
Microsoft Active Directory Module 1.4.0 Build 11032329
Naming Module 1.4.0 Build 11223817
ServiceNow CMDB Module 2022.0.0
templateProperties 1.4.0 Build 12209087
(Requires OneFuse vRA Upstream Provider package version 1.4.0.12087506 or higher)
Action to Flatten and Translate templateProperties, for example for easier Ansible Tower consumption
vmProperties 1.4.0 Build 12209087
(Requires OneFuse vRA Upstream Provider package version 1.4.0.12087506 or higher)
Migrate VM Properties using include/exclude rules
Migrate VM Properties using OneFuse Property Set for translation

Prerequisites

  1. OneFuse installed and setup:

  2. OneFuse configured:

  3. VMware Aria Automation 8.2+/Cloud installed and setup with OneFuse:

    1. Getting started
    2. Installation and setup
      • Note the OneFuse Endpoint name and configurations for step 4 below.

  4. The source vRealize Automation 7x installed and setup with OneFuse Endpoint:

    1. Getting started
    2. Installation and setup
      • When running the OneFuse Configuration workflow, the OneFuse Endpoint should be the same instance as the one setup for vRA 8.2+/Cloud from step 3, Installation and Setup (it is also highly recommended to have the same OneFuse Endpoint Name).
      • While this source vRA 7x instance could be configured to use OneFuse, the purpose of this Prerequisite Step is to create the OneFuse Endpoint.

  5. Migrate vRealize Automation 7 Deployments to Aria Automation 8.2+/Cloud

Download the migration tool vRealize Orchestrator workflow package

Access CloudBolt’s Download Article for CMP/OneFuse 2023.5.

  1. Go to https://support.cloudbolt.io/cloudbolt/s/article/cloudbolt-2023-5--1983840286--1
  2. Download the OneFuse VMware vRO Migration Package.

Import the migration tool vRealize Orchestrator workflow package

  1. Log in to vRealize Orchestrator 7x.

  2. Select Assets > Packages.

  3. Select Import.

    1. Select Browse.

    2. Select the Migration Tool vRealize Orchestrator Workflow Package (.package) to upload.

    3. Select Open.

    4. Review the imported package information.

    5. Select Import.

  4. Verify the OneFuse vRealize Orchestrator Workflow Package successfully imported:

    • io.cloudbolt.onefuse.migration is listed in the list of Packages under Assets > Packages.
    • The Build Number is found in the Description field of the vRO Package.

Run the Create vRA Migration Endpoint workflow

Specify the connection to the target Aria Automation instance, for example Aria Automation 8.2+/Cloud.

  1. Log in to vRealize Orchestrator 7x.

  2. Select Library > Workflows from the left menu.

  3. Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > Configuration

  4. Select the Workflow: Create vRA Migration Endpoint > select Run.

  5. Fill out the form fields.

  6. Select the [Run] button.

  7. Verify the Workflow completed successfully.

Create vRA Migration Endpoint form fields

Field Label Description
Common parameters
Type Select the appropriate vRA Version for the Target Aria Automation
vRA Appliance FQDN (Shown when Type is vra8)
Enter the Target Aria Automation Host in FQDN format.
vRA Cloud API FQDN (Shown when Type is vrac)
Enter the Target Aria Automation Cloud in FQDN format.
vRA Appliance Port (Shown when Type is vra8)
Enter the Port number for this Target vRA Migration Endpoint.
vRA Username (Shown when Type is vra8)
Username for OneFuse Service Account for the Target vRA in UPN format.
vRA Password (Shown when Type is vra8)
Password for user account.
vRA Cloud API Token (Shown when Type is vrac)
Enter the vRA Cloud API Token
Ignore Certificate Warnings? Check yes to silently accept the certificate.
Verify whether the target hostname matches the names stored inside the server’s X.509 certificate Check yes if the target hostname matches the names stored inside the server’s X.509 certificate.
Proxy Settings
Use Proxy? Check yes if using a Proxy.
Proxy Host FQDN / IP (Shown when Use Proxy? is Yes)
Enter the Proxy Host in Host in FQDN or IP Address format.
Proxy Port (Shown when Use Proxy? is Yes)
Enter the Port number for this Proxy Host.

Managing vRA Migration Endpoint(s)

When credentials and/or endpoints are updated, use the workflows below to update the vRA Migration Endpoint previously configured.

Only one vRA Migration Endpoint may exist at a given time.

  • To update the existing vRA Endpoint, run the workflow OneFuse > Migration Tools > Configuration > Update vRA Migration Endpoint.
  • To delete the existing vRA Endpoint, run the workflow OneFuse > Migration Tools > Configuration > Delete vRA Migration Endpoint.

Migrate existing resources to OneFuse managed objects

Ansible Tower

Migrate Ansible Tower Deployments from vRA 7x VM to create OneFuse Managed Ansible Tower Deployments. In addition, apply necessary OneFuse vRA Properties to the migrated vRA8/Cloud Deployment(s) so that when the deployment is destroyed from vRA8/Cloud, OneFuse will destroy the Ansible Tower Deployments.

Optionally, if there are any vRA Properties that identify and/or filter the VMs for particular Names, it will be helpful to have a list to reference when running the workflow below.

  1. Log in to vRealize Orchestrator 7x.

  2. Select Library > Workflows from the left menu.

  3. Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > Ansible Tower > From vRA7 > To vRA8

  4. Select the Workflow: Migrate Ansible Tower from vRA7 to vRA8+OneFuse > select Run.

  5. Fill out the form fields.

  6. Select the [Run] button.

  7. Verify the Workflow has completed successfully.

Migrate Ansible Tower from vRA7 to vRA8+OneFuse

Field Label Description
Endpoints
OneFuse Endpoint Select the OneFuse Endpoint (created in prerequisite step 4, Installation and Setup).
Same OneFuse Endpoint name in vRA8? Select whether or not this OneFuse Endpoint Name is the same as the OneFuse Endpoint Name in the target vRA 8.2+/Cloud instance.
OneFuse Endpoint name in vRA8 (Shown when Same OneFuse Endpoint name in vRA8? is No)
Enter the OneFuse Endpoint name in the target vRA 8.2+/Cloud instance.
vRA 7.x Tenant Name Select from the dropdown the vRA 7 Tenant.
Policy and Config
OneFuse Policy Name to migrate to Select the OneFuse Ansible Tower Policy Name to migrate the Deployments to from the dropdown.
Preferred order to select name to be migrated Select the order of preference to migrate the name from the dropdown.
Hostname, virtualMachineName - It will look at the Hostname property first
virtualMachineName, Hostname - It will look at the virtualMachineName property first
Limit scope based on vRA7 Business Group Choose whether or not to limit the migration to a specific vRA7 Business Group.
Business Group name (Shown when Limit scope based on vRA7 Business Group is Yes)
Select desired vRA7 Business Group Name.
Limit scope based on ALL vRA7 Properties - Number of Properties Filter VMs based on ALL specified number of vRA7 Properties.
(Migrate any Name on a VM, regardless of using SovLabs Heritage Plug-in for the module.)
Select from the dropdown:
0 - Do not Limit scope based on ALL
1 - Limit scope based on 1 vRA Property
2 - Limit scope based on 2 vRA Properties
3 - Limit scope based on all 3 vRA Properties
Limit scope based on ANY vRA7 Properties - Number of Properties Filter VMs based on ANY specified number of vRA7 Properties.
(Migrate any Name on a VM, regardless of using SovLabs Heritage Plug-in for the module.)
Select from the dropdown:
0 - Do not Limit scope based on ANY
2 - Limit scope based on matching at least one of the 2 vRA Properties
3 - Limit scope based on matching at least one of the 3 vRA Properties
Settings
Allow Ingest of duplicates Recommended to select No.
In the event this workflow runs multiple times and this is Yes, it will create the OneFuse Managed Object (regardless if another with the same values exist) and overwrite the vRA Property with the latest Managed Object reference.
Dry run? If Yes, this will not perform an actual migration. It will only provide logs for the actions this workflow would have perform.
Select No to perform a migration.
Error handling Select from the dropdown:
Roll back: Completely roll back all migration creation/vRA Properties injection
Skip failures and report: Will log the failure, continue with the migration and at the end, provide a summarized report via vRO Logs.
(The following variables for a particular Workflow run captures the outputs: managedObjectsPropString, ingestedManagedObjectsPropString, customPropertiesPropString, trackingIdPropString, resourceObjectsPropString and statusPropString. Please note that more output properties may exist.)

DNS

Migrate DNS Reservations from vRA 7x to create OneFuse Managed DNS Records. In addition, applies necessary OneFuse vRA Properties to the migrated vRA8/Cloud Deployment(s) so that when the deployment is destroyed from vRA8/Cloud, OneFuse will destroy the DNS Record(s).

Customers using the SovLabs Heritage Plug-in for vRA7x and the DNS module did not have to apply the DNS Configuration name as a vRA Property. During the VM lifecycle, the SovLabs DNS module would match the domain and apply the proper DNS Configuration accordingly. Therefore, this migration workflow will solely rely on vRA Properties provided to filter vRA 7x VMs.

Optionally, if there are any vRA Properties that identify and/or filter the VMs for particular Domains (regardless of using SovLabs DNS Module or not), it will be helpful to have a list to reference when running the workflow below.

  1. Log in to vRealize Orchestrator 7x.

  2. Select Library > Workflows from the left menu.

  3. Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > DNS > From vRA7 > To vRA8

  4. Select the Workflow: Migrate DNS Reservations from vRA7 to vRA8+OneFuse > select Run.

  5. Fill out the form fields.

  6. Select the [Run] button.

  7. Verify the Workflow completed successfully.

Migrate DNS Reservations from vRA7 to vRA8+OneFuse

Field Label Description
Endpoints
OneFuse Endpoint Select the OneFuse Endpoint (created in prerequisite step 4, Installation and Setup).
Same OneFuse Endpoint name in vRA8? Select whether or not this OneFuse Endpoint Name is the same as the OneFuse Endpoint Name in the target vRA 8.2+/Cloud instance.
OneFuse Endpoint name in vRA8 (Shown when Same OneFuse Endpoint name in vRA8? is No)
Enter the OneFuse Endpoint name in the target vRA 8.2+/Cloud instance.
vRA 7.x Tenant Name Select from the dropdown the vRA 7 Tenant.
Policy and Config
OneFuse Policy Name to migrate to Select the OneFuse DNS Policy Name to migrate the DNS record(s) to from the dropdown.
Domains for the Policy to register against Enter the Domain(s) that the DNS record(s) are registered to (for example example.com).
Validate NIC DNS Suffix against provided Domains Choose whether or not to validate if the Domains match the NIC DNS Suffix.
Limit scope based on vRA7 Business Group Choose whether or not to limit the migration to a specific vRA7 Business Group.
Business Group name (Shown when Limit scope based on vRA7 Business Group is Yes)
Select desired vRA7 Business Group Name.
Limit scope based on ALL vRA7 Properties - Number of Properties Filter VMs based on ALL specified number of vRA7 Properties.
(Migrate any DNS reservation on a VM, regardless of using SovLabs Heritage Plug-in for the module.)
Select from the dropdown:
0 - Do not Limit scope based on ALL
1 - Limit scope based on 1 vRA Property
2 - Limit scope based on 2 vRA Properties
3 - Limit scope based on all 3 vRA Properties
Limit scope based on ANY vRA7 Properties - Number of Properties Filter VMs based on ANY specified number of vRA7 Properties.
(Migrate any DNS reservation on a VM, regardless of using SovLabs Heritage Plug-in for the module.)
Select from the dropdown:
0 - Do not Limit scope based on ANY
2 - Limit scope based on matching at least one of the 2 vRA Properties
3 - Limit scope based on matching at least one of the 3 vRA Properties
Settings
Disregard SovLabs Disable DNS Properties If Yes, it will perform a migration even if the vRA 7x VM has the SovLabs_DisableDNS vRA Property.
If No, it will skip the vRA 7x VM with the SovLabs_DisableDNS vRA Property.
Allow Ingest of duplicates Recommended to select No.
In the event this workflow runs multiple times and this is Yes, it will create the OneFuse Managed Object (regardless if another with the same values exist) and overwrite the vRA Property with the latest Managed Object reference.
Dry run? If Yes, this will not perform an actual migration. It will only provide logs for the actions this workflow would have perform.
Select No to perform a migration.
Error handling Select from the dropdown:
Roll back: Completely roll back all migration creation/vRA Properties injection
Skip failures and report: Will log the failure, continue with the migration and at the end, provide a summarized report via vRO Logs.
(The following variables for a particular Workflow run captures the outputs: managedObjectsPropString, ingestedManagedObjectsPropString, customPropertiesPropString, trackingIdPropString, resourceObjectsPropString and statusPropString. Please note that more output properties may exist.)

IPAM

Migrate IPAM Reservations from vRA 7x to create OneFuse Managed IP Addresses. In addition, applies necessary OneFuse vRA Properties to the migrated vRA8/Cloud Deployment(s) so that when the deployment is destroyed from vRA8/Cloud, OneFuse will destroy the IP Address(es).

This workflow currently only enables migration of VMs that used the SovLabs Heritage Plug-in IPAM module to reserve IP Addresses.

  1. Log in to vRealize Orchestrator 7x.

  2. Select Library > Workflows from the left menu.

  3. Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > IPAM > From vRA7 > To vRA8

  4. Select the Workflow: Migrate IPAM Reservations from vRA7+SovLabs to vRA8+OneFuse > select Run.

  5. Fill out the form fields.

  6. Select the [Run] button.

  7. Verify the Workflow completed successfully.

Migrate IPAM Reservations from vRA7+SovLabs to vRA8+OneFuse

Field Label Description
Endpoints
OneFuse Endpoint Select the OneFuse Endpoint (created in prerequisite step 4, Installation and Setup).
Same OneFuse Endpoint name in vRA8? Select whether or not this OneFuse Endpoint Name is the same as the OneFuse Endpoint Name in the target vRA 8.2+/Cloud instance.
OneFuse Endpoint name in vRA8 (Shown when Same OneFuse Endpoint name in vRA8? is No)
Enter the OneFuse Endpoint name in the target vRA 8.2+/Cloud instance.
vRA 7.x Tenant Name Select from the dropdown the vRA 7 Tenant.
Policies
Migrate all Policies to OneFuse Policies with matching names Select No to specify the SovLabs IPAM Profile - this workflow have to run for each SovLabs IPAM Profile.
Select Yes only if the corresponding OneFuse IPAM Policies have the same name as the SovLabs IPAM Profile. This will get and migrate all VMs that have the SovLabs IPAM Profiles for the vRA Tenant.
SovLabs Plug-in Policy Name to migrate from Select from the dropdown the SovLabs IPAM Profile - this will perform migrations on all VMs with the specified SovLabs IPAM Profile.
OneFuse Policy Name to migrate to Select the OneFuse IPAM Policy Name to migrate the IP Address(es) to.
Settings
Allow Ingest of duplicates Recommended to select No.
In the event this workflow runs multiple times and this is Yes, it will create the OneFuse Managed Object (regardless if another with the same values exist) and overwrite the vRA Property with the latest Managed Object reference.
Dry run? If Yes, this will not perform an actual migration. It will only provide logs for the actions this workflow would have perform.
Select No to perform a migration.
Error handling Select from the dropdown:
Roll back: Completely roll back all migration creation/vRA Properties injection
Skip failures and report: Will log the failure, continue with the migration and at the end, provide a summarized report via vRO Logs.
(The following variables for a particular Workflow run captures the outputs: managedObjectsPropString, ingestedManagedObjectsPropString, customPropertiesPropString, trackingIdPropString, resourceObjectsPropString and statusPropString. Please note that more output properties may exist.)

Microsoft Active Directory computer accounts

Migrate Microsoft Active Directory Computer Account from vRA 7x VM to create OneFuse Managed Computer Accounts. In addition, apply necessary OneFuse vRA Properties to the migrated vRA8/Cloud Deployment(s) so that when the deployment is destroyed from vRA8/Cloud, OneFuse will destroy the Computer Account(s).

Optionally, if there are any vRA Properties that identify and/or filter the VMs for particular Names, it will be helpful to have a list to reference when running the workflow below.

  1. Log in to vRealize Orchestrator 7x.

  2. Select Library > Workflows from the left menu.

  3. Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > AD > From vRA7 > To vRA8

  4. Select the Workflow: Migrate AD from vRA7 to vRA8+OneFuse > select Run.

  5. Fill out the form fields.

  6. Select the [Run] button.

  7. Verify the Workflow completed successfully.

Migrate AD from vRA7 to vRA8+OneFuse

Field Label Description
Endpoints
OneFuse Endpoint Select the OneFuse Endpoint (created in prerequisite step 4, Installation and Setup).
Same OneFuse Endpoint name in vRA8? Select whether or not this OneFuse Endpoint Name is the same as the OneFuse Endpoint Name in the target vRA 8.2+/Cloud instance.
OneFuse Endpoint name in vRA8 (Shown when Same OneFuse Endpoint name in vRA8? is No)
Enter the OneFuse Endpoint name in the target vRA 8.2+/Cloud instance.
vRA 7.x Tenant Name Select from the dropdown the vRA 7 Tenant.
Policy and Config
OneFuse Policy Name to migrate to Select the OneFuse Microsoft Active Directory Policy Name to migrate the Computer Accounts to from the dropdown.
Preferred order to select name to be migrated Select the order of preference to migrate the name from the dropdown.
Hostname, virtualMachineName - It will look at the Hostname property first
virtualMachineName, Hostname - It will look at the virtualMachineName property first
Limit scope based on vRA7 Business Group Choose whether or not to limit the migration to a specific vRA7 Business Group.
Business Group name (Shown when Limit scope based on vRA7 Business Group is Yes)
Select desired vRA7 Business Group Name.
Limit scope based on ALL vRA7 Properties - Number of Properties Filter VMs based on ALL specified number of vRA7 Properties.
(Migrate any Name on a VM, regardless of using SovLabs Heritage Plug-in for the module.)
Select from the dropdown:
0 - Do not Limit scope based on ALL
1 - Limit scope based on 1 vRA Property
2 - Limit scope based on 2 vRA Properties
3 - Limit scope based on all 3 vRA Properties
Limit scope based on ANY vRA7 Properties - Number of Properties Filter VMs based on ANY specified number of vRA7 Properties.
(Migrate any Name on a VM, regardless of using SovLabs Heritage Plug-in for the module.)
Select from the dropdown:
0 - Do not Limit scope based on ANY
2 - Limit scope based on matching at least one of the 2 vRA Properties
3 - Limit scope based on matching at least one of the 3 vRA Properties
Settings
Allow Ingest of duplicates Recommended to select No.
In the event this workflow runs multiple times and this is Yes, it will create the OneFuse Managed Object (regardless if another with the same values exist) and overwrite the vRA Property with the latest Managed Object reference.
Dry run? If Yes, this will not perform an actual migration. It will only provide logs for the actions this workflow would have perform.
Select No to perform a migration.
Error handling Select from the dropdown:
Roll back: Completely roll back all migration creation/vRA Properties injection
Skip failures and report: Will log the failure, continue with the migration and at the end, provide a summarized report via vRO Logs.
(The following variables for a particular Workflow run captures the outputs: managedObjectsPropString, ingestedManagedObjectsPropString, customPropertiesPropString, trackingIdPropString, resourceObjectsPropString and statusPropString. Please note that more output properties may exist.)

Names

Migrate Names from vRA 7x VM to create OneFuse Managed Names. In addition, apply necessary OneFuse vRA Properties to the migrated vRA8/Cloud Deployment(s) so that when the deployment is destroyed from vRA8/Cloud, OneFuse will destroy the Name(s).

Optionally, if there are any vRA Properties that identify and/or filter the VMs for particular Names, it will be helpful to have a list to reference when running the workflow below.

  1. Log in to vRealize Orchestrator 7x.

  2. Select Library > Workflows from the left menu.

  3. Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > Naming > From vRA7 > To vRA8

  4. Select the Workflow: Migrate VM Names from vRA7 to vRA8+OneFuse > select Run.

  5. Fill out the form fields.

  6. Select the [Run] button.

  7. Verify the Workflow completed successfully.

Migrate VM Names from vRA7 to vRA8+OneFuse

Field Label Description
Endpoints
OneFuse Endpoint Select the OneFuse Endpoint (created in prerequisite step 4, Installation and Setup).
Same OneFuse Endpoint name in vRA8? Select whether or not this OneFuse Endpoint Name is the same as the OneFuse Endpoint Name in the target vRA 8.2+/Cloud instance.
OneFuse Endpoint name in vRA8 (Shown when Same OneFuse Endpoint name in vRA8? is No)
Enter the OneFuse Endpoint name in the target vRA 8.2+/Cloud instance.
vRA 7.x Tenant Name Select from the dropdown the vRA 7 Tenant.
Policy and Config
OneFuse Policy Name to migrate to Select the OneFuse Naming Policy Name to migrate the Names to from the dropdown.
Preferred order to select name to be migrated Select the order of preference to migrate the name from the dropdown.
Hostname, virtualMachineName - It will look at the Hostname property first
virtualMachineName, Hostname - It will look at the virtualMachineName property first
Limit scope based on vRA7 Business Group Choose whether or not to limit the migration to a specific vRA7 Business Group.
Business Group name (Shown when Limit scope based on vRA7 Business Group is Yes)
Select desired vRA7 Business Group Name.
Limit scope based on ALL vRA7 Properties - Number of Properties Filter VMs based on ALL specified number of vRA7 Properties.
(Migrate any Name on a VM, regardless of using SovLabs Heritage Plug-in for the module.)
Select from the dropdown:
0 - Do not Limit scope based on ALL
1 - Limit scope based on 1 vRA Property
2 - Limit scope based on 2 vRA Properties
3 - Limit scope based on all 3 vRA Properties
Limit scope based on ANY vRA7 Properties - Number of Properties Filter VMs based on ANY specified number of vRA7 Properties.
(Migrate any Name on a VM, regardless of using SovLabs Heritage Plug-in for the module.)
Select from the dropdown:
0 - Do not Limit scope based on ANY
2 - Limit scope based on matching at least one of the 2 vRA Properties
3 - Limit scope based on matching at least one of the 3 vRA Properties
Settings
Allow Ingest of duplicates Recommended to select No.
In the event this workflow runs multiple times and this is Yes, it will create the OneFuse Managed Object (regardless if another with the same values exist) and overwrite the vRA Property with the latest Managed Object reference.
Dry run? If Yes, this will not perform an actual migration. It will only provide logs for the actions this workflow would have perform.
Select No to perform a migration.
Error handling Select from the dropdown:
Roll back: Completely roll back all migration creation/vRA Properties injection
Skip failures and report: Will log the failure, continue with the migration and at the end, provide a summarized report via vRO Logs.
(The following variables for a particular Workflow run captures the outputs: managedObjectsPropString, ingestedManagedObjectsPropString, customPropertiesPropString, trackingIdPropString, resourceObjectsPropString and statusPropString. Please note that more output properties may exist.)

Properties

Migrate Property Groups from vRA 7x to create OneFuse Property Sets and migrate VM Properties from vRA7 to vRA8.

  1. Log in to vRealize Orchestrator 7x.

  2. Select Library > Workflows from the left menu.

  3. Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > Properties > From vRA7 > To OneFuse

  4. Select the Workflow: Migrate from Property Groups in vRA7 to Property Sets in OneFuse > select Run.

  5. Fill out the form fields.

  6. Select the [Run] button.

  7. Verify the Workflow completed successfully.

Migrate property groups from vRA7 to OneFuse property sets

Field Label Description
vRA Property Group(s)
Tenant Select from the dropdown the vRA 7 Tenant.
Get all Property Groups? Select Yes or No.
If no, an option to provide the Page Size and multi-select Property Groups.
Name Filter - Optional Limit scope based on name filter provided.
OneFuse Endpoint
OneFuse Endpoint Select the OneFuse Endpoint (created in prerequisite step 4, Installation and Setup).
Property Set(s)
Create a Property Set per vRA Group? Select Yes or No.
Advanced
Migrate vRA 7 Properties? Select Yes or No.
Migrate SovLabs Properties Select Yes or No.

Migrate VM Properties from vRA7 to vRA8 by: 1) Using inclusion and exclusion rules and/or 2) Using OneFuse Property Set for translation.

  • Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > Properties > From vRA7 > To vRA8
  • Select the Workflow: Migrate VM Properties from vRA7 to vRA8 - Using inclusion and exclusion rules or Migrate VM Properties from vRA7 to vRA8 - Using OneFuse Property Set for translation then select Run.

ServiceNow CMDB deployments

Migrate ServiceNow CMDB Deployments from vRA 7x VM to create OneFuse Managed ServiceNow CMDB Deployments. In addition, apply necessary OneFuse vRA Properties to the migrated vRA8/Cloud Deployment(s) so that when the deployment is destroyed from vRA8/Cloud, OneFuse will destroy the ServiceNow CMDB Deployments(s).

Optionally, if there are any vRA Properties that identify and/or filter the VMs for particular ServiceNow CMDB Deployments, it will be helpful to have a list to reference when running the workflow below.

  1. Log in to vRealize Orchestrator 7x.

  2. Select Library > Workflows from the left menu.

  3. Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > ServiceNow CMDB > From vRA7 > To vRA8

  4. Select the Workflow: Migrate ServiceNow CMDB Deployments from vRA7 to vRA8+OneFuse > select Run.

  5. Fill out the form fields.

  6. Select the [Run] button.

  7. Verify the Workflow completed successfully.

Migrate ServiceNow CMDB Deployments from vRA7 to vRA8+OneFuse

Field Label Description
Endpoints
OneFuse Endpoint Select the OneFuse Endpoint (created in prerequisite step 4, Installation and Setup).
Same OneFuse Endpoint name in vRA8? Select whether or not this OneFuse Endpoint Name is the same as the OneFuse Endpoint Name in the target vRA 8.2+/Cloud instance.
OneFuse Endpoint name in vRA8 (Shown when Same OneFuse Endpoint name in vRA8? is No)
Enter the OneFuse Endpoint name in the target vRA 8.2+/Cloud instance.
vRA 7.x Tenant Name Select from the dropdown the vRA 7 Tenant.
Policy and Config
OneFuse Policy Name to migrate to Select the OneFuse ServiceNow CMDB Policy Name to migrate the ServiceNow CMDB Deployments to from the dropdown.
Preferred order to select name to be migrated Select the order of preference to migrate the name from the dropdown.
Hostname, virtualMachineName - It will look at the Hostname property first
virtualMachineName, Hostname - It will look at the virtualMachineName property first
Limit scope based on vRA7 Business Group Choose whether or not to limit the migration to a specific vRA7 Business Group.
Business Group name (Shown when Limit scope based on vRA7 Business Group is Yes)
Select desired vRA7 Business Group Name.
Limit scope based on ALL vRA7 Properties - Number of Properties Filter VMs based on ALL specified number of vRA7 Properties.
(Migrate any Name on a VM, regardless of using SovLabs Heritage Plug-in for the module.)
Select from the dropdown:
0 - Do not Limit scope based on ALL
1 - Limit scope based on 1 vRA Property
2 - Limit scope based on 2 vRA Properties
3 - Limit scope based on all 3 vRA Properties
Limit scope based on ANY vRA7 Properties - Number of Properties Filter VMs based on ANY specified number of vRA7 Properties.
(Migrate any Name on a VM, regardless of using SovLabs Heritage Plug-in for the module.)
Select from the dropdown:
0 - Do not Limit scope based on ANY
2 - Limit scope based on matching at least one of the 2 vRA Properties
3 - Limit scope based on matching at least one of the 3 vRA Properties
Settings
Allow Ingest of duplicates Recommended to select No.
In the event this workflow runs multiple times and this is Yes, it will create the OneFuse Managed Object (regardless if another with the same values exist) and overwrite the vRA Property with the latest Managed Object reference.
Dry run? If Yes, this will not perform an actual migration. It will only provide logs for the actions this workflow would have perform.
Select No to perform a migration.
Error handling Select from the dropdown:
Roll back: Completely roll back all migration creation/vRA Properties injection
Skip failures and report: Will log the failure, continue with the migration and at the end, provide a summarized report via vRO Logs.
(The following variables for a particular Workflow run captures the outputs: managedObjectsPropString, ingestedManagedObjectsPropString, customPropertiesPropString, trackingIdPropString, resourceObjectsPropString and statusPropString. Please note that more output properties may exist.)