Definitive VMware to Hyper-V Migration Guide: CLI-First Enterprise Strategy

Step 1: Perform Pre-Migration Assessment and Planning

Before any migration work begins, a comprehensive assessment of your existing VMware environment is crucial. This step identifies all virtual machines slated for migration, evaluates their compatibility with Hyper-V, and meticulously plans resource allocation on the target Hyper-V hosts. This phase is about discovery, documentation, and risk mitigation.

# Connect to vCenter Server
Connect-VIServer -Server 'your_vcenter_server_fqdn' -Credential (Get-Credential)

# Get detailed information about all VMs
$VMs = Get-VM | Select-Object Name, PowerState, NumCpu, MemoryGB, ProvisionedSpaceGB, UsedSpaceGB, HardDisks, NetworkAdapters, GuestId, OSFullName, @{N='VMHost';E={$_.VMHost.Name}}

# Export VM details to a CSV for analysis
$VMs | Export-Csv -Path 'C:\MigrationPlan\VMware_VM_Inventory.csv' -NoTypeInformation

# Disconnect from vCenter
Disconnect-VIServer -Server 'your_vcenter_server_fqdn' -Confirm:$false

Connect-VIServer: Establishes a connection to your vCenter Server instance.

Get-VM: Retrieves all virtual machines from the connected vCenter or ESXi host.

Select-Object: Specifies the properties of the VM objects to include, creating custom properties for host information.

Export-Csv: Exports the selected VM data to a CSV file for detailed analysis and planning.

Disconnect-VIServer: Terminates the connection to the vCenter Server.

Portal alternative: Use the vSphere Client to manually gather VM information, including CPU, memory, disk usage, network adapters, and guest OS details. Navigate to 'VMs and Templates', select VMs, and review their 'Summary' and 'Configuration' tabs.

Expected result: A detailed CSV file containing inventory of all VMware VMs, including resource usage, disk configurations, and network settings, which forms the basis for your migration plan. This allows you to identify potential compatibility issues (e.g., old OS versions, specific hardware dependencies) and allocate appropriate resources on Hyper-V.

Step 2: Prepare VMware Virtual Machines for Migration

Optimizing and cleaning up VMware VMs before migration can significantly smooth the transition. This step focuses on snapshot consolidation, uninstalling VMware-specific drivers and tools, and general disk cleanup to reduce disk size and potential conflicts on the target Hyper-V environment.

# Connect to vCenter Server
Connect-VIServer -Server 'your_vcenter_server_fqdn' -Credential (Get-Credential)

# --- Sub-step 2.1: Consolidate Snapshots (CRITICAL) ---
# Get all VMs with snapshots
Get-VM | Get-Snapshot | Select-Object VM, Name, Created | Out-GridView -Title 'VMs with Snapshots'

# For a specific VM, consolidate snapshots
# Replace 'YourVMName' with the actual VM name
Get-VM -Name 'YourVMName' | Remove-Snapshot -RemoveChildren -Confirm:$false

# --- Sub-step 2.2: Uninstall VMware Tools (Inside Guest OS) ---
# This step MUST be performed within the guest OS of each VM.
# RDP/Console into 'YourVMName'
# Open PowerShell as Administrator inside the guest VM:
Write-Host "Please manually uninstall 'VMware Tools' from within the guest OS via 'Add or Remove Programs'."
Write-Host "Reboot the VM after uninstallation."

# --- Sub-step 2.3: General Disk Cleanup (Inside Guest OS) ---
# Run Disk Cleanup (cleanmgr.exe) to remove temporary files.
# Consider defragmenting disks (for non-SSD VMs)
Write-Host "Consider running 'cleanmgr.exe' and disk defragmentation (if applicable) within the guest OS."

# Disconnect from vCenter
Disconnect-VIServer -Server 'your_vcenter_server_fqdn' -Confirm:$false

Get-Snapshot: Identifies existing snapshots, which must be removed before migration.

Remove-Snapshot: Deletes snapshots for a specified VM. `RemoveChildren` ensures all associated child snapshots are removed.

