VMware end of availability dates.

Broadcom's end-of-availability (EOA) and end-of-support-life (EOSL) dates for the VMware portfolio are the operational backbone of the subscription-conversion programme. Every published EOA date is also a renewal lever — the date at which the alternative to converting becomes operationally untenable. This piece consolidates the EOA picture customers should plan against in 2026, the lifecycle conventions Broadcom is applying, and the operational and commercial posture that produces the best outcomes when an EOA date approaches.

Specific dates change. Treat the dates referenced here as the pattern; verify the exact current position for every SKU in your estate against the published Broadcom lifecycle matrix and against your support contract before making operational decisions.

The EOA framework Broadcom inherited and changed

Pre-acquisition VMware lifecycle conventions

Pre-acquisition VMware operated a lifecycle programme that gave customers reasonable runway between General Availability, EOA, end-of-general-support, and end-of-technical-guidance. The runway between phases was typically measured in years, and the customer-facing communications were predictable enough that lifecycle planning could be done with confidence.

What changed post-acquisition

Post-acquisition, the EOA cadence accelerated and the customer-facing communications became less predictable. EOA dates were brought forward for several editions, end-of-support runway compressed for legacy perpetual entitlements, and the documentation of lifecycle status became less stable as SKUs were retired, absorbed, and relabelled through the packaging rationalisation programme.

The cumulative effect for customers is that the lifecycle position of any given SKU in 2026 needs to be verified rather than assumed. The published matrix is authoritative; account-team verbal positions are not.

vSphere EOA picture for 2026

vSphere 7 and earlier

vSphere 7 and earlier editions are well into the lifecycle wind-down. Customers operating these editions in production should have a defined path forward — either a subscription conversion to current packaging or a deliberate migration to an alternative platform. Operating an unsupported edition in production is not strategically tenable for most organisations because the security-update flow is the lever Broadcom uses to drive conversion conversations.

vSphere 8 and the subscription transition

vSphere 8 is the centre of the current subscription transition. Perpetual entitlements to vSphere 8 carry support runway, but the runway is shorter than customers typically expect, and the conversion conversation will begin meaningfully before the formal EOSL date. Customers with perpetual vSphere 8 entitlements should treat the conversion conversation as a 2026-relevant question rather than a 2027 or 2028 question.

VCF and vSphere subscription packaging

Subscription lifecycle conventions

Under subscription packaging, the lifecycle conventions are different from the perpetual world. Subscription customers are continuously moved forward through current versions, and the EOA conversation is less about whether the customer can keep operating and more about whether the customer is on the current pricing and packaging structure. The lifecycle question becomes a commercial question.

Edition retirement under VCF rationalisation

Several VCF editions have been retired or absorbed through the rationalisation programme. Customers on a retired edition are migrated forward at renewal, typically to a higher tier with a broader bundle and a higher per-core list price. The retirement is a commercial event masked as a lifecycle event.

NSX, vSAN, and Aria lifecycle

NSX standalone

Standalone NSX entitlements are subject to lifecycle compression as Broadcom moves NSX capabilities into bundled VCF tiers. Standalone NSX customers should expect their renewal conversation to include pressure to migrate to a VCF tier that includes NSX as part of the bundle. The commercial impact of that pressure depends on the customer's broader entitlement picture.

vSAN standalone

Standalone vSAN faces the same pattern. The standalone packaging exists, but the pricing and packaging structures push customers toward VCF tiers where vSAN is bundled with other capabilities. Customers with mature vSAN deployments who do not use the broader VCF capability set face a particularly acute version of this pressure.

Aria Operations and Aria Automation

Aria has gone through several packaging iterations post-acquisition. Current customers should verify the lifecycle position of their specific Aria entitlements against the published matrix because relabelling and bundle absorption have left a material number of customers uncertain about exactly what they own and how long they own it for.

Symantec, CA, and Carbon Black lifecycle posture

Symantec endpoint and DLP

