Productive IT / Business Operations & ERP briefing · 2026-09-11

The signal

Industry reporting has described customers finding it harder to migrate off VMware after Broadcom restricted access to downloads of a key software development kit. We are not restating the details and cannot verify every claim, so treat this briefing as commentary on the pattern rather than on the specific case. The pattern is common: when a vendor changes licensing, support or access terms, the customers with the least preparation face the shortest and most expensive choices.

What it means for a growing business

Virtualisation sits underneath ERP, finance, file services and line-of-business applications. A change in how a vendor licenses or distributes its tooling therefore reaches the business as a budget question, a project-delay question or a compliance question, depending on who is asking.

Even if you do not use this particular vendor, the same exposure exists with any platform that your operations quietly depend on, including databases, backup tools, identity providers and cloud services. The relevant point is not whether a vendor is good or bad. It is whether you can still operate and move if its terms change.

The Productive IT view

  • Inventory your dependencies. List what runs where, which licence covers it, when it renews and who owns the relationship. A spreadsheet is enough to begin.
  • Hold what you are entitled to. Where your licence permits it, keep copies of installers, SDKs, documentation and keys for the versions you run, stored safely and tested, so a portal change does not block a migration.
  • Read renewal clauses early. Notice periods, price-change terms and end-of-support dates should be on a calendar well before the renewal date.
  • Prefer open formats and standard interfaces. When you build automation, favour tooling that can be pointed at another platform without a rewrite.
  • Rehearse a migration on a small workload. Moving one low-risk system end to end teaches you more about the real effort than any estimate.
  • Plan the business side. Agree downtime windows, data validation steps and rollback criteria with the teams that depend on the system, not only with IT.

Costs that are easy to miss

Migration estimates often count servers and licences but overlook the surrounding work: retraining administrators, rewriting scripts and runbooks, updating backup and monitoring tools, re-validating security controls, and running two environments in parallel for longer than planned. There is also the cost of delay, because a rushed renewal under unfavourable terms can exceed the cost of a well-planned move. Put these items in the plan early, ask each team that touches the platform for its own list, and add a contingency. A realistic estimate is the strongest argument you will have when decisions are being made.

A practical next step

Identify the three platforms whose sudden change would hurt your operations most, and for each one write down the renewal date, the copy of the software and documentation you hold, and the first step of an exit plan. If you would like an independent view while you do this, start a brief with Productive IT.

This is original Productive IT commentary informed by public reporting. It does not endorse or compare any vendor and is not legal or licensing advice. Check your own contract terms.