01
·
SOLUTIONS / VMWARE EXIT
Don't fall off
the renewal cliff
ABSTRACT
02
·
FLUIDCLOUD THESIS
You don't have a VM migration problem. You have a Network & Identity conversion problem.
Broadcom changed the economics of VMware. But the deeper issue is that most enterprises do not yet know what it would actually take to leave. The VM inventory is only the visible layer. The real blockers live in NSX policies, IAM bindings, DR runbooks, backup topology, monitoring rules, compliance workflows, shared services, and app-to-app dependencies.
FluidCloud reads that operating environment as a live graph — every resource, every relationship, every dependency — so infrastructure leaders can compare destinations, build credible migration waves, and walk into the renewal decision with real options.
the toughest part of Migrating from vmware
The tough and overlooked part is migrating network security. FluidCloud’s cloud cloning technology solves this problem by allowing you to easily clone your NSX-T policies to Nutanix Flow, ensuring your workloads are protected as soon as they are migrated, accelerating the entire migration process.
David Quinney
Global Practice Lead - Infrastructure & Professional Services at nutanix
03
·
THE SHAPE OF AN EXIT
Most VMware exits become incidents. Here's why.
Renewal pressure forces a decision before the estate is mapped. The VMs move. The dependencies don't. Day 1 of cutover, the pager starts ringing — that's not a migration; that's an incident with a project plan. The five incidents below are the five places exits actually fail. Each is preventable. None are predictable from a VM list alone.
TREATMENT
FluidCloud converts your entire VMware estate, delivering portability scores and remediations across 8 cloud providers. Our proprietary CloudCloning approach enables highly accelerated and safe cutoffs, preventing incidents.
Field guide
The five hardest problems exiting VMware, and how to overcome them.
Most exits fail because teams solve the wrong problems first. This guide names the real roadblocks behind the five incidents above and lays out the strategies enterprises use to clear each one without disrupting production.
04
·
WHAT FLUIDCLOUD CAPTURES BEYOND VMS
A VM can be moved and still not be operational.
FluidCloud captures the surrounding context that determines whether a workload can actually run, recover, comply, and be operated in its next environment.
Instant discovery with FluidCloud using a read-only permission create a graph that automatically captures every resource, dependency, networking, cost, policies, and more. This graph provides instant assessment of portability and costs across all available exit options. The Migrate and Recover operations run against this same graph.
01 · VM & WORKLOAD
12,847 resources
VM definitions, clusters, templates, boot order.
vm_definitions
12,847
clusters_hosts
86 · 9 sites
templates_images
412
boot_groups
38
VMS
HOST
TMPL
BOOT
02 · NETWORK FABRIC
1,284 policies
Segments, edges, switches, routing assumptions, firewalls.
segments
412
edges_gateways
14 · 2 misrouted
load_balancers
38
peering_transit
24 · vendor-bound
SEG
EDGE
FW
LB
03 · IDENTITY & SECURITY
3,021 principals
Directory bindings, role grants, certificates, trust.
directory_binds
primary + federated
role_grants
47 · 9 over-scoped
service_accounts
318
cert_authorities
5 · 1 expiring
DIR
IDP
ROLE
CERT
04 · RESILIENCE & COMPLIANCE
26 plans
Replication, recovery, audit workflow, and evidence chain.
recovery_plans
26 · 3 untested
backup_topology
184 protected groups
audit_workflows
PCI · HIPAA · SOC2
recovery_books
41
RPLC
BKUP
RECV
AUD
05 · MONITORING & TOOLING
640 rules
Dashboards, alerts, scripts,
scheduled jobs.
dashboards
78
alert_rules
640
scripts_cron
112 · 8 orphaned
capacity_assumes
vendor-bound
DASH
ALRT
CRON
LOG
06 · MIGRATION CONTROL
5 waves
Dependency graph, classification, scoring, gates.
dep_graph_nodes
412 surfaced
path_class
rehost · relocate · refactor
dest_scores
6 destinations · 5 axes
validation_gates
5 · signed snapshots
GRPH
CLSF
SCOR
GATE
Representative scan output · figures illustrative of a mid-size estate
Migrating virtual machines from VMware to Nutanix AHV is easy.
One distinct advantage of Fluidcloud is the fact it can clone the configuration of a VMware Environment to Nutanix AHV (including NSX to Flow) which otherwise requires a lot of manual work and planning. We were able to transform NSX rulesets to Nutanix constructs which includes subnets, address groups, categories, network security policies, service groups and VPC’s.
David Quinney
Global Practice Lead - Infrastructure & Professional Services at nutanix
05
·
HOW THE PRODUCT WORKS
From live VMware estate to operational in new destination, in two weeks.
FluidCloud is offers a productized workflow delivered by industry-defining software and a forward-deployed engineer. Week one is FluidCloud-led intelligence; week two is wave planning and execution, done jointly with your team.
Discover the live VMware estate.
A FluidCloud forward-deployed engineer connects read-only to the VMware environment. The product inventories VMs, NSX, IAM, DR tooling, monitoring, compliance workflows, and shared services — building a live as-is graph in days, not weeks of documentation review.
OUTPUTS
Classify the right exit path per workload.
The graph drives classification. Workloads sort into rehost / relocate / refactor / retire / hold-for-now buckets based on business criticality, dependency density, and migration risk — not just technical fit. No CMDB archaeology required.
OUTPUTS
Compare destinations in parallel.
All destinations — AVS, AWS EVS, Nutanix AHV, NC2, public-cloud-native, Proxmox / KVM, hybrid split estate — scored against the same estate model. The comparison engine runs in hours, not weeks.
OUTPUTS
Generate the migration wave plan.
FluidCloud generates the full wave plan from the versioned graph and destination decision — landing-zone requirements, cutover sequence, validation gates, rollback logic. What used to take weeks of architecture review now runs in hours against the graph.
OUTPUTS
Update endpoints. Migration complete.
Endpoint updates run on the customer side against the FluidCloud-generated plan: connection strings, IAM bindings, DR pointers, monitoring agents, runbook updates. Internal teams, partners, or FluidCloud-led — the workflow output is the same.
OUTPUTS
RESULT
The output of the workflow is not a deck. It is a versioned operating-environment graph, a scored destination-comparison brief, a wave plan with validated gates, and the negotiating position that comes from understanding your estate before the renewal closes.
06
·
DESTINATION STRATEGY
Different workloads should leave VMware in different ways.
A serious VMware exit program is a strategic decision that creates a path to modernization also. FluidCloud helps teams decide where speed matters, where continuity matters, where modernization is worth it, and where a split-estate strategy is the smartest move.
07
·
COMPARE DESTINATIONS IN PARALLEL
Six destinations, one estate model. Compared in parallel.
Most exits lock destination before they understand the estate. FluidCloud inverts the sequence: the estate model is destination-independent, every path is scored against the same dimensions, and the comparison ships as a scored destination brief the team can act on.
08
·
WHY DESTINATION INDEPENDENCE MATTERS
FluidCloud keeps your cloud options open. Even after the migration.
Point tools are useful after a destination is chosen. FluidCloud matters before that — when teams still need to understand the estate, compare options, and avoid locking into the next vendor before they have real options.
I
REUSABLE ANALYSIS
One model, many destinations.
Do the analysis once and reuse it across AVS, AWS EVS, NC2, Nutanix AHV, cloud-native, Proxmox / KVM, and hybrid paths.
II
Procurement position
Negotiating position.
A credible exit-readiness changes the procurement conversation because alternatives stop being theoretical. With a clear inventory you can let cloud providers compete for your business.
IV
SHARED OPERATING MODEL
Better partner leverage.
FluidCloud gives partners, SIs, CSPs, and internal teams a shared operating model instead of a pile of disconnected assessments.
08
·
PRODUCT + SERVICES MODEL
A productized exit layer, with services where they actually help.
Generic migration programs rebuild discovery, dependency analysis, wave planning, cutover orchestration, and reporting from scratch on every engagement. FluidCloud productizes the repeatable layer and uses services to accelerate adoption, validation, and execution.
The repeatable, productized layer.
Five capabilities that ship as software, not deliverables.
- +FluidCloud Dependency Graph
Captures VM inventory, network fabric, identity assumptions, security boundaries, app dependencies, DR posture, backup topology, and operational workflows.
- +Destination Comparison Engine
Scores exit paths by workload group across cost, compatibility, operational change, migration complexity, and strategic flexibility.
- +Wave Planning Workflow
Creates migration waves using dependency order, business criticality, target readiness, change-window constraints, and validation gates.
- +Validation & Evidence Layer
Produces cutover readiness, rollback posture, operational gaps, and board / procurement-ready exit artifacts.
- +APIs & Partner Execution Layer
Lets internal teams, SIs, CSPs, and partner tooling consume the graph and execute destination-specific migration steps.
Engineering expertise where the product needs hands.
Four offerings — directly from FluidCloud or via certified partners.
- +Assessment facilitation
Help teams connect sources, validate findings, and align stakeholders around the real exit scope.
- +Destination architecture review
Translate product findings into landing-zone, network, security, and operations decisions.
- +Migration factory setup
Configure wave cadence, change-window process, cutover validation, rollback procedures, and partner execution model.
- +Executive & procurement support
Package exit-readiness and destination-comparison outputs into leverage for renewal, board, and vendor conversations.
10
·
YOU'VE BEEN HERE BEFORE
You've likely run migrations before. This isn't going to feel like one of those.
11
·
FREQUENTLY ASKED
Questions technical buyers actually ask.
Treat this as the appendix to the volume. Direct answers, no marketing throat-clearing, no claims we cannot defend.
12
·
YOUR MOVE
Ready to exit VMware?
Talk to our VMware migration team. We will connect read-only to one environment, map the estate as a live graph, and return a destination-comparison brief and wave plan before your renewal window closes.