Skip to main content
Cloud DevOps Solutions
Get a quote Talk to an engineer

Planning a VMware exit? Start with the workloads

Licensing and pricing changes after the Broadcom acquisition have led many teams to reassess VMware. The useful first question is not which platform, but which workloads need to move, in what order, and what each can become.

Book a working session See a sample report
Verified credentials Azure DevOps Engineer Expert Azure Administrator Associate Certified Kubernetes Administrator

Signs this is your moment

  • A VMware renewal or new licence bundle is forcing a decision
  • Cost has changed and you need options before the next contract date
  • Applications are ageing and only partly containerised
  • The team wants a cloud or Kubernetes path but has no sequence for getting there
  • Dependencies between virtual machines are poorly documented

How we approach it

  1. Workload inventory

    Group virtual machines by function, dependency, data sensitivity and how much change each tolerates.

  2. Target per workload

    Decide for each group whether it is containerised, moved as is to cloud virtual machines, replaced by a managed service, or retired.

  3. Landing zone

    Build the target AWS or Azure foundation, or the Kubernetes platform, with networking, identity and guardrails first.

  4. Migrate in waves

    Start with low-risk workloads, rehearse cut-over and rollback, then move the critical ones.

  5. Operate and optimise

    Add monitoring, backup and cost controls so the new platform is run properly from day one.

What you receive

  • A workload inventory with a target and an order for each group
  • A landing zone or Kubernetes platform design in code
  • A wave plan with cut-over and rollback steps
  • A cost comparison method you can check against your own invoices

Start with a defined piece of work: Landing Zone Sprint. Scope and timeline are agreed in writing before anything starts.

Pricing and licence terms depend on your own agreement with your vendor. We do not quote them here.

Go deeper

Common questions

Does everything have to become containers?
No. Some workloads are better moved as virtual machines or replaced by managed services. We decide per workload, not for the whole estate.
Do you replace the hypervisor?
Our focus is the cloud and Kubernetes side: the target platform, the migration sequence and operations. We scope anything outside that in writing, or tell you it is a poor fit.
Can we do this before our renewal date?
A fixed-scope assessment can usually be completed quickly. We confirm timing in the written scope, based on current capacity.

Talk it through with an engineer

A free 30-minute working session that ends with a short written roadmap.

Book a working session

Also: Jenkins migration, Kubernetes upgrades, Audit preparation