Symantec endpoint protection and DLP product lifecycle has compressed under Broadcom ownership. Several legacy editions have moved through accelerated EOA cadences, and the bundled DLP-plus-endpoint constructs are increasingly the only forward-supported path. Customers operating legacy Symantec editions should refresh their lifecycle position before renewal conversations begin.

CA Technologies products

CA Automic, Clarity, and Rally have all gone through lifecycle and packaging changes that customers should validate against the current published position. The commercial pattern is similar to the VMware side: subscription conversion is the strategic direction, and lifecycle conventions favour the conversion.

Carbon Black

Carbon Black workload protection has moved through bundling iterations that affect both standalone and integrated lifecycle positions. Customers should verify the specific lifecycle status of their entitlements rather than relying on legacy assumptions from pre-acquisition Carbon Black documentation.

How to operate against the current EOA environment

Maintain a current SKU-by-SKU lifecycle map

The single most useful operational artefact for a Broadcom-portfolio customer is a current SKU-by-SKU lifecycle map that lists every entitlement, its current lifecycle position, its support runway, and its renewal cadence. The map should be refreshed quarterly because Broadcom's lifecycle communications change faster than the typical customer assumes.

Decouple lifecycle decisions from commercial pressure

Every approaching EOA date will be used by the account team as a commercial lever — to push subscription conversion, to push tier upgrades, to push bundle adoption. The customer's posture should be to evaluate the lifecycle decision on its operational merits separately from the commercial conversation. The two will be presented as one; they should be analysed as two.

Anticipate the conversion-or-walk decision

For every entitlement approaching EOA, the customer faces a strategic question: convert to current packaging, or migrate to an alternative platform. Both paths are legitimate. The wrong outcome is to default into the conversion path because the EOA conversation arrives without preparation. The conversion-or-walk decision should be made deliberately, with current benchmark data, alternative-platform cost analysis, and a defined target operating model.

The renewal-and-lifecycle pattern to watch

The bundled conversion proposal

The commercial framing that arrives most often near an EOA date is a "bundled conversion" proposal — convert legacy perpetual entitlements to current subscription packaging, with a one-time discount that makes the conversion economics look attractive in the proposal year and considerably less attractive in years two through five. Customers should model the proposal across the full term, not just the discount year, because the steady-state economics are typically what matter.

The tier-upgrade-on-EOA pattern

Where the customer's current SKU is being retired, the conversion proposal often combines lifecycle migration with a tier upgrade — the retired SKU's capabilities are absorbed into a higher tier that the customer is then proposed for. The tier upgrade should be evaluated on its own merits rather than accepted as a default consequence of the lifecycle migration.

Operational guardrails

Treat published dates as the authority

Account-team verbal positions on lifecycle dates are routinely more favourable to the commercial conversation than the published matrix. Operate against the published dates and use the account-team conversation as supplementary context, not as a substitute for the published authority.

Refresh the map before every renewal

A renewal conversation that arrives without a current lifecycle map produces inconsistent customer-side positioning and weaker negotiation outcomes. Refresh the map two quarters before every renewal as a standard operating practice.

Document the strategic intent

For every entitlement approaching EOA, document the strategic intent — convert, migrate, or rationalise. The documentation drives consistency across the customer-side conversation and removes the ambiguity that account teams routinely exploit when the customer's position is not pre-committed.

Closing

End-of-availability dates are a commercial instrument as much as a lifecycle convention in the current Broadcom operating model. Customers who plan against the published matrix — with current data, deliberate conversion-or-walk decisions, and disciplined separation of lifecycle and commercial conversations — land materially better outcomes than customers who default into the conversion proposal that arrives with the EOA notification. The cost of lifecycle preparation is small; the cost of an unprepared EOA conversation, particularly when it lands in the same quarter as a renewal proposal, is consistently a multiple of that preparation cost.

Lifecycle scenarios by product family

Customers running vSphere 7 or earlier in production

