March 28, 2023

Many organizations nonetheless run at the least a bit of their infrastructure on outdated bodily servers or legacy/non-VMware virtualization of their knowledge facilities. The upkeep and day-to-day operations turn into a extra vital problem every single day due to the outdated {hardware} and hypervisors being out of help.

Due to that, these organizations search for doable options to cope with it by investing minimal money and time. One of many many choices is emigrate these workloads to a contemporary and up-to-date virtualization platform.

It makes such migrations an important a part of the Cloud Suppliers’ choices to allow them to be aggressive and ship a useful service to their tenants.

VMware Cloud Director Availability already provides a migration choice for legacy vSphere workloads working on vSphere 5.5U3, 6.0U2, and 6.0U3. [Read more]

A number of different instruments present migration capabilities from legacy or non-vSphere sources, however they’re often costly or have fairly a couple of limitations with regards to VMware Cloud Director clouds being the vacation spot. 

ObserveVCPP companions are charged 0 factors per migrated workload utilizing VMware Cloud Director Availability.

VMware Merchandise in Scope

Product Objective
vCenter Converter Standalone Convert and migrate the VMs from the supply non-vSphere or Legacy vSphere to an intermediate vSphere
vSphere Intermediate for the migration course of. Vacation spot for the vCenter Converter Standalone conversions and a supply for the VMware Cloud Director Availability migrations to VMware Cloud Director
VMware Cloud Director Availability Migrations from the intermediate vSphere to the vacation spot VMware Cloud Director cloud underneath the specified group
VMware Cloud Director The vacation spot cloud

Please notice that the next merchandise must run interoperable variations:

  • vCenter Converter Standalone with Intermediate website vSphere
  • VMware Cloud Director Availability with Intermediate website vSphere and Vacation spot website VMware Cloud Director

To grasp extra in regards to the supported variations, please discuss with the VMware Interoperability Matrix.


There are a number of prospects when providing a workload migration service from non-vSphere or legacy vSphere sources:

  • As a self-service totally operated by the tenant
  • As a totally managed service by the supplier
  • As a combined service – a part of the operations are dealt with by the tenant and the remaining by the Cloud Supplier


With Converter Standalone, you possibly can convert bodily machines, legacy VMware, and Hyper-V digital machines. Since there are a number of specifics about every machine sort, you could find extra details about every of the supported sources here.

You may set up Converter Standalone parts solely on Home windows working programs. Converter Standalone helps Home windows and Linux working programs as sources for powered-on-machine conversions and virtual-machine conversions. You can’t reconfigure Linux distributions.

You could find extra in regards to the supported Working Methods here.

For any conversion limitations, please verify here.


To use any Visitor Customization properties on the migrated VM on the vacation spot website, VMware instruments must be put in earlier than the migration to the tenant group is initiated. It may be executed previous to beginning the method whereas the VM is working on the supply or after it’s transformed on the intermediate website. 


Migrating Legacy and non-vSphere Workloads to VMware Cloud Director - Flow

The steps are as follows:

  1. Put together the vacation spot cloud if it doesn’t have VMware Cloud Director Availability working.
  2. Deploy and configure the intermediate website.
  3. Deploy vCenter Converter Standalone and its parts accordingly on the supply website.
  4. Convert a VM/bodily machine to the intermediate website. 
  5. Confirm all of the properties (GuestOS sort, model, SCSI controller, and many others.) are accurately populated by way of the vSphere UI. 
  6. (Elective) Energy on the VM if wanted.
  7. Configure the migration utilizing VMware Cloud Director Availability. 
  8. (Elective) If the VM is powered off, carry out a handbook sync.
  9. (Elective) Configure the Restoration settings – Community configuration (Re-IP), Visitor Customization. 
  10. Provoke the migration.

The non-optional steps are marked with their numbers on the diagram.

Vacation spot Web site

For the reason that supposed vacation spot for the transformed workloads is VMware Cloud Director, the presumption is that the VMware Cloud Director cloud (together with its group construction) is already in place. If, for some purpose, it isn’t, please comply with the VMware Cloud Director documentation to set it up correctly.

The primary necessary requirement is to have all of the VMware Cloud Director Availability home equipment deployed and configured on the VMware Cloud Director cloud.

You may discuss with the VMware Cloud Director Availability Reference Architecture and documentation for particular recommendations and directions on how you can do it.

The cloud website is prepared for migrations when VMware Cloud Director Availability is prepared, and its Service Endpoint deal with is accessible.

Intermediate Web site

The intermediate website might be deployed and managed by the Cloud Supplier or by the tenants of their knowledge heart. Which choice is extra appropriate should be decided primarily based on a number of elements equivalent to price, obtainable {hardware}, workload criticality, and many others.The positioning should run vSphere 6.7U3 (already previous Finish of Basic Assist), 7.0, 7.0U1, 7.0U2, or 7.0U3. There should be at the least one present consumer with the next permissions required by vCenter Converter Standalone.

One of many following vSphere licenses ought to be utilized:

  • vSphere Analysis license (if the migration is completed inside 60 days of provisioning the vSphere intermediate website)
  • vSphere Necessities Plus
  • vSphere Normal
  • vSphere Enterprise
  • vSphere Enterprise Plus
  • vSphere Desktop

