VMware to Nutanix Migration: Move Tool Playbook | NutaNIX

/nix/nutanix/10-migration-path

Module 10: Migration Path (The Customer-Running Playbook)

36 min readNCA ~5%NCP-MCI ~10%NCM-MCI ~5%
Cert coverage NCA (
5%) · NCP-MCI (10%, Move and migration concepts) · NCM-MCI (5%)
This is the synthesis module. Modules 1-9 give you the technical and economic depth. This module is what BlueAlly SAs actually do for 12-18 months: lead the customer's migration from VMware to Nutanix.

Prerequisites

Key terms

Move
Pilot wave
Production wave
Cutover
Parallel-running
Hybrid steady-state
Risk register
Dependency mapping
Application affinity group
Validation criteria
Rollback plan
Decommissioning

The Promise

By the end of this module you will:

  1. Run a 12-18 month customer migration engagement end to end. Discovery, dependency mapping, platform build, pilot wave, production waves, cutover, decommissioning. The shape is consistent across customers; the specifics vary. You should be able to walk into a customer kickoff and lead the conversation.
  2. Use Move (the Nutanix migration tool) confidently. What it migrates, what it doesn't, what to plan for, what tends to require manual cleanup.
  3. Sequence migrations by risk, not by convenience. Pilot first (low-risk, internal), then low-tier production, then Tier-1, then mission-critical. Many customer projects fail because they invert this sequence; BlueAlly SAs lead customers to the right order.
  4. Design the hybrid steady-state honestly. Some workloads will stay on VMware for legitimate reasons (NSX-T routing complexity, NetApp ONTAP-specific workflows, SRM-orchestrated complex DR, third-party-vendor dependencies). The right answer for many customers is hybrid permanently. Position this as a successful outcome, not a failure.
  5. Communicate with executives, IT teams, and end users at the right level for each. Migration is as much a communication exercise as a technical one. The cadence and framing differ for each audience; you should know all three.
  6. Maintain a working risk register and act on it. Migrations have predictable risks (dependency surprises, application performance regressions, network reconfiguration issues, team capacity constraints). The risk register is how you stay ahead of them.
  7. Know what year-2 stable state looks like and have the conversation about BlueAlly's continuing role: managed services, upgrades, expansion, periodic optimization. Migrations end; relationships continue.

This is the final module. After this, the curriculum hands you the appendices. The technical and commercial depth is in your hands. What remains is the engagement skill, which this module gives you a framework for.

Foundation: What You Already Know

You have done migrations. Maybe vCenter version upgrades. Maybe storage-array swaps with Storage vMotion. Maybe a datacenter consolidation with cross-site moves. Possibly a hypervisor migration (Hyper-V to ESXi, or vice versa). You know the patterns:

You also know what the VMware-to-Nutanix migration is not:

The migration tool is Move. The framework is the phased-wave approach. The discipline is sequencing by risk. The communication is to multiple audiences with different framings. Hold all of those in mind.

Core Content

Move: The Migration Tool

Move is Nutanix's cross-platform VM migration tool. It supports several source-to-target paths:

The architecture:

What Move handles automatically:

What requires manual handling:

The 7-Phase Migration Framework

Successful migrations follow a phased structure. Each phase has clear entry and exit criteria.

Phase 0: Discovery and Dependency Mapping (4-8 weeks)

Inventory everything. Map dependencies. Classify workloads by risk and tier. Identify integration points (AD, network, monitoring, backup, DNS, load balancers, ITSM).

Deliverables:

