How to Migrate DHCP Scopes to a New Windows Server
Applies to: migrations involving Windows Server 2019, 2022 and 2025.
DHCP migration should preserve scopes, reservations, options, policies and leases while avoiding two independently active owners.
Migration requires a tested rollback and application-owner acceptance. Visit networkmanager.info for managed Windows VPS services.
Prerequisites
- Install and authorize destination DHCP.
- Verify matching time and connectivity.
- Schedule short cutover.
- Back up source configuration.
Procedure
Step 1: Export source
Run on old server.
Export-DhcpServer -ComputerName dhcp01.corp.example -File C:\Temp\dhcp-export.xml -Leases -ForceStep 2: Transfer securely
Copy export to destination.
Step 3: Import destination
Run on new server.
Import-DhcpServer -ComputerName dhcp02.corp.example -File C:\Temp\dhcp-export.xml -BackupPath C:\Temp\DhcpBackup -Leases -ScopeOverwrite -ForceStep 4: Verify configuration
Compare scopes, options, reservations and policies.
Step 5: Cut over
Deauthorize or stop source, authorize destination and update relay addresses.
Step 6: Test clients
Renew on each representative subnet.
Verification
Confirm authorization, scopes and active leases on destination.
Get-DhcpServerInDC
Get-DhcpServerv4Scope -ComputerName dhcp02.corp.example
Get-DhcpServerv4Lease -ComputerName dhcp02.corp.example -ScopeId 192.0.2.0Rollback
Stop destination, restore relay configuration and reauthorize/start source using the preserved export if cutover fails.
Operational notes
Avoid overlapping active scope ownership unless configured as supported DHCP failover.
Official references
Explore Netcloud24 Canada.
