Separate DHCP migration preparation, transfer, and acceptance

Source facts

DHCP migration moves an existing server’s settings to a replacement, with the objective of continuing lease service without a noticeable client change. Microsoft separates preparation, export/import of role settings, verification of the replacement, and post-migration retirement or recovery. The procedure calls for permissions to authorize DHCP, administer both servers, and write to the migration store. Microsoft documentation.

Applicability

Use this review when replacing a DHCP server. Identify the source, destination, migration storage, and network segments served. Review a failover deployment through the separate failover-migration procedure before treating it as a single-server replacement.

DSE recommendation

Create a checklist that keeps preparation and final acceptance as distinct decisions. Have the network owner review the settings to be transferred and name the clients used for testing. Protect the migration store and assign responsibility for each server-side operation. Leave source retirement pending until the destination has been verified against the agreed service inventory.

Verification

Compare the imported configuration with the approved source inventory and test lease service on representative segments. Record the responding server, returned configuration, and any client impact. Reconcile missing settings or unexpected responses before accepting the replacement. Document the retirement decision and retain the migration evidence through the organization’s approved recovery period.

Official references

Microsoft Learn: Migrate DHCP server to Windows Server. Source reviewed September 8, 2026.