VMware

What vSAN to native HCI exit economics actually look like in 2026.

The migration math advertised by the alternative HCI vendors compares a stale vSAN baseline against an optimistic target. The realised math, computed against a 2026 vSAN renewal and a verified replacement run cost, is narrower and more conditional on the buyer's storage policy mix than most exit business cases acknowledge.

By The Negotiation Desk · VMware · Archetype: The Exit

Published 17 Nov 2025 · Updated 1 May 2026

The vSAN exit conversation has accelerated across 2026 in lockstep with the VCF renewal cycle. The alternative HCI vendors, including Nutanix, Pure Storage, HPE SimpliVity, and the major hyperscaler native HCI offerings, are actively pursuing the vSAN installed base with detailed migration proposals. The proposals reach the buyer's procurement team with detailed five year run cost models and with confident headline migration savings. The Desk has worked through 13 vSAN to native HCI scenarios across 2026 to date, and the realised economics on the engagements that progressed to a signed replacement contract were materially different from the headline numbers in the original migration proposal. This article reports what we have seen.

The article is not an opinion on whether the buyer should exit vSAN. The Desk is buyer side and vendor independent. The Desk's posture is that the exit decision is the buyer's, taken against an accurate economic model and a clear view of the buyer's storage policy reality. The article reports the inputs and the patterns that make the model accurate. The decision itself is not within the scope of this piece.

The baseline question: which vSAN number is the right number

The first economic question is which vSAN number to compare against. The buyer's prior vSAN spend, the renewal quote as opened by the seller, and the renewal quote as cleared with serious negotiation work all sit on materially different lines. The Desk's 2026 vSAN renewal book shows a median realised renewal price that is between 28 and 39 percent below the opening renewal quote. The buyer that compares the alternative HCI proposal against the opening vSAN renewal quote is comparing against a number that the buyer would not pay if a serious renewal negotiation ran in parallel.

The right comparison point is the realistically cleared vSAN renewal price across the term. That is the number the buyer would pay if no migration occurred. A migration business case that anchors against any other vSAN number overstates the migration value. The overstatement on the Desk's 2026 sample averaged 22 percentage points of headline TCO reduction.

The replacement landing question: which HCI number is the right number

The second economic question is which replacement HCI number to compare to. The proposal in the buyer's hand is reliably a first year landed cost with an aggressive year one discount and a less defined discount profile across years two through five. The realised run cost across years two through five is reliably above the buyer's planning assumption because the year one discount is the largest discount in the contract life and because the year two uplift is a separate negotiation that occurs after migration commitment.

The right comparison number is the steady state run cost across years three through five, not the year one landed cost. The migration business case that anchors on year one understates the steady state replacement run cost by between 13 and 21 percent on the Desk's 2026 sample. The gap is enough to invert the headline migration value on several of the engagements that brought the business case to the Desk.

"The exit decision is the difference between the cleared vSAN renewal across the term and the steady state replacement run cost across the same term, net of the migration cost. The headline number in the vendor proposal is rarely the decision number."Storage Migration Lead, The Desk

The migration cost question: the storage policy refactor

The third economic question is the migration cost. The migration cost on a vSAN exit is dominated by the storage policy refactor. vSAN storage policies are defined in vSphere terms, are bound to application workload requirements through cluster level policy assignments, and are reliably the most opaque dependency in the buyer's storage architecture. The replacement HCI platform does not consume vSphere storage policies natively. The policies have to be translated, refactored, or replaced.

The Desk's 2026 sample shows that the storage policy refactor reliably exceeds the planning estimate by between 34 and 52 percent and accounts for the largest share of business case slippage on the vSAN exit. The slippage concentrates in three categories. The first is the policy inventory itself, which is often incomplete in the buyer's documentation and requires a fresh inventory effort. The second is the policy to platform mapping, which is rarely a clean one to one mapping and often requires the consolidation or splitting of policies across the replacement platform. The third is the application validation effort, which has to confirm that the refactored policy delivers the same effective storage behaviour as the prior policy.

The dual run period for a vSAN exit is reliably longer than the dual run period for a compute exit because the storage migration cannot be staged with the granularity of a compute migration. The Desk's sample shows a median dual run period of 11 months, with regulated workloads extending the dual run beyond 18 months in a material share of cases.

The realised exit economics on the Desk's 2026 sample

