VMware, SAP, Java Renewals: Build Leverage 12 Months Ahead

IT leaders are weighing alternatives to VMware, SAP's ERP suites and Oracle Java, according to a November 10, 2026 CIO feature by Grant Gross. They cite licensing costs, support changes and AI-assisted coding. The piece is just as clear that wholesale replacement isn't imminent. Executives describe migration costs, operational risks and long transitions as major obstacles.

In a survey CloudBolt commissioned in January 2026, 86% of 302 IT decision-makers at North American companies with 1,000 or more employees said they were actively reducing their VMware footprint. Only 2% had moved at least three-quarters of their environment off it.

In my view, VMware, SAP and Java are monopolies, or they're so deeply connected to a customer's tech stack that they know change isn't easy. In that, they're no different from any other technology vendor. Once customers buy, they don't manage the renewals or the price increases. By the time they realize it's renewal time, it's too late to explore the market. There are alternatives for any vendor, but the question is whether you have the time and the resources to really be prepared. For systems this deep, being prepared starts at least 12 months before the renewal.

Why Do Broadcom VMware Customers Face 300% Price Increases Before Contract Renewals?

Since Broadcom bought VMware, some customers have seen increases of 300% to 700%. On a platform that complex and integrated, the call can come two months before the renewal. There's no way to evaluate alternatives or make a switch in that time. The customer may be mad, but oftentimes they still end up paying. Or the vendor offers to reduce the increase if they sign a three-year term. Either way, they're locked in for a long time, in a situation they didn't want.

I spent 15 years on the vendor side of telecom. Before a big renewal, a vendor's sales team spends about 90 days strategizing and building a playbook, while the customer usually starts dealing with it 30 days out. The line was always some version of this: the service has been great, the team put in a lot of effort, and the pricing you have is really, really good. All of it was meant to give the customer enough comfort and confidence not to go out to market. With a VMware or SAP renewal, the vendor barely needs that line, because two months isn't enough time to go to market anyway.

What Technical Switching Costs Prevent Dissatisfied Enterprise VMware Customers from Changing Vendors?

Kevin M. Coles of Coles Technical Group told CIO that VMware customers may stay despite their dissatisfaction. Undocumented integrations, dependent reports, staff expertise and the cost of running systems in parallel all make switching hard. I agree, and the vendor knows those costs as well as you do.

We found about 50% savings for one customer if they moved off UKG, their HR and workforce management system. They stayed because UKG was so intertwined with their business that they didn't want the effort of switching, and sometimes that makes sense.

Staying still doesn't have to mean paying whatever the incumbent asks. Most of Varisource's savings come from customers who stay with their existing vendor. One customer was quoted $1.1 million for Cisco UCS blades, and Cisco said it had already given its maximum discount. We brought in competing quotes from HP and Dell, and Cisco came down to around $825,000. Even when the CIO has no plan to switch, we still run a quick RFP to create that competition. It's what lets a customer tell VMware, SAP or Oracle: if you truly are not going to be a good partner, we do have options as a customer.

Why Do Enterprise VMware and SAP Contract Renewals Require a 12-Month Preparation Timeline?

Most of the negotiations we've lost came down to time. Customers came to us with two weeks left on a vendor deeply integrated into their systems, and the vendor knew they weren't going to switch in two weeks. We track most renewals 90 to 120 days ahead. For VMware or SAP, we start at least 12 months out, because they take so long to migrate off, or even to find alternatives for.

Brad LaPorte, a strategic adviser quoted in the piece, said VMware transitions can take up to four years. So those 12 months are for being ready when the vendor calls. By then you want the contract, inventory and vendor data tracked, alternatives benchmarked and a migration path mapped. You also want a view of the next price increase and room to negotiate early. AI solutions that make a migration faster and easier belong in that plan too. They make the threat of leaving believable, and that gets VMware, SAP or Oracle to negotiate fairly.

As of November 2026, VMware, SAP ECC and Oracle Java each carry a licensing or support change with a deadline and a cost, and VMware's and SAP's land in late 2027.

For ECC customers, the exact date depends on your version. Under SAP's own support strategy, mainstream maintenance for ERP 6.0 on enhancement packages 6 to 8 ends December 31, 2027, with optional extended maintenance through 2030. ERP 6.0 with no enhancement package, or with packages 1 to 5, already reached that point on December 31, 2025. Twelve months before the end of 2027 is December 31, 2026. That's the latest I'd want preparation underway, whether the answer is S/4HANA, extended maintenance or third-party support.

If VMware, SAP or Java runs in your environment, the vendor already knows your renewal date and how hard leaving would be. Varisource does the tracking, benchmarking and market work so your engineers don't have to. I'm glad to look at where your renewals sit before that call comes.