Common discovery techniques: active discovery tools (Nutanix's discovery utility, Lansweeper, RVTools for VMware), Application Performance Monitoring data, workshops with application owners, network flow analysis. This phase often takes longer than expected. Budget aggressively.

Phase 1: Platform Build and Validation (4-6 weeks)

Deploy the Nutanix cluster. Validate it. Integrate with customer's environment.

Deliverables: Nutanix cluster deployed and validated against POC criteria; AD / SAML / SSO integration; network integration (VLANs, routing, firewalls); backup integration (Veeam / Commvault / Rubrik against Nutanix Objects or vendor-specific); monitoring integration (Prism Central forwarding to customer's SIEM, ITSM); DR site configured if applicable; categories defined (from Module 4, drives policies in subsequent waves).

Phase 2: Pilot Wave (4-8 weeks)

Migrate 5-20 low-risk VMs. Validate the migration tooling, process, and team capacity. This is where theory meets reality.

Pilot VM selection criteria:

Pilot wave establishes: Move tool installation and operation in the customer's environment; network mapping table (source port group to target virtual network); cutover runbook; communication template; rollback procedures (validated, not theoretical); the customer's team's hands-on familiarity with the new platform.

Phase 3: Production Wave 1 (Low-Tier, 8-16 weeks)

50-200 VMs. Dev/test/UAT environments. General-purpose Tier-3 production. Web tiers behind load balancers (with redundancy that absorbs cutover blips).

This wave is where you scale the team's capacity and validate the operational rhythm. By the end: the customer's team can do migrations without BlueAlly hand-holding; the runbook is mature; common issues are identified and have known mitigations; confidence is built for the next tier.

Phase 4: Production Wave 2 (Tier-1, 12-20 weeks)

200-600 VMs typically. Tier-1 production: customer-facing applications, internal-critical applications, databases (with care), core business workflows.

Tier-1 migrations require: application-owner coordination per migration batch; clear validation criteria per application; rollback plans validated per application; cutover scheduled in maintenance windows; application-aware migration patterns (for SQL Server, use Always On to minimize downtime; for Oracle, planned-failover patterns; for clustered apps, failover to standby, migrate primary, fail back).

Phase 5: Production Wave 3 (Mission-Critical, 8-16 weeks)

The remaining workloads: Tier-0 mission-critical, often with zero-downtime requirements, complex application dependencies, regulated workloads, integration-intensive systems.

Often this wave includes workloads that genuinely require Metro Availability or NearSync (Module 7), mission-critical applications with regulatory compliance constraints, applications with complex external integrations, and workloads that may stay on VMware permanently if business case justifies (the hybrid steady-state question). This wave gets the most engineering scrutiny per workload. Per-VM time investment is highest.

Phase 6: Stabilization, Decommissioning, and Steady-State (4-8 weeks)

Decommission old VMware infrastructure (or formalize the hybrid steady-state). Hand off operational ownership to customer team. Document final state. Conduct retrospective.

Deliverables: decommissioning plan executed (physical removal, contract termination, asset disposal); hybrid steady-state documentation if applicable; final BoM reconciliation; operational runbook handed off; retrospective with all stakeholders; BlueAlly's continuing role defined (managed services, upgrades, future expansion).

The Cycle, Frame Two: Migration as Phased Risk Management

For a customer's IT operations leader, the durable migration frame is risk management. Each phase has a specific risk being reduced.

Phase Primary Risk Reduced
Phase 0: Discovery "We don't actually know what we have."
Phase 1: Platform Build "The new platform doesn't fit our environment."
Phase 2: Pilot "We don't know what we don't know about migrating."
Phase 3: Wave 1 "We can't migrate at scale."
Phase 4: Wave 2 "Tier-1 workloads might break in ways we can't predict."
Phase 5: Wave 3 "Mission-critical workloads have unique constraints."
Phase 6: Stabilization "We never finish; the project never ends."

Frame each phase as risk reduction. Customers who think in risk-management terms (which is most operations leaders) respond to this framing. The migration is not about VM movement; it's about systematically reducing risk.

The Cycle, Frame Three: Migration as the SA's 12-18 Month Engagement

For BlueAlly, the migration is the engagement. The shape:

The SA's role evolves from technical leader (early) to coach (middle) to specialist consultant (late) to relationship maintainer (after). Recognize the role shift. The customer's team's growing competence is a sign of success, not a threat to your engagement.

The Cycle, Frame Four: Migration as Platform Consolidation

For an executive sponsor (CIO, CTO, sometimes CFO), the durable frame is platform consolidation. The migration is one part of a broader simplification.

What Customer Has Today What Customer Has Year-2 Stable State
3-4 separate storage tiers (filer, object, iSCSI, dedup) 1 unified-storage cluster
4-6 management products (vCenter, Aria Operations, Aria Automation, vSphere LCM, etc.) Prism Central
2-3 networking products (vSS/vDS, NSX-T, third-party security) Prism + Flow + select third-party
Multiple refresh cycles Aligned to cluster refresh
Multiple support contracts 1-2 (Nutanix + hardware OEM)
Multiple vendor relationships Consolidated to 2-3

Frame the migration as consolidation, not as VM movement. Executive sponsors care about portfolio simplification, not about Move tool mechanics.

Hybrid Steady-State: The Permanent Coexistence

Some workloads will not migrate. Legitimate reasons:

Hybrid steady-state is not a project failure. It is often the right architectural answer. The customer migrates the bulk (often 70-90%) to Nutanix, captures most of the consolidation value, and accepts permanent coexistence for the remaining workloads.

Risk Register: The Predictable Migration Risks

A working risk register tracks identified risks, mitigations, and ownership. Common risks across migrations:

Technical risks:

Operational risks:

Commercial risks:

Relationship risks:

The risk register is reviewed weekly with the customer's project lead and monthly with the executive sponsor. New risks are added as discovered. Closed risks are documented. The register is a living document.

Communication Playbook by Audience

Migrations have multiple audiences, each with different information needs and frequencies.

Year-2 Stable State and the Continuing Relationship

Migrations end. The customer's environment stabilizes. What does year 2 look like and what is BlueAlly's continuing role?

Customer's year-2 reality: the Nutanix cluster is the operational platform; the customer's team is competent at routine operations; periodic upgrades (LCM-driven) happen on a quarterly or semi-annual cadence; capacity planning is part of routine work; hybrid steady-state (if applicable) is being managed; the original BoM and TCO assumptions are tracking (or they aren't, and there are conversations about why).

BlueAlly's continuing role options:

The continuing relationship matters commercially (recurring revenue) and reputationally (reference customers, peer referrals). Plan for it from the beginning of the engagement.