JOURNEY 03 · VMWARE EXIT

Escape the VMware pullwith FluidCloud.

WHY VMWARE EXITS STALL

It is not a VMmigration problem.It is a network and identityproblem.

Broadcom changed the cost of VMware. The real blockers to an exit are NSX policies, IAM bindings, DR runbooks, backups and application dependencies.

FluidCloud maps all of them in one live dependency graph. Then you can compare destinations, plan the waves and go into the renewal with real options.

01 · Inventory60 machines in a flat list.

VMs
60
Dependencies
0
Waves planned
0/5
IdentityWave 1 · foundation ✓Shared svcsPaymentsWave 2 ✓CRMWave 3 ✓AnalyticsWave 4 ✓PortalWave 5 ✓
HOW IT WORKS

From live VMwareestate to a runningdestination, in two weeks.

FluidCloud software works with a forward-deployed engineer. In week one, we map and plan your exit. In week two, we clone and cut over with your team.

Week 01 · Map and plan

  1. 01DiscoverDay 1

    Map the live VMware estate.

    An engineer connects with read-only access. FluidCloud maps the VMs, hosts, storage, NSX, IAM and all dependencies into one live graph.

    Owner FluidCloud

    Outputs

    • Estate inventory and dependency graph
    • Hidden blockers shown
  2. 02ClassifyDay 2

    Select the exit path for each workload.

    The assessment report puts each workload into one path: rehost, relocate, refactor, retire or hold. It uses criticality, dependencies and risk.

    Owner FluidCloud

    Outputs

    • A path for each workload
    • A risk score for each workload
  3. 03CompareDay 3

    Score each destination side by side.

    Each destination gets a score against the same estate model: Azure VMware Solution, AWS EVS, Nutanix AHV and NC2, and public cloud.

    Owner FluidCloud and your team

    Outputs

    • Destination scores, side by side
    • A stronger position for the renewal
  4. 04PlanDays 4–5

    Make the migration wave plan.

    Our engineers and your team make the wave plan from the assessment report. It has the landing zone, the cutover order and a known-good capture for each wave.

    Owner FluidCloud and your team

    Outputs

    • Wave plan
    • Cutover checklist

Week 02 · Clone and cut over

  1. 05Clone & cut overWeek 2 · done by day 14

    Clone each wave. Validate it. Cut over.

    FluidCloud clones each wave into the destination. Your team validates it before cutover, then updates the endpoints and runbooks.

    Owner FluidCloud and your team

    Outputs

    • Running destination environment
    • Source unchanged until sign-off
VMWARE MIGRATION DESTINATIONS COMPARED

Five destinations,one estate model.Compared in parallel.

We score each destination against the same estate model. You choose with evidence, not with a sales pitch from a vendor.

Scoring · estate prod-vsphere-01 · 0–100 · higher is better on every axisversioned graph · rev 3.0

DestinationFit
  1. Nutanix Cloud ClustersNC2 on AWS · VM-centric

    68 / 100

    80 / 100

    85 / 100

    66 / 100

    58 / 100

    71.4Best fit for this estate

  2. Azure VMware SolutionAVS · continuity first

    55 / 100

    75 / 100

    82 / 100

    78 / 100

    65 / 100

    71.0Eligible

  3. Nutanix AHVOn-prem · HCI continuity

    78 / 100

    70 / 100

    78 / 100

    62 / 100

    55 / 100

    68.6Eligible

  4. AWS EVS / EC2 hybridEVS · ready for a split estate

    62 / 100

    78 / 100

    70 / 100

    72 / 100

    60 / 100

    68.4Eligible

  5. Public cloud-nativeAWS · Azure · GCP · modernization first

    82 / 100

    85 / 100

    45 / 100

    58 / 100

    42 / 100

    62.4Eligible

Fit = average of the selected axes · select an axis to remove itExample scores for a sample estate · your results depend on your estate

FREQUENTLY ASKED

Questionstechnical buyersask.

Direct answers. No claims that we cannot prove.

01Our documentation is weak. Is that a problem?

No. FluidCloud reads the live VMware estate, not your documentation. It finds every VM, host, NSX policy, IAM binding and dependency. The data inside each VM moves with its disks.

02How is FluidCloud different from AWS Transform, Nutanix Move or HCX?

Each of those tools works for one destination. FluidCloud maps the full estate and scores all destinations side by side. Then it clones the environment, with its network, identity and dependencies, into the destination that you select.

03Which destinations does FluidCloud support?

Azure VMware Solution, AWS EVS, Nutanix NC2 and AHV, and public cloud on AWS, Azure and GCP. FluidCloud scores all of them against the same estate model.

04How long does a VMware exit take?

Discovery runs on day one. Destination scores are ready on day three, and the wave plan at the end of week one. The full exit takes two weeks.

05What access does FluidCloud need?New

One read-only role for discovery. No agents and no installation. Cutover uses limited permissions that you approve.

06Is FluidCloud a Terraform or IaC tool?New

No. FluidCloud is a Cloud Cloning™ platform. It builds your running environment again in the destination, with its network, identity and dependencies. Terraform is one output, so your team owns the estate as code.

07Can we use FluidCloud before we decide to exit?

Yes. Many teams start before they decide. An exit-readiness report gives you a stronger position in the renewal talks, even if the migration happens later.

YOUR MOVE

Ready to exit VMware?

Connect one environment with read-only access. We map the estate and give you a destination comparison and a wave plan before your renewal date.

Read-only · No agents · SOC 2 Type II