Executive Summary
Lift-and-shift gets you to the cloud fast and can quietly cost more than the data center you left — migration is a portfolio strategy decided application by application, not a tool you point at everything.
The cloud-vendor-native suites — AWS Transform with Application Migration Service (MGN), Azure Migrate, and Google Cloud Migration Center — handle the mechanics of moving workloads: discover the estate, map dependencies, replicate at the block level, and cut over with near-zero data loss. But the mechanics are the easy part, and they are deliberately tied to a single destination cloud. The real decision is strategic: which of the six R’s — retire, retain, rehost, replatform, repurchase, or refactor — each application warrants, and how to avoid simply relocating your costs into someone else’s data center.
This guide provides a vendor-neutral framework for 8 platforms spanning both halves of the journey — assessment specialists (Device42, Flexera/Cloudamize), the three hyperscaler-native suites, third-party any-to-any movers (Zerto, OpenText Migrate), and VMware HCX for in-place mobility. It weighs dependency-aware discovery, the fit of rehost-versus-replatform-versus-refactor paths, and the one force now driving most enterprise migration timelines: the Broadcom-era VMware licensing upheaval pushing estates off vSphere.
Why Cloud Migration & Modernization Platforms Matter for Enterprise Strategy
Cloud-migration selection is dominated by strategy, not tooling: the decisive work is assessing the application portfolio, choosing the right migration path for each workload, and optimizing afterward — because rehosting everything as-is reaches the cloud while forfeiting its cost and agility benefits. Weigh discovery and dependency mapping heavily, and remember that native tools steer you toward a single cloud, which shapes lock-in for years. The timing pressure is rarely self-imposed anymore: since Broadcom moved VMware to subscription-only bundles, the renewal clock — not an internal modernization mandate — is what now forces most estates to decide where they land.
Migration tooling is converging with cloud-native modernization and AI-assisted assessment and code refactoring, pushing teams past pure lift-and-shift toward genuine modernization — AWS Transform and Azure’s Copilot-based migration agents now generate path recommendations and even refactor mainframe COBOL and legacy app code as part of the same workflow. Weigh how each platform supports assessment and modernization, not just replication, because the value of a migration shows up in the optimization and rearchitecture that follow the move, not in the move itself.
Sourcing & Destination Decision
Migration is almost never a build-vs-buy question — no enterprise hand-rolls block-level replication or dependency discovery anymore. The real decisions are which destination you are committing to, and whether a single cloud-native suite is enough or whether you need vendor-neutral assessment and any-to-any movers on top. For most enterprises in 2024–2026 the trigger is the VMware renewal, so frame the choice around where the vSphere estate lands and how much you modernize on the way.
| Your Situation | Recommended Path | Rationale |
|---|---|---|
| VMware estate facing a Broadcom subscription renewal | Assess first, then pick a destination | The renewal sets the deadline, not your readiness. Run dependency-aware discovery (Device42, Flexera, or the native suite) before committing, so you exit to cloud, a hyperscaler-hosted VMware service, or a private-cloud landing zone with eyes open — not under deadline panic. |
| Committed to one hyperscaler for the bulk of the estate | Cloud-native suite (MGN / Azure Migrate / Migration Center) | The destination cloud’s own toolchain is free or low-cost, deeply integrated, and the fastest path for straightforward rehost and replatform. Lock-in to that toolchain is acceptable when the landing cloud is already decided. |
| Multicloud or cloud-to-cloud moves on a recurring basis | Third-party any-to-any mover (Zerto, OpenText Migrate) | Native tools only move toward their own cloud. A platform-agnostic replicator handles physical, virtual, and any-cloud source and target with one workflow, and avoids re-tooling for every destination. |
| Tier-1 apps needing near-zero downtime at cutover | Continuous, journal-based replication (Zerto-class) | Snapshot-style migration widens the cutover window. Continuous block/journal replication keeps the target in sync to seconds, enabling non-disruptive test cutovers and rapid rollback for revenue-critical systems. |
| Large mainframe or COBOL portfolio in scope | Refactor program, not a rehost (AWS Transform, specialist SI) | Mainframe is a modernization project, not a migration job — code analysis, refactoring of COBOL/JCL/CICS, and data conversion dominate. Treat it as a separate workstream with agentic-AI refactoring and partner services, sequenced after the distributed estate. |
Key Capabilities & Evaluation Criteria
Weight these domains against your estate and your destination strategy. For most enterprises the assessment half of the journey — discovery, dependency mapping, and path recommendation — now outranks raw replication speed, because that is where migrations actually fail. If a Broadcom-driven VMware exit is your trigger, weight source-platform coverage and cutover orchestration higher still.
| Capability Domain | Weight | What to Evaluate |
|---|---|---|
| Discovery, Dependency Mapping & Assessment | 25% | Agentless and agent-based discovery across VMware, Hyper-V, physical, and other clouds; automatic application-affinity and network-dependency mapping; right-sizing and cost modeling; six R’s path recommendations and anti-pattern reports before any workload moves |
| Migration Execution & Cutover | 25% | Continuous block- or byte-level replication, achievable RPO/RTO at cutover, non-disruptive test cutover and rollback, wave planning and orchestration at scale, and minimal source-side performance impact during replication |
| Source & Destination Coverage | 20% | Breadth of supported sources (vSphere, Hyper-V, physical, EC2/other clouds) and targets; single-cloud-native vs. any-to-any multicloud reach; database and OS support; and explicit VMware-exit paths to cloud, hyperscaler VMware services, or private-cloud landing zones |
| Modernization & Refactoring Support | 15% | Replatform automations (managed databases, containers, app-service tiers), AI-assisted code and schema refactoring, mainframe/COBOL modernization where relevant, and how far the tool goes beyond rehost toward genuine cloud-native targets |
| Security, Compliance & Governance | 10% | Encryption of replication in transit and at rest, RBAC and SSO on the migration console, audit logging of every cutover, customer-managed keys on target disks, and landing-zone guardrails for regulated workloads |
| Cost, Licensing & Operating Model | 5% | Free-with-the-cloud vs. per-server/per-license vs. subscription economics, whether assessment is a separate paid product, professional-services dependence, and the post-migration FinOps story for the workloads you just landed |
Vendor Landscape
The market splits into three camps that most shortlists end up comparing across, not within. First, the hyperscaler-native suites — AWS, Azure, and Google — which are free or low-cost, deeply integrated, and deliberately one-way toward their own cloud. Second, third-party any-to-any movers — Zerto and OpenText Migrate — that replicate across any source and target and earn their keep on multicloud and cloud-to-cloud work. Third, assessment-first specialists — Device42 and Flexera/Cloudamize — that do the discovery, dependency mapping, and business case the movers assume you already have. VMware HCX sits apart as the tool for keeping workloads on vSphere while relocating them — the path many take to stay on VMware even as Broadcom pricing pushes others off it.
Strengths: End-to-end AWS-native journey: Application Discovery Service and Migration Hub Strategy Recommendations for assessment and six R’s planning, MGN (the successor to CloudEndure) for continuous block-level rehost, and AWS Transform — the agentic-AI experience launched in 2025 — orchestrating the workflow and refactoring mainframe COBOL/JCL/CICS. Broadest source support and the largest migration partner ecosystem. Considerations: Strongly one-way toward AWS; little reason to use it for any other destination. Migration Hub closed to new customers in November 2025, with AWS Transform as the successor, so the classic console is sunsetting. Deep modernization still leans on partners and AWS Mainframe Modernization for the hardest workloads.
Strengths: Free, broad, and well-integrated: agentless discovery and multi-server dependency mapping across VMware, Hyper-V, physical, and other clouds, with SQL Server and web-app assessment built in, plus agentless replication to Azure VMs. Wave planning and a Copilot-based migration agent (2026) add AI-guided path recommendations. The natural exit for Windows- and SQL-heavy estates and Azure VMware Solution. Considerations: Targets Azure only. Agentless dependency analysis and newer wave-planning features have rolled out in stages and some capabilities trail the classic experience. Heterogeneous Linux and exotic legacy workloads get less depth than the Microsoft-stack core.
Strengths: A unified hub for discovery, the mFit fit-assessment scoring, TCO and pricing estimates, and Migrate to Virtual Machines for the actual move — with discovery that now ingests AWS and Azure VM inventory and tags for cross-cloud visibility. License-cost optimization (for example, disabling SMT for Windows/SQL) and clean right-sizing make the business case data-driven. Considerations: Smallest of the three native ecosystems and partner networks, and oriented to Google Cloud as the destination. Best suited where GCP is the target or a serious contender; less compelling as a neutral assessment tool for non-Google landings.
Strengths: The standard for moving live vSphere (and many non-vSphere) VMs between data centers and clouds without reboot, via an automatically created hybrid interconnect — large-scale bulk and vMotion-style migrations with minimal disruption. Now packaged as VCF Operations Workload Mobility and the path of choice for landing on hyperscaler VMware services (AVS, GCVE, VMware Cloud on AWS) to stay on vSphere. Considerations: Keeps you on the VMware stack — which, post-Broadcom, means the subscription bundles and pricing that are driving many estates to leave in the first place. It is mobility, not modernization: it relocates VMs, it does not refactor or re-platform them. Value is tied to remaining a VCF customer.
Strengths: Continuous data protection and journaling deliver near-zero-RPO migration and DR to, from, and within any cloud — AWS, Azure, Google, IBM — plus on-prem, with non-disruptive test cutover and rapid rollback in a few clicks. Software-only, hardware-agnostic, and increasingly positioned for the VMware exit with live VMware-to-HPE VM Essentials migration in recent releases. Considerations: Heritage and much of the value sit in DR and continuous protection; pure one-off rehosts to a single chosen cloud may be served free by that cloud’s native tool. Licensing is per-workload and oriented to ongoing protection, so the economics favor estates that also want DR, not a one-time move.
Strengths: Real-time, byte-level replication migrates entire systems — files, applications, configurations, and permissions — across any combination of physical, virtual, and cloud, to or from AWS, Azure, and Google. Cutovers typically complete in minutes with non-disruptive testing and easy rollback, and the workflow is the same regardless of source or destination platform. Considerations: A focused migration and availability tool rather than a broad assessment or modernization suite, so pair it with separate discovery and planning. Brand has moved through Double-Take to Carbonite to OpenText; confirm current product naming and support. It rehosts faithfully — it does not modernize or refactor.
Strengths: A leader in agentless IT discovery, service mapping, and application-dependency mapping — the assessment layer migrations live or die on. Continuously inventories the estate, surfaces application affinities and communication paths, and feeds defensible move-group and wave planning. Now part of Freshworks, extending into unified ITAM/ITSM. Considerations: An assessment and CMDB tool, not a migration engine — it tells you what to move and with what, then hands off to a mover. Realizing full value depends on accurate, broad discovery coverage and ongoing data hygiene. Plan for a separate execution toolchain.
Strengths: Vendor-agnostic assessment and business case: Cloudamize performs automated discovery, analyzes utilization and dependencies, and models detailed TCO and right-sizing across AWS, Azure, and Google so you can pick the best-fit destination on data, not vibes. Flexera One ties migration planning to license optimization and ongoing cloud-cost and SaaS governance. Considerations: Planning, costing, and license intelligence — not an execution mover; you migrate with the native or third-party tools after. Strongest as a cross-cloud comparison and FinOps layer, and most valuable to organizations already invested in Flexera’s ITAM and cloud-cost platform.
Pricing Models & Cost Structure
Migration pricing forks sharply by camp. The hyperscaler-native engines are free or nominal — you pay for the target cloud resources, not the mover — which is the whole point of a one-way tool. Third-party movers and assessment specialists charge per server, per workload, or by subscription, and assessment is often a separate product line. Model the cost against the size of the wave and the destination resources, and remember the largest line is usually the target cloud run-rate, not the tool.
| Vendor | Pricing Model | Relative Tier | Key Cost Drivers |
|---|---|---|---|
| AWS (Transform & MGN) | MGN free for a staging window; AWS Transform/Discovery low-cost; pay for target | Lower (tool) / target-driven | Target EC2/EBS run-rate, replication egress and staging, extended-use beyond the free window, partner services for refactor |
| Azure Migrate | Free assessment & agentless replication; pay for Azure target | Lower (tool) / target-driven | Target Azure compute/storage, replication data, third-party offers used within Migrate, Azure VMware Solution capacity |
| Google Migration Center | Free discovery, assessment & Migrate to VMs; pay for GCP target | Lower (tool) / target-driven | Target Compute Engine/storage, egress during replication, license-optimization choices (SMT), data volume migrated |
| VMware HCX (Broadcom) | Bundled within VCF / VVF subscription | Premium (via VCF) | VCF/VVF subscription core count and bundle tier, target hyperscaler VMware service capacity, ongoing vSphere licensing |
| Zerto (HPE) | Per-workload subscription (migration & DR) | Moderate | Protected/migrated workload count, journal retention, multicloud targets, whether ongoing DR is in scope |
| OpenText Migrate | Per-server / per-target license (term or migration-window) | Moderate | Number of source servers, concurrency, OS/platform mix, migration-window vs. perpetual licensing |
| Device42 | Subscription by managed devices / resources discovered | Moderate | Device and resource counts under discovery, edition, integration scope, retention of dependency data |
| Flexera (Cloudamize) | Subscription; assessment + Flexera One platform modules | Moderate–Premium | Estate size assessed, modules (migration planning, ITAM, cloud cost), assessment duration, platform footprint |
Implementation & Migration
Sequence the program by the migration journey, not by what is easiest to replicate. Discover and decide the R for each application first; move the simple rehosts in early waves to build muscle; save the refactors and the mainframe for last. If a Broadcom VMware renewal is the trigger, work backward from that date and protect the most entangled tier-1 systems with continuous replication.
Run agentless discovery across the estate and build the dependency map (Device42, Flexera/Cloudamize, or the native suite). Assign each application a disposition from the six R’s, model TCO and right-sizing per destination, and decide the landing zone — one cloud, multicloud, hyperscaler VMware service, or private-cloud exit — against any VMware renewal deadline.
Group applications into migration waves by dependency affinity, stand up landing-zone guardrails (identity, networking, encryption, FinOps tagging), select the mover per wave, and validate replication with a low-risk pilot. Lock cutover runbooks and rollback criteria before any production move.
Replicate continuously and execute non-disruptive test cutovers wave by wave, starting with straightforward rehosts and replatforms. For tier-1 systems use journal-based replication to keep the cutover window to minutes, verify application consistency post-move, and keep rollback live until each wave is signed off.
Tackle the refactors and mainframe modernization left for last, right-size and reserve target resources, decommission the vacated VMware and data-center footprint, and stand up ongoing FinOps so the cloud bill reflects the optimization the move was supposed to buy — not just a relocated data center.
Selection Checklist & RFP Questions
Use this checklist during evaluation to ensure each shortlisted platform covers what actually decides a migration — and, for most buyers right now, a clean exit from VMware.