Building a Credible VMware Exit Plan:
Negotiation Leverage Through Migration Readiness
Whether you’re actually leaving VMware or building leverage for a better deal, the preparation is identical. Broadcom discounts most aggressively when they believe the customer will leave. This paper provides a 12-month exit planning framework designed to create credible competitive pressure while preparing you to execute if the terms remain unacceptable.
Executive Summary
Broadcom’s pricing responds to one variable above all others: credible churn risk. Complaints, industry outrage, and regulatory threats do not move pricing. A documented, funded, executive-sponsored migration plan — with a running pilot and a 12-month timeline — does.
5 Key Findings
Exit Plan Impact on Broadcom Negotiation Outcomes
credible exit plan
migratable within 12 months
first-year Broadcom increase
migration investment
The Dual-Purpose Plan: Leverage and Insurance
The exit plan is not a commitment to leave VMware. It is a preparation exercise that creates two acceptable outcomes.
Outcome A: Broadcom offers acceptable terms. If Broadcom responds to your credible exit plan with pricing that meets your targets (typically 1.5–2x prior spend vs. the initial 3–5x proposal), you renew VMware at significantly better terms. The exit plan investment (typically $50K–$150K for assessment, pilot, and cost modelling) has delivered 10–20x ROI through pricing improvement alone.
Outcome B: Broadcom’s terms remain unacceptable. If Broadcom will not move below your walk-away price, you execute the migration plan that is already documented, piloted, and funded. The 12-month timeline begins from a position of preparation, not scrambling. The exit plan has de-risked the migration and compressed the execution timeline by 3–6 months.
The preparation is identical whether you stay or leave. The workload assessment, platform evaluation, pilot migration, and cost model are required for both outcomes. The only variable is the final decision — which you make after seeing Broadcom’s response to your credible exit plan.
Workload Assessment: Categorising Your VMware Estate
The workload assessment is the foundation of the exit plan. It categorises every VMware workload by migration complexity and determines the sequencing strategy.
The Four Migration Categories
| Category | Workload Profile | % of Typical Estate | Migration Approach | Timeline |
|---|---|---|---|---|
| Category 1: Lift & Shift | Standard Windows/Linux VMs with no VMware-specific dependencies. Web servers, app servers, file servers, domain controllers | 40–50% | Direct VM conversion using migration tools (Nutanix Move, Azure Migrate, virt-v2v) | 1–3 months |
| Category 2: Moderate Complexity | VMs with VMware Tools dependencies, snapshot-based backup integration, or vSwitch networking. Databases, middleware, clustered apps | 25–35% | VM conversion + post-migration reconfiguration (networking, backup, monitoring) | 3–6 months |
| Category 3: High Complexity | Workloads with deep vSphere API integration, NSX micro-segmentation rules, vSAN-dependent storage, or DRS affinity rules | 10–20% | Architectural redesign or phased migration with extended testing | 6–12 months |
| Category 4: Cloud Candidates | Workloads better suited to cloud-native deployment: stateless apps, dev/test, seasonal capacity, modern microservices | 10–20% | Migrate to AWS/Azure/GCP instead of alternative hypervisor | 3–9 months |
The Assessment Process. For each VMware host and VM, document: operating system, application, VMware feature dependencies (VMware Tools version, VMware-specific APIs, NSX rules, vSAN policies, DRS/HA configuration), storage configuration (VMDK, RDM, vSAN), networking (vSwitch, distributed switch, NSX), and backup integration. This data determines the migration category and the sequencing strategy.
The workload assessment typically reveals that 65–85% of VMware workloads fall into Categories 1 and 2 — migratable within 6 months with standard tooling. The remaining 15–35% require longer timelines but are not blockers. Present the Category 1+2 percentage to Broadcom — it quantifies the portion of your estate that can leave within 6 months.
Alternative Platform Evaluation
Select one primary alternative and one secondary. Do not evaluate more than two in detail — depth creates credibility; breadth dilutes it.
| Platform | Strengths | Cost vs. Broadcom VMware | Migration Tooling | Best For |
|---|---|---|---|---|
| Nutanix AHV | Most VMware-comparable management; enterprise support; strong ecosystem | 40–60% lower | Nutanix Move (automated P2V/V2V) | Enterprise-grade replacement; HCI environments |
| Microsoft Hyper-V / Azure Stack HCI | Bundled with Windows Server Datacenter; Azure integration; System Center management | 50–70% lower (bundled) | Azure Migrate; SCVMM conversion | Windows-centric environments; Microsoft ecosystem |
| Proxmox VE | Open source; KVM-based; low cost; active community; web management UI | 90%+ lower (OSS + optional support) | qm importdisk; virt-v2v | Cost-sensitive; Linux-centric; mid-market; dev/test |
| KVM / oVirt | Open source; Red Hat lineage; maximum flexibility; no vendor lock-in | 90%+ lower (OSS) | virt-v2v (mature Red Hat tooling) | Linux-skilled teams; maximum control; open source policy |
| Cloud-Native (AWS/Azure/GCP) | No on-premise infrastructure; consumption-based; managed services | Variable — depends on workload | AWS SMS/MGN; Azure Migrate; GCP Migrate | Cloud-first strategy; reducing DC footprint |
The Recommended Selection
For most enterprises, Nutanix AHV is the primary alternative because it provides the most comparable management experience, has the most mature VMware migration tooling (Nutanix Move), and is aggressively pricing VMware displacement deals. Nutanix’s sales team actively supports migration planning for VMware accounts, including funded proof-of-concept deployments.
The secondary alternative should be Hyper-V / Azure Stack HCI for Microsoft-centric organisations, Proxmox VE for cost-sensitive environments, or cloud migration for organisations with a cloud-first strategy. Having a documented secondary alternative demonstrates depth of evaluation and increases credibility.
Migration Sequencing: What Moves First
The sequencing strategy determines both the migration risk profile and the negotiation leverage timeline.
Wave 1: Non-Production & Development
Migrate all development, testing, staging, and sandbox environments first. These workloads have the lowest risk, the least business impact from migration issues, and the fastest migration timeline. They also represent 15–25% of the VMware core count — meaning Wave 1 alone reduces the Broadcom subscription scope by 15–25% if completed before renewal.
Wave 2: Category 1 Production Workloads
Migrate standard production VMs with no VMware-specific dependencies: web servers, application servers, file servers, print servers, and utility infrastructure. These are lift-and-shift migrations using automated tooling. Each successful Wave 2 migration builds operational confidence and further reduces the VMware footprint.
Wave 3: Category 2 Production Workloads
Migrate databases, middleware, and clustered applications that require post-migration reconfiguration (networking, backup integration, monitoring). These migrations require more testing and validation but follow established patterns from Waves 1 and 2. Cloud candidates (Category 4) can be migrated in parallel to cloud providers during this wave.
Wave 4: Category 3 & Remaining
Migrate or redesign high-complexity workloads with deep VMware dependencies. These may require architectural changes (replacing NSX micro-segmentation with alternative SDN, moving vSAN-dependent storage to alternative HCI or SAN, redesigning applications with vSphere API dependencies). Some organisations choose to retain these workloads on a minimal VMware footprint rather than redesign.
Wave 1 is negotiation leverage. Wave 2 is proof of capability. Wave 3 is genuine momentum. Wave 4 is optional if Broadcom responds with acceptable pricing after seeing Waves 1–3. The sequencing is designed to create maximum leverage at each renewal checkpoint.
Cost Modelling: The Migration Business Case
The cost model must compare three scenarios over 5 years to determine the optimal path.
| Cost Component | Scenario A: Stay on VMware | Scenario B: Full Migration | Scenario C: Hybrid (Partial Migration) |
|---|---|---|---|
| Year 1 Licensing | Broadcom renewal (negotiated) | Alternative platform licensing + reduced VMware during transition | Reduced VMware scope + alternative platform for migrated workloads |
| Migration Cost | $0 | $300K–$800K (tooling, PS, internal effort) | $150K–$400K (partial migration) |
| Years 2–5 Licensing | Broadcom annual fee + escalators | Alternative platform annual fee (40–60% lower) + zero VMware | Reduced VMware + alternative platform |
| Operational Cost Delta | Minimal (existing skills) | Retraining: $50K–$150K | Dual-platform operations: $50K–$100K/yr |
| 5-Year TCO | Highest (3–5x pre-Broadcom) | Lowest (1–1.5x pre-Broadcom) | Middle (1.5–2x pre-Broadcom) |
Scenario C (hybrid/partial migration) is the most common outcome because it provides meaningful cost reduction (40–60% of VMware spend eliminated), maximum negotiation leverage (demonstrated migration capability), and manageable execution risk (only Category 1–2 workloads migrated). Scenario B (full migration) delivers the largest savings but requires the highest commitment and longest timeline.
The 12-Month Exit Plan Timeline
The exit plan mapped to a 12-month execution timeline.
| Month | Activity | Deliverable | Leverage Impact |
|---|---|---|---|
| 1–2 | Workload assessment; categorise all VMs | Migration readiness report by category | Quantifies migratable % |
| 2–3 | Alternative platform evaluation; select primary + secondary | Platform comparison with indicative pricing | Named alternatives with costs |
| 3–4 | Build 5-year cost model (3 scenarios); secure executive sponsorship | Migration business case for CFO/CIO approval | Funded, approved plan |
| 3–5 | Wave 1: migrate non-production environments | Dev/test running on alternative platform | Running pilot — credibility established |
| 5–6 | Present exit plan to Broadcom; negotiate | Renewal counter-proposal with exit plan evidence | Maximum leverage point |
| 6–8 | Wave 2: Category 1 production workloads | Standard production VMs migrated | 40–50% of estate migrated |
| 8–10 | Wave 3: Category 2 + cloud candidates | Databases, middleware, cloud workloads migrated | 65–85% of estate migrated |
| 10–12 | Wave 4: Category 3 or retain on minimal VMware | Full migration or hybrid steady-state | Migration complete or VMware reduced to minimum |
Common Exit Plan Traps
These traps consistently undermine the exit plan’s effectiveness as both a leverage tool and a migration strategy.
Trap 1: Building a Plan Without Running a Pilot
A documented plan without a running pilot is a PowerPoint exercise. Broadcom’s churn assessment team distinguishes between enterprises that have documented plans (low risk) and enterprises that have running pilots (high risk). The pilot is the credibility threshold.
Trap 2: Evaluating Too Many Alternatives
Evaluating 5+ alternatives dilutes depth and signals indecision, not preparation. Select one primary (typically Nutanix) and one secondary (Hyper-V, Proxmox, or cloud). Deep evaluation of two platforms is more credible than shallow evaluation of five.
Trap 3: Not Modelling the Migration Cost
Presenting an exit plan without a cost model tells Broadcom you haven’t done the work. The 5-year TCO model (comparing stay, full exit, and hybrid) demonstrates that the migration economics justify execution — and that you know the numbers.
Trap 4: No Executive Sponsorship
Broadcom monitors who is driving the exit plan. If it is only the infrastructure team, it is discounted as operational frustration. If the CIO or CTO is sponsoring the plan and the CFO has approved the migration budget, it is treated as a genuine strategic decision.
Trap 5: Treating Category 3 as a Blocker
Enterprises that focus on the 15–20% of workloads that are hard to migrate (Category 3) use them as an excuse not to build the exit plan. The 80% that can migrate within 12 months is the leverage — the remaining 20% can stay on a minimal VMware footprint if needed.
Trap 6: Presenting the Plan After Signing the Renewal
The exit plan must be presented to Broadcom before the renewal is signed. An exit plan presented after signing has zero leverage value. Time the plan presentation for Month 5–6, then negotiate from a position of demonstrated capability.
Recommendations: 7 Priority Actions
Execute these to build a credible VMware exit plan within 6 months.
Complete the Workload Assessment Within 60 Days
Categorise every VMware workload. Quantify the percentage in each migration category. The Category 1+2 percentage (typically 65–85%) is the number you present to Broadcom as “migratable within 6 months.”
Select One Primary and One Secondary Alternative
Evaluate Nutanix + one other (Hyper-V, Proxmox, or cloud). Obtain indicative pricing for both. Deep evaluation of two platforms is more credible than shallow evaluation of five.
Build the 5-Year 3-Scenario Cost Model
Stay on VMware, full migration, and hybrid. Include migration costs, retraining, and ongoing licensing. Present to CFO for budget approval. The approved cost model is a negotiation weapon.
Execute Wave 1: Migrate Non-Production Within 90 Days
Move dev/test/staging to the primary alternative platform. This is the pilot that converts the plan from theoretical to operational. A running pilot changes Broadcom’s churn risk assessment more than any document.
Secure CIO/CTO Sponsorship and CFO Budget Approval
The exit plan needs executive visibility. Broadcom monitors the seniority of people driving migration decisions. CIO sponsorship + funded budget = high churn risk = better pricing.
Present the Exit Plan to Broadcom at Month 5–6
Share the workload assessment, pilot results, cost model, and executive sponsorship with Broadcom’s account team. Let the evidence speak. Frame it as “standard infrastructure planning for a multi-vendor future.”
Make the Stay/Go Decision After Seeing Broadcom’s Response
If Broadcom responds with pricing that meets your targets, stay on VMware. If not, execute Waves 2–4. Either way, the exit plan investment has delivered ROI — through better pricing, through migration savings, or through both.
How Redress Can Help
Redress Compliance’s Broadcom/VMware Practice builds and executes exit plans as part of every VMware renewal engagement — whether the objective is leverage, migration, or both.
VMware Exit Planning Services
- Workload assessment & migration readiness categorisation
- Alternative platform evaluation (Nutanix, Hyper-V, Proxmox, cloud)
- 5-year 3-scenario cost modelling
- Wave 1 pilot migration planning & execution support
- Migration sequencing & risk management
- Broadcom negotiation with exit plan evidence
- Hybrid architecture design (minimal VMware + alternative)
- Post-migration optimisation & governance
Get In Touch
100% Independent. Zero Broadcom or Alternative Vendor Affiliation.
We do not resell VMware, Nutanix, Hyper-V, or any alternative. Every recommendation serves your interests alone.
Book a Meeting
Need help building a credible VMware exit plan? Request a call with our Broadcom/VMware Practice team.
Request a Meeting
Fill in your details and suggest times. We’ll confirm within 24 hours.
Meeting Request Sent
Thank you. Our Broadcom/VMware Practice team will confirm within 24 hours.
What to Expect
30-minute NDA-protected call reviewing your VMware estate, Broadcom proposal, and migration readiness to determine the optimal exit plan structure.
Based on your workload profile, we’ll recommend the primary and secondary alternative platforms and provide preliminary cost comparison data.
Clear 12-month roadmap: workload assessment, platform evaluation, Wave 1 pilot, cost model, and Broadcom negotiation timeline. No obligation.
100% Confidential. NDA-protected. We never share data with Broadcom or any vendor.
No Obligation. If your exit plan is already strong, we’ll tell you directly.
This document has been prepared by Redress Compliance for informational purposes. Redress Compliance is fully independent with zero vendor affiliations — including zero Broadcom/VMware partnership and zero partnership with any alternative vendor (Nutanix, Microsoft, Proxmox, etc.). We do not resell any virtualisation products. Benchmark data is based on anonymised engagements. Past results are not a guarantee of future outcomes.
© 2026 Redress Compliance. All rights reserved.