VMware to Nutanix: What the Migration Actually Involves
Nutanix comes up in almost every VMware exit conversation, and for good reason. But the question that matters is not whether it is a credible platform, it clearly is. It is what moving there actually involves, where it fits and where it does not. Here is an honest, vendor neutral walk through, from someone with no platform to sell you.
Since Broadcom moved VMware to per core subscription and withdrew perpetual licences, a lot of organisations are looking at alternatives for the first time in a decade. Nutanix is usually the first name on the list. That is partly merit and partly marketing, so it is worth separating the two before you commit to anything. This guide assumes you have already decided to evaluate leaving VMware. If you are still weighing that bigger question, start with should you leave VMware, and if you want the platform neutral mechanics of any migration, read migrating off VMware alongside this. Here we focus on the specifics of one destination.
What you are actually moving to
Nutanix is a full infrastructure stack, not just a hypervisor. The pieces worth understanding before you plan anything are these.
AHV is the native hypervisor. AHV is built on KVM and ships as part of the Nutanix platform at no separate hypervisor licence cost. This is the single biggest commercial difference from VMware, where the hypervisor is the thing you are now paying a subscription for. On Nutanix the hypervisor is included, and the licensing sits at the platform layer instead. You can run ESXi on Nutanix hardware if you want to, but doing so keeps you paying VMware, so most organisations moving for commercial reasons adopt AHV.
Licensing is per core and term based. Nutanix licenses its software, branded under names such as Nutanix Cloud Infrastructure, on a per core subscription with a term commitment. So you are not escaping the per core model itself, you are changing who you pay and what you get for it. The honest comparison is total cost over the term against a right sized VMware renewal, not a headline sticker price. Model both properly before you decide, because the answer genuinely varies by estate.
Hardware portability is real but bounded. Nutanix runs on its own NX appliances and on validated platforms from several major server vendors. That gives you choice, and in many cases you can run Nutanix on hardware you already own or are about to buy. It is not unlimited, the hardware has to be on the supported list, so check your specific models rather than assuming any server will do.
VMware sells you a hypervisor and a stack of software on top. Nutanix sells you a hyperconverged platform with the hypervisor included. You are not just swapping one hypervisor for another, you are changing the shape of the whole stack, the management tools, and the operational habits your team has built over years. Price the move on that basis, not on the hypervisor line alone.
What the migration actually involves
The hypervisor cutover is the part everyone pictures, and it is rarely the hard part. The effort lives in the surrounding dependencies. Here is the honest sequence.
The tooling exists, and it is good
Nutanix provides a migration tool, Nutanix Move, that handles the bulk of the virtual machine conversion from ESXi to AHV. It installs the right drivers, replicates the data while the source keeps running, and lets you cut over with a short final sync. For standard server workloads this part is genuinely well trodden. Move is not the constraint. The constraint is everything that touches those virtual machines.
What moves easily
Stateless and loosely coupled workloads move with little drama. Web tiers, application servers, test and development estates, and most general purpose Windows and Linux virtual machines convert cleanly. If your estate is mostly this, a Nutanix migration is a very manageable project.
What does not move easily
The hard parts are the same ones that make any hypervisor exit hard, and they deserve naming explicitly.
- Backup and disaster recovery interlock. Your backup tooling, replication and DR runbooks are written against VMware constructs. Most major backup vendors support AHV well now, but support is not the same as a working, tested recovery. You are effectively rebuilding and revalidating your recovery position, not just repointing it.
- Networking and security dependencies. Firewall rules, microsegmentation, load balancer integrations and any third party network virtualisation need to be reproduced on the new platform. Nutanix has its own approach to network policy, so this is a redesign in places, not a copy.
- Application support statements. Some software vendors certify their product only on named hypervisors. It usually runs fine on AHV, but if you need a formal support statement for a regulated or business critical application, confirm it before you migrate that workload, not after.
- VDI and specialist platforms. Virtual desktop estates, GPU heavy workloads and tightly integrated appliances carry their own integration questions and should be scoped individually rather than swept into the general migration.
- Operational tooling and skills. Your monitoring, automation, infrastructure as code and day to day runbooks assume vCenter. Prism, the Nutanix management plane, is capable and many teams prefer it, but there is a genuine reskill and a rebuild of automation to account for.
The virtual machines are the easy part. Data gravity, DR coupling, network and firewall dependencies, application certification and operational tooling are where the real effort and the real risk sit. A Nutanix migration succeeds or fails on how well you map those before you start, not on the conversion tool.
Where Nutanix fits well, and where it does not
This is the part the platform's own marketing will not give you straight. Nutanix is a strong product, and it is the right answer for some estates and the wrong one for others.
Where it fits well
Strong candidates
Estates that value the hyperconverged model and want compute and storage managed as one platform. Organisations facing a sharp VMware uplift whose workloads are mainstream rather than exotic. Teams that want a single vendor for the infrastructure stack with the hypervisor included, and that are happy to reskill onto Prism and AHV. Distributed or edge heavy estates where the operational simplicity of one platform across sites is worth a lot.
Where it fits less well
Think harder before committing
Estates that have just invested heavily in the broader VMware Cloud Foundation stack and genuinely use it, where the like for like replacement is more work than it looks. Organisations whose strategy is moving toward a disaggregated, three tier architecture, where staying hyperconverged on any platform may be the wrong direction. Workloads with hard third party certification requirements on a specific hypervisor. Teams with deep VMware automation they cannot afford to rebuild quickly.
That second column matters. If your real question is whether hyperconverged is still the right model at all, moving from one HCI platform to another may solve the licensing problem while locking in an architecture you were ready to outgrow. We cover that thread in disaggregating from HCI, and it is worth reading before you assume like for like.
The real considerations and blockers
Beyond fit, a handful of practical things decide whether a Nutanix move goes smoothly.
- Total cost over the term. Nutanix removes the VMware hypervisor subscription but adds its own platform subscription. The saving is real for many estates, but it is not automatic. Model the full term cost against a properly right sized VMware renewal, including the migration project itself, before you treat it as a saving.
- Lock in moves, it does not vanish. A single vendor stack with the hypervisor included is convenient, and it is also a new dependency. Go in with eyes open about what leaving Nutanix would later involve, so you are choosing the trade rather than stumbling into it.
- Hardware refresh timing. If you have a hardware refresh due anyway, the economics of moving improve a lot, because you are buying new kit regardless. If your hardware is mid life, the picture is different.
- The parallel run. Do not collapse the old environment until the new one has proven itself through a real recovery test and a representative workload at scale. Rushing this is where migrations go wrong.
None of this is a reason not to choose Nutanix. It is a strong, mature platform and for the right estate it is an excellent destination. The point is to choose it on evidence, with the blockers mapped, rather than because it was the first alternative anyone named.
Weighing Nutanix against the alternatives?
Send us your estate and your renewal position. We will give you an independent, vendor neutral read on whether Nutanix fits, what the migration would really involve, and how the total cost compares with a right sized VMware renewal. We have no platform to sell and no preferred destination.
Prefer email? Reach us directly at hello@c4cgroup.co.uk.
Frequently asked questions
Is Nutanix a like for like replacement for VMware?
Not exactly. Nutanix replaces the function, running virtual machines on a hyperconverged platform, but it is a different stack with its own hypervisor, AHV, its own management plane, Prism, and its own way of handling networking and DR. Most mainstream workloads move cleanly, but it is a platform change, not a drop in swap, so plan for some redesign and a team reskill.
Does Nutanix get rid of per core licensing?
No, it changes who you pay. Nutanix licenses its software per core on a term subscription, so the per core model itself does not disappear. What changes is that the hypervisor, AHV, is included rather than billed separately as VMware now is. The real comparison is total cost over the term against a right sized VMware renewal, including the migration project, not a headline price.
How do you actually move the virtual machines?
Nutanix provides a migration tool, Nutanix Move, that converts virtual machines from ESXi to AHV. It installs the right drivers, replicates data while the source keeps running, and lets you cut over with a short final sync. For standard server workloads this part is well trodden. The harder work is reproducing backup, DR, networking and application dependencies around those machines.
What is the hardest part of a Nutanix migration?
Not the hypervisor cutover. The effort and the risk sit in data gravity, disaster recovery interlock, networking and firewall dependencies, application support statements and operational tooling. The virtual machines convert easily, the runbooks and integrations around them do not. Mapping those before you start is what decides whether the project goes smoothly.
When is Nutanix the wrong choice?
When you have just invested in and genuinely use the broader VMware Cloud Foundation stack, when your strategy is moving toward a disaggregated, three tier architecture rather than staying hyperconverged, when a critical application is certified only on a specific hypervisor, or when you have deep VMware automation you cannot afford to rebuild. Nutanix is excellent for the right estate, but it is not universal.