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.
We can use the tool to move anything from a different hypervisor to Nutanix, but we cannot do it the other way around. We cannot use the solution to move a machine from Nutanix to other hypervisors. If there is no vCenter in an organization, the product must be able to pick machines directly. It should point to vSphere and migrate the machine directly from vSphere instead of moving it from vCenter.
System Administrator at a financial services firm with 1,001-5,000 employees
Real User
Top 20
Jan 4, 2023
We'd like Nutanix to be more flexible in the future. You need to have VM Tools configured with the VM guest host. Without VM Tools, you can't use Move.
The solution can be improved by adding the ability to see all the virtual machines running in a cluster without having to enter the specific name of the host or its IP address. It can't migrate virtual appliances that are proprietary because it does not have access to the source code and does not know what modifications have been made.
Senior Account Executive - All Things Software Defined at a tech services company with 51-200 employees
Real User
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.
Nutanix Move simplifies this process with infrastructure-level bulk VM migrations, removing the friction associated with onboarding new infrastructure, and enabling businesses to quickly leverage the full potential of Nutanix Enterprise Cloud, with near-zero VM or application service outage during migrations.
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.
We can use the tool to move anything from a different hypervisor to Nutanix, but we cannot do it the other way around. We cannot use the solution to move a machine from Nutanix to other hypervisors. If there is no vCenter in an organization, the product must be able to pick machines directly. It should point to vSphere and migrate the machine directly from vSphere instead of moving it from vCenter.
They should have some tools to migrate the workload from another Nutanix platform.
Nutanix Move could be made more scalable, so you could do more instead of taking five or ten VMs at a time.
We'd like Nutanix to be more flexible in the future. You need to have VM Tools configured with the VM guest host. Without VM Tools, you can't use Move.
The solution can be improved by adding the ability to see all the virtual machines running in a cluster without having to enter the specific name of the host or its IP address. It can't migrate virtual appliances that are proprietary because it does not have access to the source code and does not know what modifications have been made.
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.