Customers running vSphere 7 or earlier in production face a near-term lifecycle decision: convert to current packaging, migrate to an alternative platform, or accept the steady-state risk of operating an unsupported edition. None of these options is automatically the right answer. The decision should be driven by the customer's broader platform strategy, the operational risk tolerance, and the commercial economics of each path. Default into conversion is the easiest path and frequently the wrong one for organisations with viable alternative platforms.

Customers on perpetual vSphere 8 entitlements

Perpetual vSphere 8 entitlements carry support runway, but the runway is shorter than typical customer expectation and the conversion conversation will arrive meaningfully before the formal end-of-support date. Customers in this position should plan the conversion-or-migrate decision proactively rather than reactively. The cost of a reactive decision is consistently higher than the cost of a proactive one.

Customers on standalone NSX or vSAN

Standalone NSX and vSAN customers face lifecycle compression pressure as Broadcom moves these capabilities into bundled VCF tiers. The standalone packaging persists in 2026 but the commercial structure increasingly favours migration to the bundled tier. Customers should evaluate the bundled tier on its operational merits as well as its commercial economics — accepting a bundle that includes capabilities the customer does not use is a worse outcome than declining the bundle and accepting tighter standalone pricing.

Customers on Aria with packaging confusion

Customers operating any of the Aria product family should explicitly verify the current lifecycle position of their specific entitlements. Aria has gone through multiple packaging iterations post-acquisition, and several customers we work with discovered through this verification that their actual lifecycle position differs from what they assumed. Verification is a low-cost step with high information value.

The 24-month lifecycle planning calendar

Quarter minus eight

Eight quarters out from a major renewal, the lifecycle-and-entitlement map should be current and the strategic direction for each product family — convert, migrate, or rationalise — should be documented. This is the strategic-clarity window.

Quarter minus four

Four quarters out, the alternative-platform analysis should be complete for any product family where migration is a live option, and the benchmark data for the negotiation should be current. This is the analytical-readiness window.

Quarter minus two

Two quarters out, the defence-partner and licensing-advisor engagement should be active, the contractual position should be reviewed, and the negotiation strategy should be documented. This is the engagement-readiness window.

Quarter zero

At the renewal quarter, the customer's posture should be settled and the negotiation should run against a prepared position rather than emerge in response to the account-team proposal. Customers who arrive at the renewal quarter without the prior preparation produce materially weaker outcomes than customers who arrive prepared.

Symantec and CA lifecycle planning

The lifecycle planning framework for Symantec and CA Technologies products is structurally similar to the VMware framework, with two differences. First, the legacy product depth in Symantec and CA estates is often greater than in VMware estates, which lengthens the verification and decision cycle. Second, the alternative-platform landscape for Symantec and CA products is more variable than for VMware, with stronger alternatives in some categories and weaker alternatives in others. Customers should evaluate the conversion-or-migrate decision on a per-product basis rather than as a portfolio decision.

What to avoid

Accepting account-team verbal lifecycle positions

Account-team verbal positions on lifecycle status are routinely more favourable to the commercial conversation than the published authoritative position. Operate against the published matrix and use the account-team conversation as supplementary context, never as a substitute.

Defaulting into the conversion path

The conversion path is the path of least operational resistance. It is also the path most commercially favourable to Broadcom. The fact that it is the easiest path is not a reason to take it; the strategic merits should be evaluated on their own.

Treating EOA as a purely technical question

EOA is a commercial instrument in the current operating model. Treating it as a purely technical question understates the negotiation dynamics that surround every approaching EOA date. The defensive posture is to recognise EOA as both technical and commercial and to plan accordingly.

Closing thoughts on lifecycle as commercial lever

The customers who fare best through 2026 in the lifecycle conversation are those who maintain a current published-authority lifecycle map, plan their conversion-or-migrate decisions deliberately across a 24-month horizon, engage defence support proactively, and refuse to let EOA pressure produce commercial decisions that the operational situation would not otherwise justify. The cost of this discipline is small; the cost of its absence, particularly when EOA pressure lands in the same quarter as a renewal proposal, is consistently a multiple of that discipline cost.