VMware SnS Renewal vs VCF Subscription

Two years into the Broadcom era, most VMware customers are now reaching their first or second post-acquisition renewal. The choice presented by Broadcom is rarely subtle: continue paying Support and Subscription (SnS) at significantly increased pricing on existing perpetual licences, or convert to VMware Cloud Foundation (VCF) subscription with broader entitlement and a multi-year commitment. The economics of the decision look different depending on the customer's deployment profile, future plans, and risk tolerance. This article works through the decision framework that produces defensible answers.

What's actually being compared

The two paths are not directly equivalent, so the comparison requires careful framing.

The SnS renewal path: the customer continues to hold its existing perpetual licences (or rolls forward existing subscription licences for the same components), and pays annual SnS at Broadcom's renewed pricing. SnS provides software updates and support; the underlying entitlement remains as previously contracted.

The VCF conversion path: the customer trades existing entitlements (perpetual or subscription) for a VCF subscription at a defined per-core or per-VM price. The VCF subscription bundles vSphere, vSAN, NSX, and the Aria operations stack at defined editions and scope. The previous entitlements are typically extinguished as part of the conversion.

The headline price comparison — SnS renewal cost versus VCF subscription cost — is only one dimension. The full comparison includes scope, future flexibility, exit cost, and operational implications.

The SnS renewal economics

SnS pricing under Broadcom has typically increased 30-100% versus pre-acquisition rates, with the largest increases on:

• vSphere Enterprise Plus — Broadcom has steered customers off this edition; SnS pricing reflects the steering pressure
• NSX standalone (any edition) — particularly steep increases as Broadcom prefers NSX consumed within VCF
• vSAN standalone — similar pattern to NSX
• vRealize/Aria Suite — significant increases coordinated with the VCF bundling push

Smaller increases — sometimes flat or modest — have applied to:

• vSphere Standard and Foundation editions — Broadcom's volume play for smaller customers; pricing held more stable
• Specific niche products — Workspace ONE, Carbon Black, some legacy Symantec components

For most enterprise customers, the SnS renewal price is meaningfully higher than the pre-acquisition baseline. The question is whether that price is still better than the VCF conversion alternative.

The VCF subscription economics

VCF subscription is priced per core, typically with minimum-core commitments per host. The bundled scope (vSphere + vSAN + NSX + Aria) is intentionally broader than what most customers had previously licensed, which produces two effects:

Effect 1: Customers who previously held only vSphere find themselves paying for unused vSAN, NSX, and Aria capacity in the VCF subscription. The per-core price is higher than vSphere-only would have been, but lower than the sum of separately licensing all four components.

Effect 2: Customers who previously held vSphere plus some combination of vSAN/NSX/Aria find the VCF subscription is roughly comparable to or sometimes cheaper than separately renewing each component. The bundling helps customers who use multiple components.

For per-core economics, typical VCF pricing in late 2025/early 2026 ran in the $300-$500 per-core per-year range for mainstream enterprise contracts, with discounts for volume and term length. Specific pricing varies by negotiated discount, term, and bundle.

The scope comparison

A direct price comparison misses the scope difference between the two paths. The customer needs to compare apples to apples:

SnS-renewal scope: exactly what the customer previously licensed, at the same editions, with the same scope. No change in entitlement.

VCF-conversion scope: the VCF-bundled entitlement (vSphere + vSAN + NSX + Aria at defined editions). Components the customer previously had separately are now part of the bundle. Components the customer didn't previously have are now available within the bundle.

If the customer was previously running only vSphere, the VCF conversion adds vSAN, NSX, and Aria entitlement. The customer pays more per core but gains entitlement to deploy these components going forward. If the customer was previously running vSphere + vSAN + NSX Enterprise Plus + Aria Suite, the VCF conversion may be roughly cost-neutral or cheaper, with broadly equivalent scope.

The term-commitment dimension

SnS renewals are typically one to three years. VCF subscriptions are commonly three to five years, sometimes longer. The longer commitment carries implications:

Risk: the customer is locked in for the term. If pricing improves elsewhere (alternative vendors, alternative architectures), the customer cannot capture the improvement until the term expires.

Predictability: the customer has price certainty for the term. Annual budget planning is simpler.

Exit: exiting before the term expires usually requires either negotiated unwind (rare) or the customer continuing to pay through the term while migrating off. The exit cost can be material.

Customers with high confidence in their VMware commitment over the next five years should weight predictability higher; customers exploring alternatives should weight flexibility higher.

The flexibility dimension

VCF as a bundle is constraining as well as enabling. The constraints:

• Bundled scope — the customer is paying for the full VCF stack whether or not they use all components; partial deployments don't unbundle the price
• Edition gating — VCF includes specific editions; using above-edition features requires uplift or add-ons
• Architectural alignment — VCF's value proposition assumes a vSphere-managed compute estate with vSAN storage and NSX networking; customers with different architectures (third-party storage, different networking stack) may not capture the bundle value
• Term commitment — the longer commitment limits flexibility

SnS renewal preserves the customer's existing architectural choices and avoids the bundling. It's less efficient per dollar for customers who genuinely use the full VCF stack but more flexible for customers who don't.

