Virtualisation and VMware migration
Run virtual machines beside containers on one Kubernetes or OpenShift platform, and move workloads off VMware in planned waves, each with a way back.
One platform for virtual machines and containers
Most organisations will run virtual machines for years to come: packaged software, Windows servers and systems that can't be containerised yet. Running them on a separate hypervisor means two platforms, two teams and two sets of licences.
With OpenShift Virtualization, built on the open-source KubeVirt project, virtual machines run on the same Kubernetes platform as containers, with the same networking, storage, automation and monitoring. Since VMware's licensing changes, many organisations are using it to leave VMware altogether. We plan and run those migrations, wave by wave.
When it fits
01
A VMware renewal is due
The renewal quote has gone up, and you want to compare the alternatives before you sign.
02
Two platforms, two teams
Virtual machines and containers are run separately, with duplicate tools and skills.
03
Software that can't be containerised yet
Packaged or Windows applications need VMs, but you want them on your modern platform.
04
A hardware refresh is coming
Servers are due for replacement, a natural moment to change the platform that runs on them.
What we do
Virtualisation assessment
Inventory your VMs, group them by fit, and compare the cost of staying, moving and containerising.
Platform design
Size clusters for VM workloads, with the networks, VLANs, storage and live migration they need.
Migration in waves
Move VMs with the Migration Toolkit for Virtualization, using warm migration to keep downtime short and a rollback plan for each wave.
Windows and Linux guests
Run supported Windows Server and Linux guests, with drivers, templates and backups set up.
VM operations
Templates, live migration, snapshots, backup and monitoring for VMs, with the same tools as containers.
Containerise over time
Once VMs run on Kubernetes, modernise them into containers one by one, where it pays.
Migration waves
VMs move in planned waves, next to the containers already there
We group virtual machines into waves by risk and dependency. Each wave is tested and moved in a planned window with a way back, and the old platform shrinks as each wave lands, until it can be switched off.
- VMs on the existing hypervisor
- Still running where they are, until their wave.
- Migrated VMs
- Running on the Kubernetes platform, on the same networks and storage as containers.
- Containers on the same platform
- Modern applications sharing the same nodes, tools and team.
- Migration waves
- Groups of machines moved together, lowest risk first.
How we migrate
01
Assess
Inventory the VMs, map dependencies and licences, and decide which to move, which to containerise and which to retire.
02
Build
Build the platform, connect networks and storage, and move a pilot wave of low-risk VMs.
03
Migrate
Move the remaining VMs in waves, with warm migration, testing and a rollback plan for each.
04
Retire and optimise
Switch off the old hypervisor, reclaim licences and hardware, and plan which VMs to modernise next.
What you get
- A VM inventory with a decision for each machine
- A cost comparison of staying, moving and containerising
- A virtualisation platform, built and tested
- A wave plan with rollback steps
- Migrated VMs, verified with their owners
- Runbooks for running VMs on the new platform
Platforms and tools
Moving from
- VMware vSphere and ESXi
- Microsoft Hyper-V
- Red Hat Virtualization
To
- OpenShift Virtualization
- KubeVirt
- Migration Toolkit for Virtualization
- OpenShift Data Foundation
- OpenShift API for Data Protection
- Ansible Automation Platform
Questions about virtualisation
Is OpenShift Virtualization ready for production?
Yes. It is a fully supported part of OpenShift, widely used in production, and built on KubeVirt, a CNCF project.
Do we need OpenShift, or can we use upstream KubeVirt?
Upstream KubeVirt works, but you assemble and support it yourself. OpenShift Virtualization adds the migration toolkit, a console, tested storage and networking, and vendor support, which most production estates need.
How much downtime does a migration need?
With warm migration, data is copied while the VM keeps running, and the final cutover usually takes minutes. Each wave runs in an agreed window with a way back.
Will our backup and monitoring tools still work?
Many will, and the platform's own tools cover VMs and containers together. We check each tool during the assessment and plan any replacements.
Should we containerise instead?
Where it pays, yes. Moving the VM first and modernising later is often faster and safer, because it separates the platform change from the application change.
Containerisation and replatformingPlan your move off VMware
Tell us how many VMs you run and when your renewal is due. We'll suggest an assessment and a first wave.