vSphere 8 end of support in Switzerland: 11 October 2027 holds
vSphere 8 end of support stays 11 October 2027 in Switzerland: Broadcom's extension to 2028 covers the EEA only. The renewal options and a dated exit plan.
On 4 November 2026, Broadcom announced that vSphere Standard 8 and vSphere Enterprise Plus 8 stay on sale to customers in the European Economic Area (EEA) until 31 October 2027, with Extended Support in active subscriptions until the subscription ends or 31 October 2028, whichever comes first. Switzerland is not in the EEA and the announcement does not mention it, so for a Swiss organisation vSphere 8 end of support stays on 11 October 2027, after which Broadcom promises “no Technical Support and no new patches” unless it sells that organisation Extended Support. As of 6 November 2026, that leaves 339 days to secure that support, commit to version 9 on Broadcom’s terms or move the virtual machines off.
This post covers the announcement, the Swiss position, the options at renewal, an exit timetable, and a move to Proxmox VE or KVM in waves.
What did Broadcom announce on 4 November 2026?
The paragraph reads: “Furthermore, for customers in countries in the European Economic Area, vSphere Standard version 8 and vSphere Enterprise Plus version 8 will remain available for sale until October 31, 2027, and will have Extended Support included in any active subscriptions to those offerings until the earlier of the applicable subscription end date or October 31, 2028.”
It gives no reason for limiting the offer to the EEA, and it does not define Extended Support. heise finds it “unclear whether its scope and response times match those of regular support” and notes that it makes no commitment for perpetual licences.
The same post introduced vSphere Express, built on vSphere 9 and “available immediately in all regions”. Its documentation sets “a maximum of 128 cores per customer” and states: “vSphere Express is only available for version 9 or later.” Broadcom has not published a price.
When does vSphere 8 end of support apply in Switzerland?
On 11 October 2027. Broadcom’s KB 459135 reads: “The End of general support for vSphere 8.0 is October 11, 2027”, for ESXi, vCenter and vSAN 8.x. KB 456708, dated 15 October 2026, adds: “Post the listed End of Service dates, there will be no Technical Support and no new patches for these product versions.” Neither article carries an EEA note.
The EEA is the EU plus Iceland, Liechtenstein and Norway, and EFTA states that “Switzerland is not part of the EEA Agreement”. On the plain text, a customer in Liechtenstein is covered and one in Switzerland is not, which is how heise and Network World read it too. Broadcom’s post names no country.
Swiss customers lost nothing on 4 November. Their date was 11 October 2027 before the announcement, and it still is. What they did not get is the extra time:
| Customer | vSphere 8 support until | Days after 6 November 2026 |
|---|---|---|
| Switzerland, and any other country outside the EEA | 11 October 2027, end of general support, unless Broadcom sells you Extended Support | 339 |
| EEA, with an active Standard 8 or Enterprise Plus 8 subscription | Subscription end or 31 October 2028, whichever is earlier | Up to 725 |
Two questions stay open. First, who counts as an EEA customer? Network World reports Aman Mahapatra of Tribeca Softech asking whether eligibility follows the contracting entity, the billing address or the location where the software runs; he advises: “Get Broadcom’s interpretation in writing before building a plan on it.” The same question, who signs and where, decides whether the EU Data Act’s switching rules protect a Swiss group in its cloud contracts.
Second, can a Swiss organisation still renew Standard 8 or Enterprise Plus 8 at all? Broadcom does not say. C4C, a UK consultancy, wrote on 4 November 2026 that “resellers report that Standard and Enterprise Plus reached end of sale elsewhere at the end of October 2026”. C4C writes from the UK and does not name Switzerland; that is the resellers’ account, not Broadcom’s.
What are the options at a Swiss renewal?
As of 6 November 2026, a Swiss organisation has five routes:
- Version 9 on VMware Cloud Foundation (VCF) or vSphere Foundation (VVF). KB 456708 recommends both. So far, heise reports, Standard and Enterprise Plus are available only up to version 8 Update 3. In December 2025, a Broadcom spokesperson told The Register that “VVF is no longer available in some EMEA countries”, without naming them, so ask whether it is sold in Switzerland.
- vSphere Express, if you are eligible. Version 9 only, 128 cores for the whole organisation, upgradeable from vCenter Server 8.0 and ESXi 8.0. We found no published eligibility rules; C4C, citing reseller briefings, says existing customers need Broadcom’s authorisation.
- Extended Support for vSphere 8, if Broadcom sells it to you. It is included in the EEA subscriptions above. For other customers, the latest Broadcom statement we found, in an August 2025 post for SAP customers, says vSphere 8 “will be supported until October 2027, with an optional two-year Extended Support period available for purchase”. We found no published scope or price.
- Staying on vSphere 8 without Broadcom support. The hosts keep running, but KB 456708 promises no new patches after 11 October 2027.
- Leaving. Proxmox VE or plain KVM for what stays a virtual machine, containers for services that fit, retirement for what nobody uses. It is the only route whose timetable you set.
Then set your renewal date against 11 October 2027. A vSphere 8 renewal, if your reseller still offers one, does not move that date: after it, the hosts run without patches unless Extended Support is in the contract. That renewal is the decision point: version 9, or the shortest term that covers your exit.
Staying is a project too: even Express requires VCF Operations and a licence server next to ESX and vCenter.
How long does a VMware exit take?
An exit in waves can fit into 339 days if it starts in November 2026; it is unlikely to if it waits for the renewal quote. The timetable is our suggestion; only 11 October 2027 is Broadcom’s date.
| Phase | By | What it produces |
|---|---|---|
| Inventory | 18 December 2026 | Every virtual machine with its operating system, disks, network, dependencies, owner and window |
| Decision per machine | 29 January 2027 | Move as a VM, rebuild as a container or retire; the target platform; the order of waves |
| Target built, pilot wave | 31 March 2027 | Hosts, storage, network, backups and monitoring running; a few low-risk machines moved; a restore tested |
| Production waves | 30 July 2027 | The bulk of the estate, a few machines per wave, each with its rollback |
| Hard cases | 17 September 2027 | Large databases, appliances, encrypted disks, anything that failed a first attempt |
| Decommissioning | Before 11 October 2027 | Sources removed once their owners have signed off |
If your renewal comes before 29 January 2027, decide before it. The weeks after the last wave are the margin.
How to move to Proxmox VE or KVM in waves
Inventory first. From a vCenter export, record for each machine the guest operating system, each disk and its datastore, encryption, virtual TPM, snapshots, networks, dependencies, owner and maintenance window.
A pilot wave. Move a handful of low-stakes machines that look like the rest onto a target cluster built for production; Proxmox recommends at least three nodes so that the cluster keeps quorum. It tests the runbook, not the hypervisor.
Conversion and testing. Proxmox VE has an import wizard that reads virtual machines straight from an ESXi host, tested by Proxmox from ESXi 6.5 to 8.0. Its migration guide lists what to plan around:
- vSAN. “Importing a VM with disks backed by a VMware vSAN storage does not work”; moving the disks to another datastore first may work around it.
- Encrypted disks. They “cannot be imported” until the encryption policy is removed.
- Virtual TPM. “It is currently not possible to migrate the vTPM state to Proxmox VE from VMware”, so keep the manual recovery keys of any guest whose disk encryption relies on it.
- Snapshots. An import “can be significantly slower if the VM has snapshots”; consolidate them first.
- Windows drivers. Windows guests need VirtIO drivers for the recommended devices; install them before the move where you can.
Live import shortens the downtime but does not remove it. Plain KVM with libvirt suits smaller or fully automated estates.
Backups and monitoring before cutover. A migrated machine goes into production only once its backup has run and has been restored at least once, and its monitoring alerts someone who will act. Keep the VMware source powered off but intact until the owner signs off.
Then the rest, in small waves and agreed windows, with the expected downtime written down in advance.
What to do, and by when
Only 11 October 2027 and 31 October 2027 are Broadcom’s dates; the others are our suggested timetable.
- By 20 November 2026: put your dates in one place. For each VMware contract: end date, contracting entity, where the hosts run, subscription or perpetual licence, and licensed cores.
- By 4 December 2026: put five questions to your reseller, in writing. Can we renew Standard 8 or Enterprise Plus 8 in Switzerland, and until when? Does the EEA offer follow the contracting entity, the billing address or the site? Are we eligible for vSphere Express? Is Extended Support for vSphere 8 available to us, with what scope and until when? Is VVF sold in Switzerland?
- By 18 December 2026: finish the inventory, with the fields above for every machine.
- By 29 January 2027, or before any earlier renewal: decide per machine and price both routes, version 9 with its upgrade project against an exit. For EEA customers, Broadcom keeps Standard 8 and Enterprise Plus 8 on sale until 31 October 2027.
- By 31 March 2027: finish the pilot wave, with backups, a tested restore and monitoring in place.
- By 17 September 2027: finish the last wave, hard cases included.
- By 11 October 2027: run nothing on vSphere 8 without a written support commitment. Every host is upgraded to a supported version, covered by Extended Support in a signed contract, or switched off.
What an open-source hypervisor does not give you on its own
Broadcom sets vSphere’s terms region by region: “Customers will have to reach out to sales reps or partners to determine availability of a given product in their region,” a Broadcom spokesperson told The Register in December 2025. Proxmox VE is licensed under the GNU AGPLv3, whose rights “are irrevocable provided the stated conditions are met”. KVM is part of the Linux kernel. The licence reads the same in Vaduz and in Bern.
That does not make Proxmox VE a drop-in vSphere. On its own, it does not give you:
- Every vSphere feature. Live migration, clustering and high availability are there. The dynamic load balancer that Proxmox VE 9.2 added on 21 May 2026 migrates guests managed by its high-availability stack (check it against the DRS rules you use), and snapshots on shared thick LVM over iSCSI or Fibre Channel are a technology preview. Some VMware features have no direct equivalent.
- Your tooling. Backup jobs, monitoring checks and scripts written against vCenter have to be replaced or rewritten.
- Your team’s skills. Linux bridges, Corosync quorum and ZFS or Ceph storage are new to a team trained on vSphere.
- Someone to call. Proxmox’s Basic, Standard and Premium subscriptions include technical support, one per node. Without one, or an operator, nobody is bound by contract to answer.
Each gap is operations work, and each can be closed before the first production cutover: a list of the features you use with how each is covered, backups and monitoring built for the new platform, runbooks and training, and a support subscription or an operator under an SLA. Run that way, an open-source hypervisor ends the lock-in that 4 November made visible: whether your country is on the right list stops mattering.
How Pilae fits
Pilae moves virtual machines off vSphere to Proxmox VE, plain KVM or containers, and runs the result on your premises, on dedicated machines in Pilae Cloud, or across both. On premises comes first: Proxmox VE and KVM usually run on the servers you already have. Operation on your premises, or across both, starts on the Business plan; plans are on the pricing page.
- A target for every machine, at a fixed price. We read your vCenter inventory and decide with you what each machine becomes. VMware features with no direct equivalent are listed in the plan with the way we cover each one, and onboarding for the VMware exit is quoted at a fixed price before work starts.
- Waves with the source as the rollback. Disks are converted and drivers checked before cutover. Each wave is tested by its owner and switched over in an agreed window, and the source machine stays intact until its owner signs off.
- Backups from the first wave. Each migrated workload is backed up daily, encrypted and stored offsite in your chosen country. On the Enterprise plan, a restore is also tested every month and recorded in the console.
- Alerts to an engineer. Metrics are kept for every machine, and a failed probe or a crossed threshold alerts a Pilae engineer at any hour, on every plan (monitoring).
- Operated after the move, with you approving. We run the new platform under managed operations, with updates planned by the Pilae Agent and approved by you.
To find out what 11 October 2027 means for your estate, talk to an engineer: send us your vCenter inventory, and we name a target for each group of machines and quote the migration at a fixed price.