Write-Host: Provides instructions for manual steps to be performed within the guest OS.

Portal alternative: In the vSphere Client, right-click a VM, navigate to 'Snapshot', and select 'Consolidate'. For VMware Tools, log into the guest OS, go to 'Control Panel' -> 'Programs and Features', and uninstall 'VMware Tools'.

Expected result: VMware VMs are free of snapshots, VMware Tools are uninstalled, and guest OS disks are cleaned up. This reduces the disk image size and prevents potential conflicts with Hyper-V drivers post-migration.

Step 3: Prepare the Hyper-V Host Environment

A robust Hyper-V host environment is foundational for successful migration. This step involves installing the Hyper-V role, configuring storage paths, and setting up virtual networks to seamlessly integrate the migrated VMs into their new home.

# --- Sub-step 3.1: Install Hyper-V Role ---
# Run on the target Windows Server where Hyper-V role is not yet installed
Add-WindowsFeature -Name Hyper-V -IncludeManagementTools
Restart-Computer -Force

# --- Sub-step 3.2: Configure Hyper-V Default Storage Paths ---
# It's good practice to dedicate specific storage for VHDX files and VM configurations.
# Create base directories if they don't exist
$VMPath = 'D:\Hyper-V\Virtual Machines'
$VHDXPath = 'D:\Hyper-V\Virtual Hard Disks'
New-Item -Path $VMPath -ItemType Directory -Force
New-Item -Path $VHDXPath -ItemType Directory -Force

# Set the default paths for new VMs and VHDX files
Set-VMHost -Path $VMPath -VirtualHardDiskPath $VHDXPath

# --- Sub-step 3.3: Configure Virtual Networks ---
# Get available physical network adapters
Get-NetAdapter | Select-Object Name, Status, MacAddress | Out-GridView -Title 'Available Network Adapters'

# Create an external virtual switch. Replace 'Ethernet' with your actual physical adapter name.
New-VMSwitch -Name 'External_Switch' -NetAdapterName 'Ethernet' -AllowManagementOS $true

# Verify virtual switch creation
Get-VMSwitch | Select-Object Name, SwitchType, NetAdapterInterfaceDescription

Add-WindowsFeature -Name Hyper-V: Installs the Hyper-V role and its associated management tools.

Restart-Computer -Force: Initiates an immediate reboot, necessary for the Hyper-V role installation to complete.

New-Item -ItemType Directory: Creates the specified directories for VM configuration files and virtual hard disks.

Set-VMHost: Configures default paths for virtual machine files and virtual hard disks on the Hyper-V host.

Get-NetAdapter: Lists all physical network adapters on the host.

New-VMSwitch: Creates a new virtual switch. Use -NetAdapterName to bind it to a physical adapter for external network access. `AllowManagementOS` allows the host OS to share the adapter.

Get-VMSwitch: Verifies the creation and configuration of virtual switches.

Portal alternative: In Server Manager, add the Hyper-V role. After reboot, open Hyper-V Manager, navigate to 'Hyper-V Settings' to configure default paths, and use 'Virtual Switch Manager' to create and configure virtual switches.

Expected result: A fully configured Hyper-V host, ready to receive migrated VMs, with dedicated storage locations and network connectivity established.

Step 4: VM Disk Export and Conversion Strategy (Manual vmdk to vhdx)

This step details the recommended manual approach for exporting VMware VMDK disks and converting them into the Hyper-V VHDX format. This method is highly reliable and provides granular control over the conversion process, ensuring optimal compatibility and performance. It's suitable for small to medium migrations where SCVMM might be overkill.

# --- Sub-step 4.1: Identify the VMDK Path and Copy to Hyper-V Host ---
# Connect to vCenter (if not already connected)
# Connect-VIServer -Server 'your_vcenter_server_fqdn' -Credential (Get-Credential)

# Get the VMDK path for the VM (replace 'YourVMName')
$VM = Get-VM -Name 'YourVMName'
$VMDKPath = $VM.HardDisks[0].ExtensionData.Backing.FileName
Write-Host "VMDK Path for 'YourVMName': $VMDKPath"

