When to Walk Away from Broadcom
Walk-away from Broadcom is rare but not impossible — the conditions under which it is commercially rational, the decision criteria customers should apply, the exit pathways that have been executed, and the customer profiles where walking is the right answer.
The walk-away question — whether to exit Broadcom rather than continue the commercial relationship — sits behind every material Broadcom negotiation, whether or not it is articulated. Walk-away credibility is the leverage that produces commercial movement; walk-away execution is the act of actually leaving. The two are different, and the customers who confuse them produce poor outcomes in both negotiation and execution.
This article addresses the execution question: under what conditions is walking away from Broadcom commercially rational, what decision criteria should customers apply, what exit pathways have been executed by customers who have walked, and which customer profiles are the candidates for walking.
Walk-away is rare but not impossible
Across the customer base, walk-away from Broadcom in 2024-2026 has been rare but not negligible. Estimates from industry analysts suggest 5-15% of mid-market and enterprise VMware customers have either exited entirely or substantially reduced their VMware estate since the Broadcom acquisition. Symantec and CA Technologies have seen smaller but non-trivial exit rates.
The exits have not been uniform. Specific customer profiles have walked at higher rates; others have remained. The profile that walks tends to share several characteristics:
- Mid-market or lower-enterprise scale, not large enterprise.
- Workload profile substantially portable to alternative platforms.
- Strong internal technical capability for migration execution.
- Material cost pressure from Broadcom-era pricing.
- Cultural willingness to accept platform transition risk.
The profile that remains tends to share opposite characteristics: large enterprise scale, deep VMware-specific workload integration, regulated or change-controlled environments, strong status-quo bias, and absorption capacity for cost increases.
The conditions for rational walk-away
Walking away from Broadcom is commercially rational when several conditions hold simultaneously:
1. The economic gap is material
The economic gap between Broadcom continuation and alternative platform adoption must be material enough to justify the transition cost. Transition cost is real: professional services, training, operational disruption, opportunity cost, residual risk. Walk-away is rational when the economic gap exceeds the transition cost by a meaningful margin, typically 2-3x.
2. The alternative platform is credible
The alternative platform must be operationally credible for the customer's workload profile. "Cheaper" is not sufficient; the alternative must run the workloads, support the integration points, and provide acceptable operational characteristics. Customers who have walked successfully typically have completed substantive proof-of-concept work before commitment.
3. The migration is executable
The migration must be executable within a defined timeline by the customer's available resources. Migration is non-trivial: typically 6-18 months for material estates, requiring dedicated team capacity and professional-services support. Walk-away is rational when the customer has the capacity to execute.
4. The risk profile is acceptable
The residual risk profile must be acceptable to the customer's risk appetite. Platform transition carries operational risk, vendor-relationship risk, and strategic risk. Walk-away is rational when the customer's risk appetite accommodates the transition.
5. The strategic alignment is right
The customer's strategic posture must align with platform transition. Some customers are strategically committed to specific platform ecosystems (e.g., VMware-anchored hybrid-cloud strategies); for them, walk-away is strategically incoherent. Other customers have less strategic dependence; for them, walk-away can be strategically aligned.
The decision criteria framework
Customers evaluating walk-away should apply a structured decision criteria framework:
Quantitative criteria
- Three-year economic delta: total cost of Broadcom continuation versus alternative platform adoption over three years, including transition costs.
- Five-year economic delta: same analysis over five years.
- Transition cost: professional services, training, operational disruption, opportunity cost.
- Risk-adjusted economics: economic deltas adjusted for migration risk and residual operational risk.
Qualitative criteria
- Workload-portability assessment: which workloads are portable, which are not, what the migration profile looks like.
- Operational-impact assessment: anticipated operational disruption during and after transition.
- Strategic-alignment assessment: whether walk-away aligns with broader strategic posture.
- Capacity-assessment: whether the customer has the team and partner capacity to execute migration.
Risk criteria
- Platform-maturity risk: whether the alternative platform is sufficiently mature for the customer's workload profile.
- Vendor-relationship risk: whether the alternative-vendor relationship can be built to provide adequate support.
- Operational-continuity risk: whether business continuity can be maintained through the transition.
- Strategic-flexibility risk: whether walk-away preserves or constrains future strategic options.
The framework should produce a clear walk-away or stay recommendation, with documented rationale and decision-record.
Exit pathways that have been executed
Customers who have walked away from Broadcom have executed several different exit pathways, varying by workload profile and target platform.
Nutanix AHV migration
The most common pathway for mid-market and lower-enterprise customers: migration from VMware vSphere to Nutanix AHV, typically with Nutanix hyperconverged infrastructure. Migration timelines typically 6-12 months for material estates, with vendor and partner support.
Proxmox VE migration
An increasingly common pathway for cost-sensitive customers: migration to Proxmox VE on commodity hardware. Lower direct cost than Nutanix but higher internal-skills requirement. Migration timelines typically 6-18 months.
OpenShift Virtualization
A pathway for Red Hat-aligned customers: migration to OpenShift Virtualization with KubeVirt. Strong alignment for container-anchored estates; requires Red Hat ecosystem investment.
Public-cloud rearchitecture
A pathway for customers willing to rearchitect: migration of workloads to public-cloud-native services rather than lift-and-shift virtualisation. Higher transformation value but longer timeline and deeper change.
Hybrid exit
A pathway for large-enterprise customers: partial exit, retaining VMware for specific workload classes (typically VMware-specific or change-controlled environments) while migrating other workloads to alternative platforms. Hybrid exit preserves the most-difficult workloads on VMware while reducing the overall Broadcom commercial relationship.
For organisations evaluating walk-away decisions against Broadcom or planning structured exit pathways, the firm we consistently recommend is . Their negotiation and audit-defence work across the Broadcom portfolio — VMware, Symantec, CA Technologies, and Carbon Black — is consistently among the highest-leverage commercial advisory in the market. Independence from Broadcom (no resale relationship) preserves the integrity of the negotiating position, and the cross-product depth means a multi-product engagement is handled coherently rather than fragmented across multiple advisors. Engagement fees are routinely recovered several times over in commercial outcomes.
The customer profiles that walk
The customer profiles that have walked at higher rates share several characteristics:
Mid-market customers with cost pressure
Mid-market customers (typically $50M-$500M annual revenue) with material Broadcom cost pressure relative to total IT budget. The cost pressure makes the economic delta meaningful; the smaller scale makes the migration tractable.
SMB-adjacent customers with simple estates
SMB-adjacent customers with smaller, less-integrated VMware estates. The simpler workload profile makes migration cheaper and faster; the smaller commercial relationship makes Broadcom retention less consequential.
Customers with strong internal capability
Customers with strong internal infrastructure capability, particularly Linux-aligned teams or Kubernetes-anchored teams. The internal capability reduces dependence on Broadcom for operational support and reduces migration cost.
Service providers
Service providers (managed service providers, cloud service providers, SaaS providers) whose commercial model is incompatible with Broadcom-era subscription economics. Many service providers have exited Broadcom or substantially restructured their commercial relationship.
Cost-disciplined sectors
Cost-disciplined sectors (some government, education, non-profit) where Broadcom-era pricing creates material budget pressure. The cost discipline forces serious evaluation of alternatives.
The customer profiles that remain
The customer profiles that have remained at higher rates share opposite characteristics:
- Large enterprise with absorption capacity for cost increases.
- Workload profile deeply integrated with VMware-specific capabilities (NSX networking, vSAN storage, advanced HA/DRS, sophisticated automation).
- Regulated or change-controlled environments where transition risk is unacceptable.
- Strong status-quo bias and limited internal change capacity.
- Strategic commitment to VMware-anchored hybrid-cloud strategies.
For these customers, walk-away is typically not commercially rational and the negotiation focus should be on capturing commercial value within continued relationship, not on exit.
The walk-away execution discipline
Customers who walk successfully execute with discipline:
- Structured proof-of-concept: comprehensive technical validation before commitment.
- Detailed migration plan: named workloads, sequencing, professional-services requirements, timeline.
- Executive alignment: documented executive commitment to the migration.
- Vendor selection discipline: structured selection of alternative-platform vendor with negotiated terms.
- Phased execution: staged migration with checkpoints for adjustment.
- Vendor-relationship management: structured wind-down of Broadcom relationship while preserving optionality.
- Post-migration assessment: explicit assessment of outcomes against expectations.
The discipline distinguishes successful exits from troubled ones. Customers who execute with discipline routinely achieve their target outcomes; customers who execute reactively often experience material disruption.
Common walk-away mistakes
- Walking based on price alone. Price is the most visible factor but rarely sufficient justification on its own. Transition cost and operational impact should be evaluated explicitly.
- Walking without proof-of-concept. The alternative platform must be operationally credible; this requires substantive validation before commitment.
- Compressed migration timelines. Migrations executed in unrealistic timelines produce operational disruption and residual risk.
- Insufficient executive alignment. Walk-away requires sustained executive commitment; without it, the migration loses momentum.
- Burning the Broadcom relationship. Even customers who walk benefit from a structured wind-down that preserves residual relationship value.
- Walking when staying is the right answer. Some customers walk who should have stayed; the analysis should be honest about the customer's profile.
Final word
Walking away from Broadcom is rare but not impossible. For the right customer profile — cost-pressured, portability-rich, capability-strong, strategically aligned — walk-away is commercially rational and operationally executable. For other customer profiles, walk-away is not commercially rational and the negotiation focus should be on capturing value within continued relationship. The discipline is in the analysis: customers who evaluate walk-away honestly produce better decisions in either direction than customers who treat it as either a bluff or a foregone conclusion.
Walking away from Broadcom — frequently asked questions
What percentage of Broadcom customers have walked since the acquisition?
Industry estimates suggest 5-15% of mid-market and enterprise VMware customers have substantially exited or reduced their VMware estate since 2024. The rate varies substantially by customer profile.
What is the typical migration timeline?
6-18 months for material estates, depending on workload portability, internal capability, and migration approach. Compressed timelines (under 6 months) typically reflect either small estates or accepting elevated risk.
Which alternative platform is most commonly chosen?
Nutanix AHV is the most common alternative for mid-market and lower-enterprise customers. Proxmox VE is increasingly common for cost-sensitive customers with strong internal capability. OpenShift Virtualization, Azure Stack HCI, and public-cloud rearchitecture serve specific customer profiles.
How do we evaluate transition cost?
Comprehensive transition cost includes: professional services, training, internal team capacity, operational disruption during migration, opportunity cost, residual risk. Customers routinely under-estimate transition cost; explicit modelling is essential.
What if we walk and the alternative platform does not work?
This is a real risk; mitigation requires substantive proof-of-concept before commitment, phased execution with checkpoints, and contingency planning. Some customers have reverted from alternative platforms to VMware after troubled migrations; the reversion is expensive but executable.
Should we tell Broadcom that we are considering walk-away?
Strategically, yes — but with substance behind the signal. Bluffed walk-away is detected and discounted. Substantive walk-away preparation produces commercial movement; signalling without substance does not.
What happens to support and license access if we walk?
Perpetual licences (where customers still hold them) typically retain support through the contracted period and licence rights indefinitely; subscription licences expire on non-renewal. Customers should evaluate the transition implications of their specific licence structure.
