For a decade, the most reliable objection in any Nutanix evaluation had nothing to do with the hypervisor. It was the array. “We have three years left on our SAN — moving to HCI means writing it off.” I have watched that single line kill more AHV proposals than any technical gap ever did. As of mid-2026, the objection is mostly dead: Nutanix now runs compute-only nodes against Pure Storage FlashArray over NVMe/TCP, Dell PowerFlex is supported, NetApp ONTAP and Dell PowerStore are in early access, and January’s FlashStack with Nutanix launch turned the Pure option into a pre-validated converged stack from Cisco, Pure, and Nutanix.
This brief covers what actually shipped, what it does to the VMware-exit math, and who should still buy integrated Nutanix nodes anyway.
What changed
Nutanix built its brand on collapsing three-tier infrastructure. Every node ran AOS, compute and storage scaled together, and your existing array had no role except the recycling dock. That architecture was the pitch — and the problem, because it forced a storage buy into every deal.
Through 2025 and into 2026, Nutanix deliberately walked that back. Nutanix Cloud Infrastructure now supports compute-only clusters that consume external arrays: Pure Storage FlashArray (//X, //XL, and //C models) over NVMe/TCP is generally available, Dell PowerFlex is supported through its native SDC client on PowerEdge servers, and NetApp ONTAP — announced at .NEXT 2026 as an NFS-based integration — is in early access with general availability targeted for the second half of 2026. Dell PowerStore sits in early access as well.
Then on January 13, 2026, Cisco, Pure Storage, and Nutanix announced general availability of FlashStack with Nutanix: UCS compute, FlashArray storage, and NCI with AHV as a jointly validated converged architecture, with lifecycle management stitched across Intersight, Prism, and Pure1. That is not a compatibility footnote. It is three vendors co-selling a packaged alternative to vSphere on converged infrastructure.
Why it matters for the VMware-exit math
Every VMware-exit business case I have seen since the Broadcom acquisition has the same three ugly lines: new hardware, data migration, and project risk. External storage support attacks all three.
- Hardware: an array with two or three years of depreciation and support left keeps doing its job. You buy compute-only nodes, not a full HCI refresh.
- Migration: the data does not move. You present the same array to AHV compute-only nodes, migrate VMs off ESXi, and retire hosts. Zero-data-migration is the phrase that changes steering-committee body language.
- Risk: a hypervisor swap with storage in place is a materially smaller project than a hypervisor swap plus a storage platform swap. Fewer moving parts, shorter rollback path.
The verdict is short: the single largest capex objection in the Nutanix column of your Nutanix vs. VMware cost model just left the spreadsheet. If you priced an AHV migration in 2024 and rejected it on hardware grounds, that number is stale. Reprice it.
The external storage matrix, as of mid-2026
| Protocol | Status (mid-2026) | Notes | |
|---|---|---|---|
| Pure Storage FlashArray | NVMe/TCP | GA | //X, //XL, //C qualified; the FlashStack with Nutanix reference design |
| Dell PowerFlex | PowerFlex SDC client | GA | Runs on PowerEdge; software-defined, not NVMe/TCP |
| NetApp ONTAP | NFS | Early access | Announced at .NEXT 2026; GA targeted second half of 2026 |
| Dell PowerStore | NVMe/TCP | Early access | Timeline not yet firm — plan accordingly |
Read the status column literally. Early access means you can pilot, not that you can build a Q4 production migration on it. And every row carries qualifications — supported server platforms, protocol constraints, and feature dependencies — so treat the hardware compatibility list as a gate, not a suggestion.
The vendor-by-vendor read
Pure Storage: first mover, deepest integration
Pure got there first and it shows: NVMe/TCP end to end, three FlashArray families qualified, and the only external option wrapped in a jointly validated converged design. If your arrays are already Pure, this is the shortest credible path off ESXi. The trade-offs are the usual ones — FlashArray carries premium list pricing, and the FlashStack design assumes you are willing to standardize on the Cisco-Pure pairing. Pure’s Evergreen consumption model, though, dovetails neatly with the whole premise here: keep the array, upgrade in place, stop forklifting.
Dell: the biggest installed base, the most mixed incentives
Dell brings two tracks. PowerFlex is generally available today, but it is a software-defined system using Dell’s own SDC client rather than NVMe/TCP, and it expects PowerEdge underneath — fine if you are a Dell shop, irrelevant if you are not. PowerStore, the array most mid-size enterprises actually own, is still early access. Be clear-eyed in account conversations: Dell also sells competing stacks and has its own hypervisor-adjacent interests, so the enthusiasm of your Dell team for a Nutanix attach may vary. Push for roadmap dates in writing.
NetApp: the sleeper, if the date holds
The ONTAP integration announced at .NEXT 2026 matters because of who owns ONTAP: a huge share of exactly the enterprises now staring at Broadcom renewal quotes. NFS-based consumption keeps it operationally simple. The caution is timing — early access now, GA targeted for the second half of 2026. If your renewal lands before the GA date plus a sensible pilot window, ONTAP support is a 2027 lever, not a 2026 one.
Cisco: the packaging play
Cisco’s contribution is UCS compute and the validated-design muscle that makes FlashStack with Nutanix a one-motion purchase — reference architecture, joint support posture, Intersight lifecycle management. For shops already standardized on UCS, that removes most of the integration homework. Worth remembering: after HyperFlex’s retirement, Cisco needed a hyperconverged-adjacent answer, and this is it. Cisco sells the compute either way — which is precisely why the partnership is stable.
Nutanix: a reversal, and a smart one
Credit where due — Nutanix spent years arguing three-tier was legacy, and now it sells into three-tier. That is pragmatism, and it widens the funnel enormously. The honest caveat: on external arrays, data services live on the array. Compression, dedupe, snapshots, and replication become the array vendor’s job, and some AOS-native capabilities do not apply. The “one platform, one support call” story gets more nuanced the moment a second storage vendor is in the room.
Who should still buy integrated Nutanix nodes
External storage support does not kill the HCI pitch; it narrows it to where it was always strongest. Buy integrated nodes when the array is within roughly twelve months of a support renewal or refresh anyway, when you are deploying edge or ROBO sites where a SAN never made sense, or when you want one operational model and one throat to choke — AOS data services, native DR, and a single upgrade train. That consolidation value is real; it was just never worth writing off a healthy array to get.
My rule of thumb: two or more years of array support runway and adequate headroom, go compute-only against the array. Renewal inside twelve months, price both paths — the integrated node quote will often be closer than you expect once array support renewal costs land in the model.
What to do about it
- Inventory array support runway and utilization before any vendor conversation. The array’s remaining life is now a negotiating asset in every VMware alternatives evaluation, not a constraint.
- Ask Nutanix to quote compute-only nodes against your existing array and full HCI nodes side by side. Make them show both numbers.
- Check feature dependencies early: metro clustering, synchronous replication, and backup vendor integration behave differently on external storage than on AOS. Get specifics per array, in writing.
- Pilot on a non-production cluster before committing a migration wave — especially anything currently in early access.
- If you are also weighing keeping vSphere but dropping vSAN, run the same array-reuse logic across the vSAN alternatives field; the pattern is identical.
The takeaway for the meeting: Nutanix no longer requires a storage decision to make a hypervisor decision. Price your exit accordingly.
Frequently asked questions
Does Nutanix AHV support external SAN storage?
Yes. As of mid-2026, Nutanix compute-only clusters can consume Pure Storage FlashArray over NVMe/TCP and Dell PowerFlex in general availability, with NetApp ONTAP (NFS) and Dell PowerStore in early access. Support comes with qualified hardware lists and protocol requirements, so verify your exact configuration.
What is FlashStack with Nutanix?
A converged infrastructure architecture from Cisco, Pure Storage, and Nutanix, generally available since January 2026. It pairs Cisco UCS servers and Pure FlashArray with Nutanix Cloud Infrastructure and AHV, validated jointly and managed through Intersight, Prism, and Pure1.
Do I lose Nutanix data services with external storage?
Some. On external arrays, capacity efficiency and replication are handled by the array rather than AOS, and certain AOS-native features do not apply to compute-only deployments. Map your DR and backup requirements against the specific array integration before committing.
Is moving to Nutanix cheaper than renewing VMware?
It depends on your renewal quote, host counts, and hardware timing — but external storage support removes the forced array write-off that used to sink the comparison. Model compute-only nodes against your existing array before assuming the incumbent renewal wins.
Enterprise Techie publishes vendor-honest analysis like this daily — get the brief by email, free.