# BEFORE COPYING: Power off the VMware VM! This is CRITICAL.
# Once powered off, use SCP/SFTP or direct storage access to copy the .vmdk file
# from the ESXi datastore to a temporary location on your Hyper-V host (e.g., C:\TempVMDK).
Write-Host "Ensure 'YourVMName' is powered off in VMware before proceeding."
Write-Host "Manually copy the VMDK file '$VMDKPath' to 'C:\TempVMDK\YourVMName.vmdk' on the Hyper-V host."

# --- Sub-step 4.2: Convert VMDK to VHDX ---
# Run this on the Hyper-V host where the VMDK was copied.
$SourceVMDK = 'C:\TempVMDK\YourVMName.vmdk'
$DestinationVHDX = 'D:\Hyper-V\Virtual Hard Disks\YourVMName_Disk01.vhdx' # Use the path defined in Step 3

# IMPORTANT: Ensure the VMDK file is not locked by any process.
# Consider using a tool like qemu-img if Convert-VHD has issues with specific VMDK types.
# This example assumes Convert-VHD is sufficient, which it usually is for standard VMDKs.
Convert-VHD -Path $SourceVMDK -DestinationPath $DestinationVHDX -VHDType Dynamic

# For a fixed size disk (recommended for performance for boot drives):
# Convert-VHD -Path $SourceVMDK -DestinationPath $DestinationVHDX -VHDType Fixed

$VMDKPath = $VM.HardDisks[0].ExtensionData.Backing.FileName: Retrieves the absolute path to the primary VMDK file for a given VM.

Write-Host: Provides critical instructions for manual intervention (powering off the VM, copying the VMDK).

Convert-VHD: Converts a virtual hard disk from one format to another (e.g., VMDK to VHDX). This cmdlet is part of the Hyper-V module.

-Path: Specifies the source VMDK file.

-DestinationPath: Specifies the target path and filename for the new VHDX file.

-VHDType Dynamic: Creates a dynamically expanding VHDX. Use -VHDType Fixed for better performance for OS disks.

Portal alternative: Power off the VMware VM in vSphere Client. Copy the VMDK from the datastore. On the Hyper-V host, open Hyper-V Manager, go to 'Action' -> 'Edit Disk...', browse to the VMDK, and follow the wizard to convert it to VHDX.

Expected result: A new VHDX file created in your designated Hyper-V virtual hard disk path, representing the converted VMware VMDK disk, ready to be attached to a new Hyper-V VM.

Step 5: Enterprise V2V with System Center Virtual Machine Manager (SCVMM)

For large-scale enterprise migrations, System Center Virtual Machine Manager (SCVMM) provides an integrated, robust solution for performing V2V (Virtual to Virtual) conversions directly. SCVMM streamlines the migration process by handling disk conversion, VM creation, and initial configuration, making it ideal for environments with numerous VMs and centralized management needs.

# Connect to SCVMM Server
# Ensure SCVMM has been configured to manage both VMware and Hyper-V environments.
# This requires installing SCVMM agents on ESXi hosts and adding vCenter Server to SCVMM.
Connect-SCServer -ComputerName 'your_scvmm_server_fqdn'

# --- Sub-step 5.1: Get Source VMware VM and Target Hyper-V Host ---
$SourceVM = Get-SCVirtualMachine -Name 'YourVMName' -VMMServer 'your_scvmm_server_fqdn'
$TargetHost = Get-SCVMHost -Name 'your_hyperv_host_fqdn' -VMMServer 'your_scvmm_server_fqdn'

# --- Sub-step 5.2: Perform V2V Conversion ---
# This command converts the VMware VM to a Hyper-V VM, placing it on the specified host.
# Specify the path for the VHDX files on the target host's storage.
# Ensure the VMware VM is powered off BEFORE running this command.
New-SCV2V -VM $SourceVM -VMHost $TargetHost -Path "D:\Hyper-V\Virtual Machines" `
          -Name "YourVMName_Migrated" -Description "Migrated from VMware" `
          -RunAsynchronously -JobGroup (New-Guid)

