top of page

Actual v2t Migration

For today's Blog I will show you the actual process of v2t migration I successfully completed.


I have this project in our company that I'm involved with. To migrated all 202 tenant Org VDCs from NSX-V to NSX-T backing type network.


Important need to prepare before initiating the v2t migration:


To do the pre-check


  • Open CMD point the directory in your nsx migration tool folder path and run vcdNSXMigrator.exe --filepath E:\VMware-NSX-Migration-for-VMware-Cloud-Director-1.4.2\vcdNSXMigrator\V2T_South\OrgVDC.yml --passwordFile passfileGC --preCheck

  • We can see the output below that the pre-check is successful meaning it's ready for v2t migration

  • In case there is an error you need to fix or remediate that


To initiate the migration


  • Run this next command >> vcdNSXMigrator.exe --filepath E:\VMware-NSX-Migration-for-VMware-Cloud-Director-1.4.2\vcdNSXMigrator\V2T_South\OrgVDC.yml --passwordFile passfileGC

  • Here is the successful output

  • We can see here that Target or Destination Org VDC is created included the edges, routed, isolated and imported networks

  • Also we can see that vApp and VM is moved to the destination Org VDC


Note: Before running the clean up you should get client health check confirmation. Once clean up is initiated and successful you can't rollback anymore.


To initiate the clean up


  • Run this command >> vcdNSXMigrator.exe --filepath E:\VMware-NSX-Migration-for-VMware-Cloud-Director-1.4.2\vcdNSXMigrator\V2T_South\OrgVDC.yml --passwordFile passfileGC --cleanup

  • Once clean up process is completed you will notice that Source Org VDC is deleted and renamed the Destination Org VDC same to the Original Naming included the networks

  • That's All :)



Note: This is my personal and owned experience that I love to share in the VMware Community. I hope you appreciate it, thank you

Recent Posts

See All

Can't delete vApp and VM

Error: [ bfe374cf-fd73-4076-86da-e842ba50b13a ] No row with the given identifier exists: [com.vmware.vcloud.common.model.logicalresource.VdcLogicalResourceModel#f8e04f29-5810-4fe6-9178-94b7ab049f25] W

bottom of page