Back to Insights

The VMware Renewal Playbook: How a Nine-Hospital System Cut Its Broadcom Exposure in Half

VMware to Azure migration data center transformation visualization
ShareLinkedInEmail

By Leigh Sleeman, Partner, T2 Group  ·  May 2026  ·  VMware Migration

Most healthcare technology articles about Broadcom's VMware pricing changes stop at the headline number. The 300 to 1,000 percent increase. The five-year minimum commitment. The shock.

Headlines do not help a CIO build a business case. Numbers do.

If your renewal lands in the next 12 to 24 months, this story maps the sequence of decisions you will need to make.

The starting position

Sharp HealthCare is a nine-hospital system in Southern California. Their VMware footprint at peak was approximately 9,400 licensed cores, supporting hundreds of applications across the system.

That was the baseline. Stable, predictable, manageable infrastructure cost.

Then Broadcom acquired VMware. The renewal quote that came back at the end of 2025 was structured differently. That is what a Broadcom renewal looks like for a hospital that has not actively reduced its footprint. Not a discussion. Not a negotiation. A take-it-or-leave-it commitment for five years.

If your VMware renewal arrives and you have not done the work to reduce your footprint first, you are negotiating against yourself.

The work that bent the curve

Sharp did not accept the renewal quote at face value. Instead, the program focused on a single question: how much of the existing VMware footprint was actually required?

The answer, as it usually is, was less than half.

Step 1: Inventory and right-size

Before any migration, before any platform decision, the first work was understanding what was actually running. Across nine hospitals and 9,400 licensed cores, my team mapped utilization against allocation. We identified zombie virtual machines, oversized hosts, redundant training environments, and workloads that had been provisioned years earlier and never decommissioned.

In my experience across hospital environments, this exercise typically reveals 20 to 40 percent of licensed cores can be reclaimed without migrating anything. At Sharp, the reduction was at the higher end of that range.

Step 2: Build the Hyper-V alternative

In parallel with the right-sizing work, we built and validated a Microsoft Hyper-V environment as the migration target. Hyper-V was selected for the same reason most hospitals end up there: it integrates with existing Microsoft infrastructure, the licensing is often included in Datacenter agreements, and the operational pattern is familiar to teams already running Windows Server at scale.

Sharp now has a fully operational Hyper-V environment, validated against representative workloads, with documented operating procedures.

Step 3: Migrate in waves, sequenced around clinical operations

Migration waves were planned around clinical impact, not VM count. Non-clinical workloads moved first, including administrative systems, test environments, and reporting tools. Clinical-adjacent systems followed. Core clinical applications were sequenced into tightly controlled change windows.

The core count came down. Wave by wave, application by application, the licensed footprint shrank from 9,400 cores toward 4,300.

Why the story is not done yet

The 4,300 cores still running on VMware at Sharp carry a real commitment over the term. The strategic objective is to drive that number to zero before the next renewal cycle forces another decision.

The remaining migration work is harder than the work already done. The applications still on VMware tend to be the more complex ones: the systems with deeper integrations, the older platforms with thinner vendor support, the workloads where the application owner is more cautious about change. None of these are reasons to stop. They are reasons to be deliberate.

Sharp has decided to accelerate. That means more applications moving per quarter, more parallel work streams, and more coordination between infrastructure and application teams. It also means a different conversation about how the work gets paid for.

The shared-risk model

On qualifying engagements like this one, T2 Group offers a shared-risk pricing model that ties a portion of our fees to delivering documented savings. The structure is straightforward.

During the assessment phase, we project the savings the migration will produce against the current and forecasted VMware spend. We then propose a fee structure where a portion of our compensation is contingent on hitting the savings number within the agreed timeline. If the savings show up, we are paid in full. If they do not, we are not.

This is not available on every engagement. It requires the right scope, the right timeline, and a level of alignment up front that most engagements do not have. But for hospitals that want a partner with skin in the game on the financial outcome, it is on the table.

We can offer shared-risk pricing because we have done the math, run the assessment, and seen the savings appear in real environments. The model only works when both sides have done the work to make the projection real.

What to do with this

If your hospital is approaching a Broadcom renewal, the playbook is not complicated. It is just hard to execute without disciplined coordination.

If your renewal is more than 24 months away

Start the assessment. Map your current footprint against actual utilization. Quantify your zombie VM and right-sizing opportunity. Build the Hyper-V proof of concept. Begin migrating non-clinical workloads as the first wave. You have time, but only if you start using it now.

If your renewal is 12 to 24 months away

Do everything above, faster. Stand up the wave program. Get application owners and infrastructure leads in the same weekly cadence. Sequence the high-confidence migrations so the core count is meaningfully lower by the time the renewal lands.

If your renewal is inside 12 months

Your options narrow but they do not disappear. The right-sizing exercise alone can reduce the renewal by hundreds of thousands of dollars. Even if you have to sign a new contract because you are not yet at zero cores when the renewal date arrives, you may still benefit from an accelerated migration plan if you have the option to terminate-for-convenience when you get to zero Broadcom products installed. The math gets harder but it is still defensible.

Whatever your timeline

Do not negotiate the renewal until you have done the assessment work. The conversation with Broadcom changes when you can show them which workloads are leaving and when. The conversation with your CFO changes when you can put a number on the savings. The conversation with your board changes when you have a plan, not just a problem.

Final numbers

9,400 cores down to 4,300. A path to zero before the next renewal. A shared-risk model that ties a partner's fees to the savings.

This is what the math looks like at hospital scale when the work gets done right. Your numbers will be different, but the structure of the decision will not be. The renewal is coming, the licensing model has changed, and the only variable left is whether you do the work now or sign another costly commitment later.

Save the Renewal

Your renewal is coming. Let's reset the math.

15-minute scoping call with a T2 Group migration lead. No deck, no pitch, just your environment and your timeline.

About the Author

Leigh Sleeman is a Partner at T2 Group, a healthcare-focused IT consulting firm serving hospitals and health systems since 2006. He leads delivery for the firm's hospital VMware migration practice, including the eighteen-month engagement at Sharp HealthCare across nine hospitals.

Frequently Asked Questions

How much did Sharp HealthCare reduce its VMware footprint?

Sharp HealthCare reduced its licensed VMware footprint from about 9,400 cores to about 4,300, a reduction of more than 50 percent across nine hospitals. The work included right-sizing zombie VMs, migrating workloads to Hyper-V in clinical-freeze-aligned waves, and building a sustainable decommission plan.

What is the typical VMware to Azure migration timeline for a hospital?

A mid-size hospital migrating several hundred virtual machines typically completes in 9 to 12 months. Multi-hospital systems with 1,000+ VMs plan for 12 to 18 months. Timelines are driven by clinical freeze windows and application dependency complexity as much as by VM count.

What is T2 Group's shared-risk pricing model for VMware migration?

On qualifying engagements, T2 Group ties up to 20 percent of its fees to documented savings from the migration. If the projected savings do not materialize within the agreed timeline, the client does not pay the full fee. The model requires a completed assessment and agreed-upon savings projection before it applies.

How do you right-size a VMware environment before migration?

The right-sizing exercise maps current VM utilization against allocation across every host. Teams identify zombie virtual machines (provisioned but idle), oversized hosts, redundant test environments, cluster consolidation, and workloads never decommissioned after a prior project ended. In hospital environments, this exercise typically reveals 20 to 40 percent of licensed cores can be reclaimed before any migration begins.

Ready to explore a partnership?

Let's Connect

We use cookies. View our Privacy Policy