The Complete VM Migration Checklist (2026 Edition)

VM migration projects fail most often due to inadequate planning, not technical limitations. Whether you are migrating 20 VMs or 2,000, following a structured checklist ensures nothing falls through the cracks. This guide covers every phase of a production VM migration, from initial assessment through post-migration validation.

Phase 1: Pre-Migration Assessment

Before touching a single VM, your team needs a complete picture of what you are working with and where you are going.

Inventory and Discovery

• Generate a complete VM inventory from vCenter, Hyper-V Manager, or your current hypervisor management tool
• Document each VM's resource allocation: vCPUs, memory, disk size, and network configuration
• Identify OS versions and editions for every VM (Windows Server 2016/2019/2022, RHEL 7/8/9, Ubuntu 20.04/22.04, etc.)
• Map network dependencies: VLANs, static IPs, DNS entries, firewall rules, and load balancer configurations
• Identify storage dependencies: shared storage, NFS mounts, iSCSI targets, and local disk layouts
• Catalog installed applications and their licensing requirements on the target platform
• Flag VMs with hardware dependencies: USB passthrough, GPU passthrough, SR-IOV, or TPM requirements

Risk Classification

• Classify each VM by criticality: Tier 1 (mission-critical), Tier 2 (important), Tier 3 (non-critical)
• Identify VMs that require zero-downtime migration vs. those that can tolerate a maintenance window
• Document compliance requirements: HIPAA, PCI-DSS, SOX, FedRAMP, or internal security policies
• Establish rollback criteria: what conditions trigger a rollback, and what is the rollback procedure

Target Environment Preparation

• Provision target hypervisor infrastructure (KVM hosts, Proxmox cluster, or cloud accounts)
• Configure networking on target: bridges, VLANs, DNS, and DHCP
• Set up shared storage if required: Ceph, NFS, or local ZFS pools
• Install and configure HyperSDK on a management node with API access to both source and target environments
• Verify connectivity between source hypervisor, HyperSDK management node, and target infrastructure
• Configure backup strategy for the target environment before migration begins

Phase 2: Pilot Migration

Never go straight to production. A pilot migration with non-critical VMs validates your process and surfaces issues early.

Pilot Execution

• Select 5-10 Tier 3 VMs representing your most common OS and application configurations
• Run a test export using HyperSDK to verify connectivity and credential configuration
• Export and convert each pilot VM, documenting the time required per VM and any errors encountered
• Verify disk image integrity using SHA-256 checksums from the export manifest
• Deploy pilot VMs to the target environment and verify first-boot success
• Test application functionality on each migrated VM: services running, network connectivity, data integrity
• Measure performance baselines: CPU utilization, memory usage, disk I/O, and network throughput
• Compare performance baselines against pre-migration measurements

Pilot Review

• Document any VMs that required manual intervention after migration
• Identify OS-specific issues: driver installation, bootloader configuration, or service startup failures
• Calculate actual migration throughput (GB/hour) to estimate production migration timelines
• Update the migration plan based on pilot findings
• Obtain stakeholder sign-off on pilot results before proceeding to production migration

Phase 3: Production Migration

With pilot results validated, execute the production migration in planned waves.

Wave Planning

• Group VMs into migration waves based on application dependencies and criticality
• Schedule each wave during approved maintenance windows
• Notify application owners and support teams of migration schedules
• Ensure rollback resources are available: source VMs remain running until target validation is complete

Migration Execution

• Execute pre-migration VM snapshots on the source hypervisor as a safety net
• Run HyperSDK export jobs for each wave, monitoring progress through the dashboard
• Verify export manifests: disk checksums, metadata integrity, and conversion status
• Deploy converted VMs to target infrastructure
• Validate first-boot success for each VM (HyperSDK reports this automatically)
• Run application-level health checks immediately after deployment
• Update DNS records, load balancer configurations, and monitoring systems to point to migrated VMs
• Verify backup jobs are running on the target environment for each migrated VM

Phase 4: Post-Migration Validation

The migration is not complete until everything is verified and documented.

Validation Checklist

• Confirm all VMs are running and accessible on the target platform
• Verify application functionality with end-users or application owners
• Compare performance metrics against pre-migration baselines
• Confirm backup and disaster recovery procedures are operational on the target
• Validate monitoring and alerting: all migrated VMs are visible in your monitoring system
• Update CMDB and asset management records with new infrastructure details
• Verify compliance controls: audit logging, access controls, and encryption are configured on the target

Cleanup

• Retain source VM snapshots for a defined rollback period (typically 7-30 days)
• Decommission source VMs after the rollback window expires
• Revoke source hypervisor credentials from HyperSDK once migration is finalized
• Generate a final migration report: VMs migrated, success rate, time elapsed, and cost savings
• Conduct a retrospective with the migration team to document lessons learned

Timeline Guidance

Based on production migrations using HyperSDK:

Deployment Size	Pilot Phase	Production Migration	Total Timeline
20-50 VMs	1 week	1-2 weeks	3-4 weeks
50-200 VMs	1-2 weeks	3-4 weeks	5-6 weeks
200-500 VMs	2 weeks	4-8 weeks	6-10 weeks
500+ VMs	2-3 weeks	8-16 weeks	10-20 weeks

The single most important factor in migration success is thorough pre-migration assessment. Invest the time upfront, and the execution phases will run predictably.