-
Live Migration vs Cold Migration in Hyper-V
-
How Hyper-V Live Migration Works
-
Benefits of Hyper-V VM migration
-
How to choose the right Hyper-V VM migration method
-
Method 1. Hyper-V Live Migration (Without Shared Storage)
-
Method 2. Migrate Hyper-V VM with Hyper-V manager
-
Method 3. Export and Import Hyper-V VM
-
Method 4. Move Hyper-V VM to another host via PowerShell
-
Method 5. Migrate Hyper-V VM to another host with Vinchin Backup & Recovery
-
Common Hyper-V Migration Issues and Fixes
-
Move Hyper-V VM to another host FAQs
-
Sum Up
As workloads grow, older Hyper-V hosts may no longer provide enough performance, capacity or reliability for production. Administrators then need to move VMs to other hosts to balance load, retire hardware, consolidate into a new cluster or prepare for maintenance.
Hyper-V offers several ways to do this, and they differ mainly in downtime and setup effort. This guide explains how each method works, what it requires and when to use it, so you can move VMs without losing data or configuration.
Live Migration vs Cold Migration in Hyper-V
Moving a Hyper-V VM to another host can be done in two ways:
Live migration moves a running VM to another host with no noticeable downtime. Users and applications stay connected while the VM changes hosts.
Cold migration moves a VM that is shut down or saved. It is simpler to set up but takes the VM offline for the whole move.
Hyper-V can also move different parts of a VM:
Move the VM only: the VM's running state moves to a new host, while its virtual hard disks stay on shared storage, such as a Cluster Shared Volume or an SMB 3.0 share.
Move the storage only: the virtual hard disks, checkpoints and configuration files move to a new location while the VM keeps running on the same host.
Move both: the VM and all its files move to another host. Hyper-V calls this "shared nothing" live migration, available since Windows Server 2012, and it requires no cluster or shared storage.
How Hyper-V Live Migration Works
Setup: the source host connects to the destination host and creates an empty VM there with the same configuration.
Memory transfer: the VM's memory pages are copied to the destination while the VM keeps running. Pages that change during the copy are sent again in further passes.
Switchover: when only a small amount of changed memory remains, the VM is paused for a moment, its final state is copied, and the VM resumes on the destination host. The network switch updates so clients reach the VM at its new location.
If the VM's disks are not on shared storage, Hyper-V copies them to the destination first and keeps them in sync until the switchover.
Benefits of Hyper-V VM migration
Migrating Hyper-V virtual machines provides several important benefits for virtualized environments.
First, it helps optimize resource utilization by moving VMs away from overloaded hosts to servers with available CPU, memory, and storage resources, which can improve VM performance and overall infrastructure efficiency.
By moving VMs to another host, organizations can maintain business continuity and minimize service downtime while performing maintenance tasks safely.
In hybrid virtualization environments, Hyper-V VM migration enables greater platform flexibility. For example, organizations may migrate workloads from Hyper-V to VMware to meet changing infrastructure requirements or support multi-platform virtualization strategies.
In disaster recovery scenarios, migrating or restoring VMs to healthy hosts helps rapidly recover business services after unexpected server failures or downtime events. Regular VM backups further improve recovery reliability and reduce data loss risks.
Additionally, VM migration and cloning simplify application deployment. When the same application or service is needed on another host, cloning or moving an existing VM provides a much faster solution than rebuilding the environment from scratch.
How to choose the right Hyper-V VM migration method
The right method depends on how much downtime you can accept, what infrastructure you have and whether you need to move VMs often or across platforms.
| Method | VM state | Downtime | Requirements | Best for |
| Hyper-V Live migration | Running | Minimal | Live migration configured on both hosts; similar hardware and software; fixed IP addresses | Business-critical VMs that can’t be shut down |
| Hyper-V Manager | Powered off | Yes, during the move | Source and destination hosts added to Hyper-V Manager | Quick moves when live migration isn't set up |
| Export and import | Powered off | Yes, during the move | Hyper-V Manager on both hosts; storage space for the export | Keeping a standalone VM copy as an extra safety layer |
| PowerShell | Depends on the command | Depends on the command | PowerShell knowledge and proper permissions; VM stored on an SMB share for Move-VM | Multiple hosts and repetitive migration tasks |
| Vinchin Backup & Recovery | Running | Minimal | Vinchin backup server; Hyper-V 2012 or later | Cross-version or cross-platform migration, combined with data protection |
Method 1. Hyper-V Live Migration (Without Shared Storage)
Live migration is the feature wanted by every IT administrator. It moves VM to another host while doesn't require shutting down the guest operating system or export the VM, greatlyly reducing downtime.
Hyper-V supports live migration on Windows Server 2008 R2 and later versions. It requires failover cluster setup (physically connecting servers), similar or the same hardware and software configuration (for compatibility ), fixed IP addresses, etc. before live migration.
In Windows Server 2016 and later versions, failover cluster is not required but more software layer configuration is required.
Method 2. Migrate Hyper-V VM with Hyper-V manager
Hyper-V Manager is often used in Hyper-V virtual environment management. If you haven’t done the configuration for live migration, just use Hyper-V manager to directly migrate VM when it is powered off.
Add the destination server:
Open Hyper-V Manager > right-click Hyper-V Manager (above the host name) > select Connect to Server > add the destination server and source server
Migrate Hyper-V VM:
Right-click the VM you would like to migrate > select Move > follow the Move Wizard to migrate the whole VM or just storage to another location
Method 3. Export and Import Hyper-V VM
Exporting would let you get all the files of the Hyper-V VM including data, snapshots, and configurations. After importing the VM to another host, you still keep the VM export as a kind of backup. Hyper-V Manager is still the tool used in this method.
The steps to export Hyper-V VM:
In Hyper-V Manager, right-click the VM on the source host > select Export > specify the destination to store the VM export > click Export
Steps to Import Hyper-V VM:
In Hyper-V Manager, right-click the destination host > select Import VM > follow the wizard to import the VM with the VM extract
Method 4. Move Hyper-V VM to another host via PowerShell
Microsoft PowerShell could also be used to migrate Hyper-V VM.
To move VM to a remote server when the virtual machine is stored on an SMB share, type the command below:
Move-VM -Name "Test VM" -DestinationHost remoteServer
Method 5. Migrate Hyper-V VM to another host with Vinchin Backup & Recovery
Built-in Hyper-V migration works best when hosts share a domain, a processor family and a supported configuration version. When they don’t, or when you want every move protected by a backup, backup-based migration is a more flexible option.
Vinchin Backup & Recovery backs up Hyper-V VMs without agents and restores them to another Hyper-V host, even one running a different Windows Server version. With V2V migration, the same restore can move the VM to VMware, Proxmox, oVirt, Oracle OLVM and other platforms, across 19+ supported hypervisors.
Every migration starts from a verified backup, so you always have a rollback point.
Encrypted transmission protects data while it moves between hosts.
One web console manages backup and migration jobs for all your hosts, with schedules and throttling policies.
Take Hyper-V to VMware Migration as an example:
1. Navigate to VM Backup > Restore, and select the Hyper-V host you backed up just now from the expanded list.

