The automated migration feature is the most effective. It automates the whole process, like installation from VMware to Nutanix AHV cluster. It retains the IP and MAC addresses of VMs and cleans up migrated VMs by removing VMware tools from the source. The automated migration is seamless - when we do the cutover, Nutanix Move powers off the source VM and automatically powers on the virtual machine on the Nutanix cluster.
When you have regular questions, like how do I do something in the tool or when you want to know when can I do anything in the product, the solution's support team can take around three to four days to give you an answer, or they may even sometimes take more time.
I think Nutanix Move could be improved by adding a way to retry failed migrations. Sometimes when seeding fails, there's no way to redo it without recreating the whole migration plan. I'd like a button to restart the process without creating a migration plan.
The most valuable feature is the automation. The solution will clone the data that you want to migrate, shut down the virtual machine, disconnect it from the network and start the clone virtual machine inside the solution's platform.
Senior Account Executive - All Things Software Defined at a tech services company with 51-200 employees
Dec 27, 2021
We can migrate from Hyper-V to Acropolis, but we can't move from Acropolis back to Hyper-V. However, we do not have customers who want to, but if we could reassure them that it was possible it would be better. Having our Hyper-V customers have a two-way option that may help. A customer would like to hear that if they do switch they can switch back. I know it's a limitation on Hyper-V but not a limitation on VMware.