The decision matrix

The choice between SnS renewal and VCF conversion typically resolves to one of four quadrants:

Quadrant 1: Limited VMware footprint, expecting to migrate away. SnS renewal is usually right. Avoid the multi-year VCF commitment; keep flexibility for migration.

Quadrant 2: Limited VMware footprint, committed to continued use. SnS renewal may still be right if the customer doesn't need vSAN/NSX/Aria. VCF if the bundled components have planned use cases.

Quadrant 3: Significant VMware footprint, using multiple components. VCF conversion is usually economically attractive at the bundled price. The trade is flexibility for unit economics.

Quadrant 4: Significant VMware footprint, planning major migration. Probably SnS renewal in the short term to preserve flexibility, with VCF conversion considered after migration plans are clearer. The risk of committing to VCF when about to migrate is the exit cost.

Hybrid approaches

Some customers can structure hybrid arrangements:

Partial VCF, partial SnS. Convert a portion of the estate to VCF (typically the stable, multi-component portion) while keeping SnS on the portion expected to migrate or change. Negotiating this requires Broadcom's agreement; not always available.

VCF with reduced scope commitment. Convert to VCF but with a smaller per-core commitment than current deployment, planning to reduce deployment over the term. This trades higher per-core price for lower total commitment; only available with negotiated structure.

Phased migration to VCF. Convert incrementally over the renewal cycle rather than all at once. Useful when the customer's architecture is in transition.

Hybrid approaches require active negotiation; Broadcom's default offer is a clean conversion of the customer's entitlement into VCF subscription at scale.

The exit-cost calculation

Both paths have exit costs, but they differ in character:

SnS exit cost: the customer loses access to updates and support but retains the right to use the perpetual licence under the existing contract. The licence continues to function without updates. Many customers can operate on stale versions for an extended period.

VCF exit cost: the subscription ends at the end of the contracted term (or earlier if negotiated). After the term, the customer no longer has the right to use the VCF-bundled software. Continued use requires either renewal, conversion to a different entitlement, or migration off VMware. Mid-term exit usually requires paying through the remaining term.

For customers seriously considering migration, the SnS path preserves more options. For customers committed to long-term VMware use, the VCF path is fine because exit considerations are not driving the decision.

Negotiation levers in either path

Both paths admit negotiation, though Broadcom's account team incentives push toward VCF:

For SnS renewal: multi-year commitment in exchange for pricing concessions, expanded scope in exchange for renewal, partial conversion to subscription metrics in exchange for SnS rate hold.

For VCF conversion: term length, volume discount, edition specifications, included add-ons, exit terms, conversion credits for unused legacy entitlement, pricing protection at renewal.

The negotiation works best when the customer has prepared its own analysis of value, has credible alternatives in view, and is willing to walk if terms are unacceptable. Customers who arrive without analysis or alternatives typically accept Broadcom's first offer.

Common decision mistakes

Treating headline price as the comparison

Scope, term, flexibility, and exit all matter. A "cheaper" VCF subscription may be more expensive in total cost than SnS renewal once flexibility is valued.

Assuming the bundled components will be used

If the customer's architecture doesn't fit vSAN-on-vSphere with NSX networking, the VCF bundle's per-core price is paying for capability that won't be deployed.

Underestimating the term commitment

Five years is a long time in enterprise IT. Migration plans, vendor relationships, and architecture preferences can all shift; the term commitment limits the customer's ability to respond.

Failing to model the alternatives

The decision isn't only SnS-versus-VCF. Migration to alternatives (Proxmox, Nutanix, public cloud) is a third path. The right answer might involve all three across different parts of the estate.

Going in without independent analysis

Broadcom's account teams are professionally skilled at framing the value of VCF conversion. Customers without their own framing tend to anchor on Broadcom's framing.

Frequently asked questions

Can we renew SnS indefinitely on perpetual licences?

In principle, yes — perpetual licences remain in force and SnS can typically be renewed annually. In practice, Broadcom's pricing pressure on SnS encourages conversion. Long-term SnS renewal is contractually possible but increasingly economically unattractive.

What happens to our perpetual entitlement if we convert to VCF?

Typically extinguished as part of the conversion; the customer surrenders the perpetual entitlement in exchange for the VCF subscription. Preserve a copy of the entitlement records for audit-defence purposes even after conversion.

Is VCF subscription cheaper than separately licensing the components?

Usually yes for customers using multiple components; usually no for customers using only vSphere. The economics depend on which components the customer actually uses.

Can we negotiate the VCF subscription scope?

Yes, within limits. Term length, volume, discount level, included add-ons, and exit terms are negotiable. The bundle composition itself is largely fixed by SKU.

What if we want to convert later, not now?

SnS renewal preserves the option to convert later. Many customers renew SnS once or twice before converting to VCF, particularly while evaluating alternatives.

How does the SnS-versus-VCF decision interact with audit risk?

Audit risk is somewhat higher during periods of pricing dispute or apparent customer migration intent. Either path can be defended; the customer's compliance position matters more than the path chosen.