2. Then, select a VMware host as the restore destination.

3. Configure the restore strategy; either to run the task immediately or schedule it. You can also customize any migration or throttling policies.

4. Finally, name the job, check all the details, and click Submit to let the migration task start.

Vinchin Backup & Recovery has been selected by thousands of companies and you can also start a 60-day full-featured free trial here. Also, contact us, leave your requirements, and then you will receive your tailored solution.
Common Hyper-V Migration Issues and Fixes
1. Authentication fails
With CredSSP, migrations started remotely fail with a credentials error. Sign in on the source host and start the move there, or switch to Kerberos and configure constrained delegation as described above.
2. Processor incompatibility
The move fails when the hosts have different processor generations. Shut down the VM, enable processor compatibility mode in its settings, and try again. VMs cannot be live migrated between Intel and AMD hosts. Use export and import or backup-based migration instead.
3. VM loses its network after the move
The destination host has no virtual switch with the same name, or it is connected to a different VLAN. Create a matching virtual switch before you migrate, and check VLAN, firewall and routing settings.
4. Storage errors
The destination folder lacks free space or permissions, or the hosts can’t reach the shared storage. Check free space, grant both host computer accounts access to SMB shares, and merge unnecessary checkpoints to reduce the amount of data to copy.
5. Migration is slow or times out
Use a dedicated migration network, keep compression enabled, limit simultaneous migrations, and schedule large moves outside business hours.
After any migration, check that users can sign in, applications and databases connect, and scheduled tasks run. For critical workloads, back up the VM before you start so you can roll back if something goes wrong.
Move Hyper-V VM to another host FAQs
1. What is the difference between Hyper-V live migration and quick migration?
Live migration moves a running VM with no noticeable downtime. Quick migration, available in failover clusters, saves the VM’s state, moves it and resumes it on another node, so the VM is briefly unavailable.
2. Is live migration the same as failover?
No. Live migration is a planned move between healthy hosts. Failover restarts VMs on another node after a host fails. For disaster recovery, you still need backups or replication.
3. Does live migration move the VM’s disks too?
It depends on the move type. In a cluster or with SMB shared storage, only the running state moves and the disks stay in place. With shared nothing live migration, Hyper-V copies the disks to the destination host as part of the move.
Sum Up
You can move a Hyper-V VM to another host in 5 ways: live migration with Hyper-V Manager, live or quick migration in a failover cluster, export and import, PowerShell, and backup-based migration with Vinchin Backup & Recovery. Live migration avoids downtime but needs the most preparation, while export and import works almost anywhere at the cost of an outage.
If you need to move VMs between different Hyper-V versions or to other platforms, or simply want a backup behind every move, Vinchin Backup & Recovery can both back up Hyper-V VMs and migrate them from that backup. Try it free for 60 days.
Share on: