
Client: Oil and gas company in Scotland (anonymised)
An oil and gas company in Scotland ran its applications on its own VMware infrastructure. The estate held three kinds of workload: containerised applications, an ERP system, and a mix of other servers and SQL Server databases.
Veriland took the company off VMware by three routes, each chosen for the workloads it suited:
The company owned and ran the whole VMware stack itself. Every application, the ERP included, depended on that infrastructure, so leaving VMware meant deciding what should happen to each workload, not just where to copy the VMs.
The containerised applications moved from VMware to Kubernetes clusters managed with SUSE Rancher. Rancher gives the client one place to manage clusters, access and upgrades.
Rehosting the ERP would have moved the old system onto new infrastructure and kept its limits in place. We replaced it with Dynamics 365 Finance & Operations, so the ERP left VMware as a modern SaaS platform.
The remaining workloads moved to Azure. Where Azure could run a service for the client, we used the Azure service instead of a plain virtual machine. The SQL Server estate moved to Azure too.
Most VMware estates mix workloads that want different destinations. Our VMware exit service chooses a route for each one, and our guide to leaving VMware after Broadcom covers the licensing changes and the dates to plan around.