Migrating a DHCP from Server 2012 R2 to Server 2016 involves only two commands. The first command is to export the DHCP data and is run on Server 2012 R2. The second command imports the DHCP data and it is run on the Windows 2016 server.

The following steps illustrate how to use those two commands.

Import and Export DHCP Data

1. Log in with an administrator account to the Windows Server 2012 R2 system.

2. Open Powershell and then type in the following command:

Export-DhcpServer -File C:\DHCPdata.xml -Leases -Force -ComputerName old.network.local –Verbose

3. Copy the file C:\DHCPdata.xml the Windows Server 2016 system.

4. Install and configure the DHCP role on Server 2016 (Same Server 2012 R2 installation steps, Check my related article on DHCP Server 2012 R2 for help).

5. Start the DHCP service.

6. Type in the following command on Powershell to import the DHCP Data.

Import-DhcpServer -File C:\DHCPdata.xml -BackupPath C:\DHCP\ -Leases -ScopeOverwrite -Force -ComputerName new.network.local –Verbose

7. Restart the DHCP service.

Verify your DHCP scope, IP leases, reservations etc and they should match with DHCP Server 2012 R2.

How to Migrate DHCP from Windows Server 2012 R2 to Server 2016

Karim Buzdar

About the Author: Karim Buzdar holds a degree in telecommunication engineering and holds several sysadmin certifications. As an IT engineer and technical author, he writes for various web sites. You can reach Karim on LinkedIn

4 thoughts on “How to Migrate DHCP from Windows Server 2012 R2 to Server 2016

  • Avatar
    April 13, 2017 at 1:18 pm

    Nice post!
    Your post helped me live migrating a 2012 DHCP server to 2016.


  • Avatar
    June 13, 2017 at 5:35 am

    All the DHCP server migration tutorials forget that you must remove/stop the old DHCP server.

  • Avatar
    August 11, 2017 at 4:29 pm

    Is the same procedure working on Cluster?


    • Avatar
      September 17, 2018 at 6:42 am

      Hi, did you ever got a response to your cluster question ?


Leave a Reply

Your email address will not be published. Required fields are marked *