The vCenter deal with should be accessible from the vCenter Converter Standalone machine.

There are two doable choices for the deployment of the Intermediate vSphere surroundings:

  • A devoted vSphere per tenant with a VMware Cloud Director Availability On-Premises to Cloud Director Replication equipment paired to the tenant Group within the VMware Cloud Director cloud. It can be a vSphere surroundings working on the tenant’s infrastructure and managed by them.
Migrating Legacy and non-vSphere Workloads to VMware Cloud Director - Self-service
  • A shared vSphere with a VMware Cloud Director Availability On-Premises to Cloud Director Replication equipment per tenant paired to the tenant Group within the VMware Cloud Director cloud.
Migrating Legacy and non-vSphere Workloads to VMware Cloud Director - Managed service

Possibility #1 is appropriate when the Cloud Supplier provides the migration as a self-service or a combined service. Then the tenants can management the entire course of or simply a part of it. For instance, the deployment and operation of the vCenter Converter Standalone. Choices #2 is appropriate when the Cloud Supplier provides a managed service as a result of limiting the visibility of tenants solely to their sources in a shared vSphere surroundings is likely to be difficult.

TipTo optimize the fee accrued to the Cloud Supplier by working the Intermediate website, the transformed VMs can stay powered off and immediately be migrated to the cloud(Chilly Migration). It is going to require a handbook sync after the migration is configured however will permit even a deployment with much less compute sources for the Intermediate vSphere surroundings. It may possibly additionally make the most of a slower however cheaper storage resolution (NFS, for instance). Nevertheless, these deployment choices ought to be made solely after contemplating the variety of workloads that shall be migrated. Additionally, this strategy would possibly result in a greater downtime interval for the transformed workload.

Deployment steps

These steps should be adopted to get the intermediate website able to accommodate the transformed VMs.

  1. Deploy and put together the vSphere infrastructure in response to the chosen design (configure networking, storage, and many others.). VMware Cloud Foundation can be utilized for automating the deployment course of. 
  2. Deploy the VMware Cloud Director Availability On-Premises to Cloud Director Replication equipment following the steps supplied within the documentation
  3.  Run the preliminary setup wizard of the newly deployed equipment to pair it with the vacation spot cloud. Use the VMware Cloud Director Availability Service Endpoint deal with and Group administrator credentials (relying on the design, the credentials ought to be for a tenant or system Group).
  4. Create a consumer for vCenter Converter Standalone with at the least these permissions.
  5. Carry out all of the community configurations essential to make the vCenter accessible from the tenant website. 

TipThroughout the preliminary setup wizard, think about enabling the Permit entry from Cloud setting, which can allow you to configure the migration from the cloud website. 

Supply Web site

Due to the assorted sources supported by vCenter Converter Standalone (see Limitations for extra info) and every has totally different necessities, there isn’t any advisable structure for the supply website. 

Probably the most appropriate conversion strategy ought to be decided by the machine (digital or bodily) proprietor in response to its compliance with the vCenter Converter Standalone necessities and limitations.

For instance, it’s doable to transform a Hyper-V VM utilizing two strategies:

  • Powered-off digital machine conversion
  • Powered-on machine conversion

A call should be made primarily based on the Visitor OS distribution, its compatibility with vCenter Converter Standalone, and another elements, equivalent to downtime, the necessity to modify the community configuration, and many others.

In case any configuration modifications to the Visitor OS are required throughout the migration (equivalent to community reconfiguration, laptop title change, and many others.), then VMware instruments shall be necessary to be put in. Please discuss with the Considerations part for extra info on what is required.


A number of steps might be automated to cut back the quantity of handbook work.

  1. Transport the binaries and silent set up of VMware instruments. (Link for Windows & Link for Linux)
  2. Intermediate website deployment by way of VMware Cloud Basis. (Link)
  3. OVF Instrument to deploy the VMware Cloud Director Availability On-Premises to Cloud Director Replication equipment on the Intermediate website. (Link)
  4. Set up vCenter Converter Standalone by way of command-line. (Link)


You could find an in depth instance of the method in our Migrating Legacy and non-vSphere Workloads to VMware Cloud Director doc.


Although the circulation requires a number of handbook steps, most are trivial and require no particular data. Following the documentation is enough for the profitable completion of the duties. Nonetheless, a few of them might be automated to cut back the quantity of handbook work.

The mix of vCenter Converter Standalone and VMware Cloud Director Availability is a sensible and environment friendly resolution for migrating workloads from legacy or non-vSphere environments to VMware Cloud Director clouds with minimal effort. It may possibly take only a few hours to efficiently migrate and power-on a workload within the VMware Cloud Director cloud.

The fee-effectiveness of this resolution can be a undeniable fact that ought to be thought-about (0 factors per migration).

Bear in mind, to get the newest updates, verify this weblog repeatedly, you can also discover us on SlackFacebookTwitterLinkedIn in addition to many demo movies and enablement YouTube, particularly our Feature Fridays series!