The Desk's 2026 sample includes 13 vSAN to native HCI scenarios, of which 6 progressed to a signed replacement contract, 4 progressed to a renegotiated vSAN renewal that used the replacement proposal as a negotiation reference, and 3 remained on the buyer's evaluation desk at the time of writing. The 6 signed replacement scenarios produced a median TCO reduction of 8 percent across a five year horizon, computed against the realistically cleared vSAN renewal and the steady state replacement run cost net of the actualised migration cost. The headline reduction in the original replacement proposal across the same 6 scenarios had a median of 34 percent. The realised reduction was 26 percentage points narrower than the headline reduction.

The 4 renegotiated vSAN scenarios produced a median TCO reduction of 17 percent across the same horizon, computed against the opening vSAN renewal quote and the realistically cleared vSAN renewal. The renegotiated vSAN reduction was wider than the realised replacement reduction on the median engagement. That is a sample specific result, not a generalisable conclusion. The buyer that chooses to migrate on the Desk's sample reliably has a workload profile that supports the migration economically even at the narrower realised value.

2026 vSAN to native HCI scenarios reviewed13

Scenarios progressed to signed replacement contract6

Median headline TCO reduction in original proposal34 percent

Median realised TCO reduction over five year horizon8 percent

Storage policy refactor overrun against plan34 to 52 percent

Dual run period, median11 months

Sensitivity to storage policy mix

The exit economics on any specific buyer's portfolio are most sensitive to the storage policy mix. Buyers with a small number of standardised policies applied broadly across the workload population see migration economics close to the headline. Buyers with a large number of bespoke policies applied narrowly across the workload population see economics that often do not justify the migration. The Desk's 2026 sample shows that buyers with fewer than 12 distinct storage policies across the estate produced TCO reductions of 14 to 22 percent on the migration. Buyers with more than 40 distinct policies produced TCO reductions of negative 4 to 7 percent on the migration, meaning that several actually lost money against the realistically cleared vSAN renewal across the five year horizon.

The policy count is the single most actionable input to the exit decision. The buyer that does not produce a current policy inventory before evaluating an exit proposal is evaluating against unknown migration economics.

The hyperscaler native HCI alternative

A growing share of the Desk's 2026 vSAN exit conversations consider a hyperscaler native HCI offering as the replacement target rather than a traditional HCI vendor. The hyperscaler native option carries a different economic profile from the traditional vendor option. The headline run cost is reliably higher on the hyperscaler native option, often materially higher, but the migration cost is reliably lower because the storage policy refactor can lean on the hyperscaler native policy abstraction rather than on a vendor specific replacement abstraction.

The Desk's 2026 sample includes 4 hyperscaler native scenarios out of the 13 total. The realised TCO across five years on those 4 scenarios was on average 11 percent above the realistically cleared vSAN renewal, computed against the steady state hyperscaler run cost. The hyperscaler native option did not produce a TCO reduction on any of the 4 scenarios but did produce a meaningful reduction in the storage management operational cost across the term. The buyer's choice between the traditional and hyperscaler native options is rarely a pure TCO decision. The hyperscaler native option is selected on operational and architectural grounds when it is selected, with the TCO trade off accepted as a deliberate cost.

The relevance to the exit conversation is that the buyer's evaluation has to model both options independently. The hyperscaler native run cost cannot be modelled by adjusting the traditional vendor model. The two run cost profiles differ in their underlying drivers and have to be built from the ground up against the buyer's specific consumption pattern.

What we have seen on live deals

A Fortune 200 retail buyer brought a vSAN to alternative HCI business case to the Desk in late 2025 with a headline TCO reduction of 41 percent across five years. The buyer had 67 distinct storage policies across the estate, of which 38 were applied to a single workload class each. The Desk rebuilt the model with a realistic storage policy refactor cost and against the realistically cleared vSAN renewal. The rebuilt model showed a TCO reduction of negative 2 percent across five years. The buyer chose to renegotiate the vSAN renewal rather than migrate and used the rebuilt model as the basis for a portfolio consolidation effort that ran in parallel. The cleared vSAN renewal produced a 31 percent reduction against the opening quote and the parallel consolidation reduced the policy count from 67 to 22 ahead of the next renewal cycle.

The takeaway

The realistic exit value is the difference between the cleared vSAN renewal across the term and the steady state replacement run cost across the same term, net of the actualised migration cost. The headline reduction in a vendor proposal is a starting point for analysis, not an answer.
The single largest source of business case slippage on the Desk's 2026 sample is the storage policy refactor, which reliably exceeds the planning estimate by 34 to 52 percent. The dual run period for a storage exit is longer than for a compute exit and is concentrated on regulated workloads.
The buyer's storage policy mix is the single most actionable input to the exit decision. The buyer with fewer than 12 distinct policies sees economics that often support the migration. The buyer with more than 40 distinct policies sees economics that often do not. A current policy inventory has to precede any exit decision.