Home > vCloud Automation Center, vCloud Director > Migrate a VM from vCloud Director to vCloud Automation Center

Migrate a VM from vCloud Director to vCloud Automation Center


First, there’s no official automated procedure for the migration yet. Here is a method to get some of your vCD-managed VMs into vCAC.

  1. Because vCD names the actual VM with an ugly UID, we want to clone the VM to a “nice” name with vSphere.  As always, make sure you have sufficient room on your storage.  The destination cluster for the clone should already be included as a compute resource in vCAC/IaaS.
  2. In the vSphere Web Client, edit the clone VM, navigate to the “vApp Options” tab and uncheck “Enable vApp Options”.  This removes the vCloud Director properties from the VM.Disable vApp options
  3. Request (or wait for) an inventory data collection to run against the compute resource in vCAC.
    Request an Inventory update for the Compute Resource

    Request an Inventory update for the Compute Resource

  4. Login to vCAC as a Fabric Admin, navigate to Infrastructure|Infrastructure Organizer|Infrastructure Organizer.
  5. Click “Next” on step 1 of the Infrastructure Organizer wizardInfrastructure Organizer - Step 1
  6. On step 2, check the box beside the Compute Resource that contains the clone VM, click “Next”.Infrastructure Organizer - Step 2
  7. On step 3, ensure your compute resource is assigned to a Fabric Group and, optionally, a Cost Profile, click “Next” to continue.Infrastructure Organizer - Step 3
  8. In step 4, you’ll be presented with a list of the VMs in the compute cluster that are not managed by vCAC.  For each VM to be imported, click the pencil to edit it and assign to a Business Group.  Any VMs you do not want to import, just do not assign to a Business Group. Click “Next” when done.
  9. In step 5, you’ll edit your selected VMs to assigning them to an existing Blueprint, Reservation and Owner.  This is done so that vCAC knows how to handle the VM’s lease, resource allocation and who has access.  Next!Infrastructure Organizer - Step 5
  10. Last Step, verify how many machines will be registered.  Click Finish to complete the import.
  11. Once the VMs are imported, the owner or appropriate Business Group Manager can logon to vCAC, find the VM under his or her items and power it on from there.
  12. Lastly, once the VM’s operation is verified, the original VM in vCloud Director should be backed up and removed.


This is not intended to import a vApp into a multiple-machine blueprint or similar.  This is just for importing individual VMs into a Business Group.

I used vCloud Director v5.5.1.1 and vCloud Automation Center v6.0.1.1.

  1. Randy Johnson
    06/02/2014 at 12:45 pm

    Thanks for the info. We may need to do this soon.

    “This is not intended to import a vApp into a multiple-machine blueprint or similar.” Do you know if importing a vApp into a MM-blueprint is even possible?

    • 06/02/2014 at 1:26 pm

      I suspect there’s a programmatic way to import a vApp into an MM blueprint, but I don’t know it yet. Will definitely post about it when I know more.

      Thanks for reading, hope it helps!

  2. James Peifer
    06/04/2014 at 8:08 am

    Good day sir,
    Is there an added benefit from first making the change of a vCloud machine to vSphere prior to attaching it to vCAC? I only wonder because I have imported a few machines from both vSphere directly to vCAC as well as directly from vCD into vCAC. I only notice a few differences in the way they are brought in but for the most part they both function the same. The only problem I am having is getting the machine directly from vCD to take commands from vCO workflows just yet.

    • 06/07/2014 at 4:59 pm

      Technically, functionally, it shouldn’t matter. I suggested these steps so that the VM doesn’t complain about being managed by vCD and so the VM name is shorter and (maybe) compliant with the convention used in the vCAC workflows.

  1. 06/07/2014 at 4:47 pm
Comments are closed.
%d bloggers like this: