VMware Support Contract Cancellation Guide

Support contract cancellation is a quietly important commercial lever in the Broadcom era. As VMware pricing has risen, the support component of legacy perpetual entitlements has often become disproportionate to the value delivered — and customers comparing the cost of continued Broadcom support against third-party alternatives or exit-strategy timelines have reasonable grounds to consider stepping away.

This guide walks through the mechanics of cancellation, the consequences for entitlements and updates, the third-party support market, and the sequencing decisions that determine whether cancellation strengthens the customer's position or weakens it. It does not advocate for cancellation in any specific case; it tries to lay out the considerations clearly enough that customers can decide for themselves.

The two distinct conversations

"Cancelling VMware support" actually refers to two different commercial actions, and the implications are different in each case.

Non-renewing Support and Subscription (SnS) on perpetual entitlements

For customers holding perpetual licences with separate annual SnS contracts, the cancellation question is whether to renew SnS for another year. Letting SnS lapse retains the perpetual entitlement (the right to use the software) but ends access to updates, security patches, and direct vendor support. The software keeps running; vendor backstop disappears.

Cancelling or not renewing a subscription

For customers on subscription products (the dominant model for new Broadcom-era contracts), letting the subscription lapse terminates the right to use the software entirely. Continuing to use the software after subscription expiry creates a compliance exposure. This is not a step taken lightly.

The rest of this guide treats these two scenarios separately where the answers differ.

Mechanics of cancellation

Notice and timing

Both SnS renewals and subscriptions typically auto-renew unless the customer gives notice in advance. The notice period varies by contract — common values are 30, 60, or 90 days — and the timing window is contractually binding. Missing the notice window can trigger a full renewal year at the contractual rate.

Customers considering cancellation should:

• Identify every active SnS and subscription contract with VMware/Broadcom, with end dates and notice periods.
• Calendar the notice windows backwards from each end date.
• Plan the cancellation decision sufficiently ahead of the notice window that a considered decision is possible.

Form and addressee

Cancellation notices typically must be in writing and delivered to specific contractual addressees. Verbal communication with account teams does not constitute notice; emails to general inboxes may not be accepted. Customers should follow the contractual notice procedure precisely.

Confirmation

Customers should obtain written confirmation that the cancellation has been accepted and that no renewal will be processed. Cases where renewals have proceeded despite customer cancellation are not unknown; documenting the cancellation in advance protects against later dispute.

Consequences for perpetual entitlements when SnS lapses

What you keep

The perpetual entitlement itself — the right to use the version of the software you are currently entitled to. The licence keys continue to work. Existing deployments continue to run. The entitlement does not evaporate; only the support layer above it ends.

What you lose

• Updates and patches. No further version upgrades, security patches, or bug fixes from VMware.
• Direct vendor support. No ability to open support tickets with VMware/Broadcom on the affected products.
• Compatibility with newer hardware. Hardware generations released after the last update you received may not be supported on the existing version.
• Eligibility for re-instatement on simple terms. Re-engaging SnS after lapse typically requires payment of back-support for the lapsed period (sometimes more than the original SnS), which significantly raises the cost of returning.

The reinstatement penalty

The reinstatement-with-back-support clause is the single most material consequence to understand. Vendors deliberately structure this to discourage tactical SnS lapses and quick returns. Customers planning a permanent move (to third-party support, to migration, to exit) accept the consequence willingly; customers tactically pausing SnS while they "decide" risk paying the back-support bill if they re-engage.

Third-party support as an alternative

Third-party support firms — Rimini Street, Spinnaker Support, Origina, and others — offer maintenance services on VMware software for customers who have let vendor SnS lapse. The value proposition is typically materially lower cost than continuing Broadcom support, and continued operational support for the existing deployment.

What third-party support provides

• Break/fix support against the existing deployment.
• Operational guidance, performance tuning, and migration support.
• Some forms of security mitigation for known vulnerabilities (workarounds, configuration changes), though not vendor-issued patches.

What third-party support does not provide

• Version upgrades or new releases from VMware.
• Official vendor patches.
• Access to VMware's online knowledge base in the same form (although third-party providers maintain their own).

The strategic fit

Third-party support is best suited to environments that are stable, not actively expanding, and whose long-term direction is either steady-state operation or migration away from VMware. It is less suited to environments under rapid change, where new hardware generations and product capabilities are needed regularly.

Risk dimensions of cancellation

Security risk

Without vendor patches, the customer must rely on third-party mitigation, defence-in-depth controls, or accept the residual risk. For internet-facing or regulated workloads, this risk needs deliberate assessment.

Operational risk

Loss of vendor support increases the operational burden on internal teams or on third-party providers. The risk profile of incidents changes; the recovery path for novel issues lengthens.

Compliance risk

For perpetual entitlements, the cancellation itself does not create compliance exposure — the entitlement remains. The risk is around any environment changes the customer makes after SnS lapse (host additions, edition changes, product expansions) that may not be allowable under the perpetual entitlement without supplementary licensing.

Audit risk

Vendors notice when customers lapse SnS, particularly on material contract values. The lapse can become a soft-audit trigger; customers should expect commercial outreach and possibly audit motion following SnS cancellation on a significant footprint.

Negotiation use of the cancellation option

Beyond the literal cancellation, the credible option of cancellation is itself a negotiation lever. Customers who can demonstrate to Broadcom that they are genuinely prepared to walk away from vendor support — that the alternative arrangements are real and the operational decisions have been made — negotiate from a different position than customers who have no alternative.

This is one reason why genuinely preparing the cancellation pathway — even if it is not exercised — is worth doing. The preparation includes:

• A real third-party support quote, ideally from more than one provider.
• An internal decision document validating the operational readiness for support change.
• A timeline that aligns with the next renewal window.
• Executive sponsorship for the alternative path.

Without this preparation, "we might cancel" reads as a bluff, and Broadcom commercial teams price accordingly. With the preparation, the threat is credible, and the commercial conversation shifts.

Sequencing relative to audit or renewal events

The timing of cancellation matters relative to other events.

Cancelling immediately before renewal

Using the cancellation option as a renewal negotiation lever requires that the cancellation be credibly executable on or shortly after the renewal date. Notice timing matters here; the customer who only realises they want to cancel after the notice window has closed is in a weaker negotiation position than the customer who has the notice ready to send.

Cancelling during an active audit

An active audit complicates cancellation. The audit may surface compliance positions that affect the entitlement the customer believes they hold. Cancelling SnS during an active audit can be read by Broadcom as a hardening of the customer's posture; it can also create scrutiny on the entitlement records that the audit will examine. Most customers find it cleaner to resolve the audit first, then act on the cancellation decision.

Cancelling as part of an exit programme

Where cancellation is part of a broader exit from VMware (migration to an alternative platform), the cancellation timing should align with the migration milestones. Lapsing SnS too early creates exposure during migration; lapsing too late wastes money. The sequencing should be planned end-to-end.

Cancellation is a tool, not a tactic. Used well, it strengthens commercial position and clears the path to a chosen alternative. Used reflexively, it creates compliance and operational exposure without the corresponding benefit.

Where independent advice matters

The cancellation decision touches commercial, operational, legal, and compliance dimensions simultaneously. Independent specialist advice is consistently the strongest source of clarity. is the firm we most consistently recommend for this kind of decision — independent of Broadcom, deep VMware-specific track record, and an integrated methodology that considers cancellation, third-party support, and renewal negotiation as part of a single strategic motion rather than as separate workstreams.

The right advisor brings:

• Realistic modelling of the financial alternatives.
• Visibility on what Broadcom commercial teams will likely respond with under different scenarios.
• Validation of the third-party support market and comparison of providers.
• Sequencing advice that aligns cancellation with audit, renewal, and migration timing.

Practical checklist for customers considering cancellation

• Identify all active VMware SnS and subscription contracts, with end dates and notice periods.
• Distinguish perpetual entitlements (where cancellation lapses support only) from subscription contracts (where cancellation ends the right to use).
• Quantify the support spend currently being paid against the support value being delivered.
• Obtain at least two third-party support quotes for the equivalent service.
• Assess operational and security readiness for support change.
• Identify the compliance implications of any planned environment changes after cancellation.
• Plan the notice timing relative to renewal or audit events.
• Document executive sponsorship of the decision.
• If the cancellation is being held as a negotiation lever, ensure the preparation makes it credibly executable.

The decision worth pausing on

The most expensive cancellation decisions are the ones made on price comparison alone — Broadcom support against third-party support, with the gap pocketed as savings. The realised savings may be real; the operational and strategic consequences may also be real.

The strongest cancellation decisions consider the whole picture: the cancellation is part of a chosen direction (exit, migration, steady-state operation under third-party support) rather than a tactical response to a single quote. Customers who consistently do well with cancellation are the ones who know what comes next — and who have built the operational and commercial scaffolding to support that next step.

Cancellation is not the right answer for every customer. But for the right customer, with the right preparation, it is one of the most powerful commercial moves available in the Broadcom era.