Skip to Content

How Can You Safely Move Hyper-V from Windows Server 2019 Core to 2025?

What Are the Essential Steps for a Successful Hyper-V Migration with Minimal Risk?

Moving Hyper-V from Windows Server 2019 Core to Windows Server 2025 can improve stability and unlock new features. Each step matters for a happy and working setup. Let’s take each part one at a time, with clear actions and no jargon. The goal: every virtual machine runs smoothly, nothing gets lost, and you feel calm and confident.

What Are the Essential Steps for a Successful Hyper-V Migration with Minimal Risk?

Prerequisites

  • Windows Server 2025 must be installed on your new host.
  • You need the same number of network cards (with identical names) on both the old and new servers.
  • The Hyper-V role should be installed on the new server.
  • Back up all your virtual machines and the host configuration to avoid loss.
  • Write down or export your virtual switch (vSwitch) settings—do not skip this.

Step 1: Export Virtual Switches

You want all network settings copied so VMs work seamlessly.

Open PowerShell.

Run:

Export-VMSwitchConfiguration -Path "C:\Export\SwitchConfig.xml"

This command saves your network settings to an XML file.

If your setup doesn’t support this command, list all your vSwitches:

Get-VMSwitch

Then, note names, types, and network cards for manual recreation.

Step 2: Export Virtual Machines

Get every VM safely moved.

Open PowerShell.

To export all VMs at once:

Get-VM | Export-VM -Path "D:\ExportVMs"

To export a single VM:

Export-VM -Name "VM-Name" -Path "D:\ExportVMs\VM-Name"

Always check exported files to be sure every disk and setting is copied over. Wait for the export to finish before moving on.

Step 3: Import Virtual Switches on New Server

Bring your old network setup into the new system.

Open PowerShell on Windows Server 2025.

Run:

Import-Clixml -Path "C:\Export\SwitchConfig.xml"

For each switch, run the right command based on its type:

# Example for External switch
New-VMSwitch -Name "SwitchName" -NetAdapterName "AdapterName" -AllowManagementOS $true
# For Internal switch
New-VMSwitch -Name "SwitchName" -SwitchType Internal
# For Private switch
New-VMSwitch -Name "SwitchName" -SwitchType Private

Make sure adapter names match what’s on the new server. If not, update them to fit your new hardware. Any mismatch can cause problems.

Step 4: Import Virtual Machines

Get your VMs running on the new host.

For each VM, run:

Import-VM -Path "D:\ExportVMs\VM-Name" -GenerateNewId

The -GenerateNewId option is important. It makes a new unique ID for each VM, preventing conflicts—especially if you import the same VM more than once or the old VM still exists elsewhere.

Step 5: Verify Everything Works

Check every detail to guarantee smooth VM operation.

To see network adapters:

Get-VM -Name "VM-Name" | Get-VMNetworkAdapter

To check boot order and firmware:

Get-VM -Name "VM-Name" | Get-VMFirmware

To see storage paths:

Get-VM -Name "VM-Name" | Select-Object Name, ConfigurationLocation, SnapshotFileLocation, AutomaticCheckpointsEnabled

Review the results. Make sure settings match what you expect.

Step 6: Start and Test the Virtual Machines

Time to bring your VMs online and check everything runs as it should.

Start all VMs at once:

Start-VM -Name *

Check that every VM boots up and works as planned.
Open each VM, log in, check network and disk access.

Best Practices and Final Tips

  • Use folders with clear names and dates for exports.
  • Always double-check when you move or rename anything.
  • Test each VM before putting anything into production.
  • Write down what you do at every step.

Frequently Asked Questions

Question: Can I export a running VM?

Answer: No. The VM needs to be off or saved.

Question: What to do if export fails?

Answer: Make sure you have admin rights. Check disk space. Try again.

Question: Is there one tool that does it all automatically?

Answer: No. This migration is manual—each step must be done with care.

A careful, step-by-step process brings happy results and steers you clear of common pitfalls. Following these steps, you make the move from Windows Server 2019 Core to 2025 as safe and positive as possible.