# --- Sub-step 5.3: Monitor the Conversion Job ---
# Get-SCJob | Where-Object { $_.Status -eq 'Running' -and $_.Description -like '*V2V*' }
# Refresh-VMHost -VMHost $TargetHost # Refresh the host in SCVMM after conversion

Connect-SCServer: Connects to the SCVMM management server.

Get-SCVirtualMachine: Retrieves a virtual machine managed by SCVMM (can be VMware or Hyper-V).

Get-SCVMHost: Retrieves a virtual machine host managed by SCVMM (can be ESXi or Hyper-V).

New-SCV2V: Initiates the V2V conversion process. This cmdlet handles powering off the source VM (if configured), converting disks, and creating the new Hyper-V VM.

-VM: Specifies the source VMware virtual machine object.

-VMHost: Specifies the target Hyper-V host where the new VM will reside.

-Path: Defines the storage path on the target Hyper-V host for the VM files.

-Name: Assigns a new name to the migrated Hyper-V virtual machine.

-RunAsynchronously: Executes the command as a background job, allowing you to continue working.

Portal alternative: In the SCVMM Console, navigate to 'VMs and Services'. Right-click the desired VMware VM, select 'Migrate Virtual Machine' -> 'V2V'. Follow the wizard to choose the target Hyper-V host, storage paths, and network settings.

Expected result: The specified VMware VM is converted and recreated as a Hyper-V VM on the target host, with its disks converted to VHDX format. The new VM will appear in Hyper-V Manager and be manageable via SCVMM.

Step 6: Create and Configure Hyper-V Virtual Machines

With your VHDX disks ready (either through manual conversion or SCVMM), this step focuses on creating the new Hyper-V virtual machine shell and attaching the converted VHDX disks. You'll also configure essential resources like CPU, memory, and network adapters.

# Run this on the Hyper-V host.

# --- Sub-step 6.1: Create a New Hyper-V Virtual Machine ---
# Choose Generation 1 for older OS (Windows Server 2003/XP), Generation 2 for modern OS (Windows Server 2012+ / Windows 8+).
# Use the VM path defined in Step 3.
$VMName = 'YourVMName_Migrated'
$VHDXFilePath = 'D:\Hyper-V\Virtual Hard Disks\YourVMName_Disk01.vhdx' # Path from Step 4 or 5
$MemoryStartupGB = 4
$ProcessorCount = 2

New-VM -Name $VMName -MemoryStartupBytes ($MemoryStartupGB * 1GB) -Generation 2 `
       -NewVHDPath $null -SwitchName 'External_Switch' -Path 'D:\Hyper-V\Virtual Machines'

# --- Sub-step 6.2: Attach the Converted VHDX Disk ---
# Remove the empty VHD created by New-VM by default if -NewVHDPath is not null
# If -NewVHDPath $null was used, there might not be a disk to remove.
# For simplicity and clarity, we assume a new VM without an attached disk.
Add-VMHardDiskDrive -VMName $VMName -Path $VHDXFilePath -ControllerType SCSI -ControllerNumber 0 -ControllerLocation 0

# --- Sub-step 6.3: Configure CPU and other settings ---
Set-VMProcessor -VMName $VMName -Count $ProcessorCount
Set-VMMemory -VMName $VMName -StartupBytes ($MemoryStartupGB * 1GB) -MinimumBytes 512MB -MaximumBytes ($MemoryStartupGB * 2GB) -DynamicMemoryEnabled $true

# Set boot order (e.g., to boot from the attached VHDX)
Set-VMFirmware -VMName $VMName -FirstBootDevice (Get-VMHardDiskDrive -VMName $VMName)

# --- Sub-step 6.4: Power On the VM for the First Time ---
Start-VM -Name $VMName

New-VM: Creates a new virtual machine. -Generation 2 is recommended for modern OS, offering UEFI boot and other features. -NewVHDPath $null prevents creating a default empty VHDX. -SwitchName connects it to the virtual network.

Add-VMHardDiskDrive: Attaches an existing virtual hard disk (your converted VHDX) to the VM. -ControllerType SCSI is generally preferred for Generation 2 VMs for hot-add capabilities.

Set-VMProcessor: Configures the number of virtual processors for the VM.

Set-VMMemory: Adjusts memory settings, including dynamic memory, which allows Hyper-V to dynamically allocate RAM based on VM needs.

Set-VMFirmware: Configures UEFI/BIOS settings, including boot order. Essential for ensuring the VM boots from the correct disk.

Start-VM: Powers on the newly created virtual machine.

Portal alternative: In Hyper-V Manager, click 'Action' -> 'New' -> 'Virtual Machine...'. Follow the wizard to specify VM name, generation, memory, and network. On the 'Connect Virtual Hard Disk' page, select 'Use an existing virtual hard disk' and browse to your VHDX file. After creation, adjust CPU and memory settings in the VM's 'Settings'.

Expected result: A new Hyper-V VM created, with the converted VHDX attached, configured with initial CPU and memory resources, and successfully booted into its operating system.

Step 7: Post-Migration Hardening and Optimization

After the initial boot, several critical steps are needed to ensure the migrated VM performs optimally and securely on Hyper-V. This includes installing Hyper-V Integration Services, configuring network settings within the guest OS, and applying performance and security optimizations.

# --- Sub-step 7.1: Install Hyper-V Integration Services (Inside Guest OS) ---
# For Windows Server 2012 R2 and newer, Integration Services are built-in and auto-updated via Windows Update.
# For older OS or if services are missing, you might need to manually install.
# Mount the Integration Services ISO
Mount-VMHostAssignableDevice -VMName 'YourVMName_Migrated' -HostDevice 'C:\Windows\System32\vmguest.iso' # Path to built-in ISO

# Instruct user to manually install within guest OS
Write-Host "Log into 'YourVMName_Migrated' via Hyper-V Manager Console."
Write-Host "Open File Explorer, find the mounted Integration Services disk (D: or E: drive)."
Write-Host "Run 'setup.exe' or 'Install-VMIntegrationServices.ps1' (for newer OS) to install or update."
Write-Host "Reboot the guest VM after installation."

# --- Sub-step 7.2: Verify Integration Services Status (On Hyper-V Host) ---
Get-VMIntegrationService -VMName 'YourVMName_Migrated' | Format-Table Name, Enabled, PrimaryStatus

# --- Sub-step 7.3: Configure Network Settings (Inside Guest OS) ---
# After integration services, the network adapter will be properly recognized.
# RDP/Console into the VM and verify/configure IP addressing.
Write-Host "Verify network connectivity and IP configuration within the guest OS. Use 'ipconfig /all'."
Write-Host "Reconfigure static IP addresses, DNS servers, and gateways if necessary."

# Example for configuring static IP inside the guest (if no DHCP is desired):
# Run this inside the guest VM (requires elevated privileges):
# New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress "192.168.1.100" -PrefixLength 24 -DefaultGateway "192.168.1.1"
# Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses "8.8.8.8","8.8.4.4"

# --- Sub-step 7.4: Remove Legacy Hardware (Inside Guest OS) ---
# Open Device Manager and remove any "ghost" VMware network adapters or SCSI controllers.
Write-Host "In Device Manager within the guest OS, show hidden devices and remove any non-present VMware hardware."

# --- Sub-step 7.5: Hyper-V Specific Optimizations (On Hyper-V Host) ---
# Enable Production Checkpoints (recommended over standard snapshots)
Set-VM -Name 'YourVMName_Migrated' -AutomaticCheckpointEnabled $true -CheckpointType Production

# For Gen 2 VMs, consider disabling Secure Boot if applications require it (rare, but possible)
# Set-VMFirmware -VMName 'YourVMName_Migrated' -EnableSecureBoot $false

# Disconnect the Integration Services ISO
# Dismount-VMHostAssignableDevice -VMName 'YourVMName_Migrated' -HostDevice 'C:\Windows\System32\vmguest.iso'

Mount-VMHostAssignableDevice: Attaches a physical host device (like the Integration Services ISO) to a VM. Note: The path to `vmguest.iso` may vary by Windows Server version.

Get-VMIntegrationService: Verifies the status of individual Hyper-V Integration Services for a VM.

New-NetIPAddress / Set-DnsClientServerAddress: PowerShell cmdlets for configuring network settings directly within the guest OS (if run from within the guest).

Set-VM -CheckpointType Production: Configures the VM to use Production checkpoints, which leverage guest OS snapshot technologies for consistency.

Set-VMFirmware -EnableSecureBoot: Manages the Secure Boot setting for Generation 2 VMs.

Portal alternative: Use Hyper-V Manager to connect to the VM. Within the VM, open 'Device Manager' to clean up old drivers. For network configuration, use 'Network and Sharing Center'. In Hyper-V Manager, for the VM's settings, configure checkpoints and other advanced features.

Expected result: The migrated Hyper-V VM has Hyper-V Integration Services installed and enabled, network connectivity is fully functional, and necessary performance/security optimizations are applied, ensuring optimal operation within the Hyper-V environment.

Step 8: Validation, Testing, and Cutover

The final, critical stage involves comprehensive testing of the migrated VMs and their applications, performance validation, and planning a phased cutover. This ensures business continuity and confirms that the migration has met all functional and performance requirements.

# --- Sub-step 8.1: Functional Validation ---
# Access the migrated VM and its applications.
# This requires manual interaction and application-specific test scripts.
Write-Host "Perform comprehensive application testing on 'YourVMName_Migrated'."
Write-Host "Verify all services are running and accessible (e.g., web servers, databases, file shares)."
# Example: Check if a specific service is running inside the guest OS
# Invoke-Command -VMName 'YourVMName_Migrated' -ScriptBlock { Get-Service -Name 'W3SVC' -ErrorAction SilentlyContinue } | Select-Object Name, Status

# --- Sub-step 8.2: Performance Validation ---
# Monitor key performance counters on both the Hyper-V host and within the guest VM.
# Use Performance Monitor (perfmon.exe) or PowerShell to collect data.
# Example: Collect CPU and Memory usage for a short period on the Hyper-V host for a specific VM
Get-Counter '\Hyper-V VM(*)\% Processor Time' | Select-Object CounterSamples
Get-Counter '\Hyper-V VM(*)\Consumed Memory' | Select-Object CounterSamples

# --- Sub-step 8.3: Network Connectivity and Latency Testing ---
Write-Host "Test network connectivity from and to 'YourVMName_Migrated'."
Test-NetConnection -ComputerName 'YourVMName_Migrated' -Port 3389 # Example for RDP
Test-NetConnection -ComputerName 'YourVMName_Migrated' -Port 80   # Example for HTTP

# --- Sub-step 8.4: Backup and Disaster Recovery Testing ---
Write-Host "Verify that the new Hyper-V VM can be backed up and restored successfully using your backup solution."
Write-Host "Test your disaster recovery plan for the migrated VM."

# --- Sub-step 8.5: Cutover Plan Execution ---
# This is a high-level overview. Actual cutover requires detailed planning.
Write-Host "Execute a planned, phased cutover. This typically involves:"
Write-Host "1. Final sync of data (if applicable for applications like SQL replication)."
Write-Host "2. Shut down the original VMware VM."
Write-Host "3. Power on the Hyper-V VM and redirect traffic (DNS, load balancers, etc.)."
Write-Host "4. Monitor closely for issues post-cutover."

Invoke-Command -VMName: Executes a PowerShell script block directly within the guest VM.

Get-Counter: Collects performance counter data from the Hyper-V host or within a guest OS (if run inside the guest).

Test-NetConnection: Verifies network connectivity to a specified computer and port.

Write-Host: Provides textual guidance for manual testing and cutover strategy.

Portal alternative: Use Hyper-V Manager to connect to the VM and manually test applications. Use Performance Monitor (Perfmon.exe) on both the Hyper-V host and within the guest OS to gather performance metrics. Ping and tracert utilities can confirm network paths.

Expected result: All applications and services on the migrated VM are validated to be fully functional and performing optimally. A successful cutover is executed with minimal downtime, and the original VMware VM is decommissioned or archived.