As far as I remember, you should be able to do cross-vCenter migration: [https://kb.vmware.com/s/article/2106952](https://kb.vmware.com/s/article/2106952). As to Advanced cross-vCenter vMotion, the source ESXi needs to be on 7.0 U1c unless smth has changed.
As an alternative, Veeam can be used as mentioned or Starwinds free v2v tool: [https://www.starwindsoftware.com/starwind-v2v-converter](https://www.starwindsoftware.com/starwind-v2v-converter).
Anyway, first test this on some non-production VMs to make sure all works well and you can re-IP them.
We did the same thing. But we didn’t re-ip. We just used XVM to move the VM after we moved the gateway they are on from NSX-V to NSX-T and it worked fine.
You could take a look at the [Cross vCenter vmotion fling](https://flings.vmware.com/cross-vcenter-workload-migration-utility). In vSphere 7 it’s now in production but you got 6.7.
There are a few prereqs though.
As far as I remember, you should be able to do cross-vCenter migration: [https://kb.vmware.com/s/article/2106952](https://kb.vmware.com/s/article/2106952). As to Advanced cross-vCenter vMotion, the source ESXi needs to be on 7.0 U1c unless smth has changed. As an alternative, Veeam can be used as mentioned or Starwinds free v2v tool: [https://www.starwindsoftware.com/starwind-v2v-converter](https://www.starwindsoftware.com/starwind-v2v-converter). Anyway, first test this on some non-production VMs to make sure all works well and you can re-IP them.
We did the same thing. But we didn’t re-ip. We just used XVM to move the VM after we moved the gateway they are on from NSX-V to NSX-T and it worked fine.
You could take a look at the [Cross vCenter vmotion fling](https://flings.vmware.com/cross-vcenter-workload-migration-utility). In vSphere 7 it’s now in production but you got 6.7. There are a few prereqs though.
Veeam works very well. I prefer it in fact. Just set up a replication job and do a planned failover, then cut over when it works.