Home/VMware to AWS Migration
Migration guide

VMware to AWS migration: paths, tools, and real costs

There are three honest ways to move VMware workloads to AWS, and they differ wildly in effort, risk, and what they do to your bill. Here is how to choose, the tools that do the work, and how AWS stacks up against simply staying on VMware for less.

AWS is one of the most capable destinations for VMware workloads, but "migrate to AWS" hides three very different projects. Pick the wrong one and you either overpay (keeping VMware licensing you no longer need) or overspend on rework you did not have to do. This guide walks the three paths, the tooling for each, and the budget reality.

Quick read: If your priority is speed and zero refactoring, VMware Cloud on AWS keeps vSphere intact, but VMware licensing stays in your bill. If your priority is escaping VMware licensing, rehosting to native EC2 with AWS Application Migration Service is the workhorse path. The biggest long-term savings come from replatforming, and the biggest effort too.

Get a free AWS migration assessment →

The three migration paths

PathWhat it isEffortVMware licensing after?
Rehost to VMware Cloud on AWSLift-and-shift vSphere VMs into a managed VMware SDDC running on AWS bare metalLowYes, you still license VMware
Rehost to native EC2Convert VMs to EC2 instances with AWS MGN; vSphere is left behindMediumNo
Replatform / refactorRe-architect onto managed services (RDS, ECS/EKS, Lambda, S3)HighNo

Most mid-market migrations are a blend: rehost the bulk to EC2, replatform the few workloads where managed services pay off quickly (databases to RDS, file shares to FSx or S3), and leave nothing on VMware unless there is a hard reason to.

The tools that do the work

  • AWS Application Migration Service (MGN). The primary free rehost tool. It installs a lightweight agent, replicates each VM at the block level continuously, then cuts over to EC2 with minimal downtime. This is the default for native rehosting.
  • VMware HCX. Bundled with VMware Cloud on AWS for large-scale lift-and-shift, including bulk migration and vMotion-style live moves into the cloud SDDC.
  • AWS Application Discovery Service (ADS). Run this before MGN. ADS deploys a lightweight collector or agentless connector to your vCenter and maps server inventory, CPU/memory utilization, and network dependencies. The output feeds Migration Hub and prevents wave-planning surprises from undocumented app dependencies.
  • AWS Migration Hub. A single pane to track wave progress across MGN, DMS, and other tools in one view.
  • AWS Database Migration Service (DMS). For moving SQL Server, Oracle, PostgreSQL and MySQL into RDS or Aurora with minimal downtime.

What it actually costs

The migration project itself follows the same per-VM math as any replatform (see our migration cost guide). The bigger variable with AWS is the recurring run cost, which you control through purchasing decisions:

Cost leverImpactNotes
Savings Plans / Reserved InstancesUp to ~50–72% off on-demand1- or 3-year commit; the single biggest lever on EC2 cost
Right-sizing20–40% typicalVMware VMs are often over-provisioned; MGN cutover is the moment to fix it
Data egressWatch closelyOutbound transfer is billed; chatty hybrid apps can erase savings
VMware Cloud on AWS licensingMaterialOnly on the VMC path; this is the cost native EC2 removes
Reality check: AWS rarely wins on price by accident. Native EC2 with committed-use discounts and disciplined right-sizing can beat a Broadcom renewal on 3-year TCO; VMware Cloud on AWS usually wins on speed and continuity, not raw cost.

The comparison nobody runs: staying on VMware for less

Before committing to a hyperscaler, it is worth pricing the boring option. Moving to a managed VMware provider (a VCSP partner) keeps vSphere intact, so workloads move with HCX rather than being converted, and the savings against a Broadcom-direct renewal arrive fast with almost no project risk. For some shops AWS is the right answer; for many, it is more migration than the cost problem requires. Our VMware vs. VMware Cloud on AWS comparison and the full alternatives matrix lay the options side by side.

How to decide

Frame it as 3-year TCO, not migration sticker price: status quo (Broadcom renewal × 3 plus hardware) versus each AWS path (one-time migration plus run cost × 3). Run your inventory through the free cost calculator, or get a priced, advisor-built comparison across AWS, the other hyperscalers, and managed VMware with a free assessment. Once your path is set, use the migration timeline guide to phase the project and the migration checklist to track every pre-cutover step.

VMware to AWS migration FAQ

What are the main ways to migrate VMware to AWS?
There are three common paths. Rehost to VMware Cloud on AWS keeps vSphere intact and moves VMs with HCX, the lowest-effort option but you keep paying VMware licensing. Rehost to native EC2 uses AWS Application Migration Service (MGN) to convert VMs to EC2 instances, which removes VMware licensing but requires more rework. Replatform or refactor moves workloads onto managed AWS services and containers for the biggest long-term payoff and the highest effort.

Which tools migrate VMware VMs to AWS?
AWS Application Migration Service (MGN) is the primary free tool for rehosting VMware VMs to native EC2 through continuous block-level replication. VMware HCX handles lift-and-shift into VMware Cloud on AWS. AWS Migration Hub coordinates discovery and tracking, and AWS DMS handles database migrations.

Is migrating VMware to AWS cheaper than renewing with Broadcom?
It depends on the path. Native EC2 with Savings Plans or Reserved Instances can beat a Broadcom renewal on multi-year TCO because it eliminates VMware licensing, but watch egress and right-sizing. VMware Cloud on AWS keeps VMware licensing in the bill, so it usually wins on speed and operational continuity rather than raw cost. Staying on VMware through a managed VCSP provider is often the fastest savings of all.

Vendor-neutral, no cost to you

Not sure AWS is the right move?

A Bridgepointe advisor prices AWS against the other hyperscalers and managed VMware, using your real inventory, so you compare apples to apples before you commit.