trio.so
Explained

Active Directory Migration: A Step-by-Step Checklist

An Active Directory migration checklist and project plan: assess, prepare, migrate users and computers, cut over, and the tools for each path.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

An Active Directory migration moves your users, groups, computers and services to a new domain controller, a new domain or forest, or to Microsoft Entra ID. Whatever the destination, the work follows the same six steps: assess and inventory, plan, prepare the target, migrate objects in stages, cut over, then decommission the old environment. The checklist below works as a domain migration checklist you can paste into a project plan, followed by the three common paths and an honest look at the tools.

Domain migration checklist: six steps

  1. Assess and inventory.
    • Record domain and forest functional levels, domain controllers, FSMO role holders and sites.
    • Export users, groups, computers, OUs, GPOs and service accounts. Flag stale and disabled objects.
    • List what depends on AD: file servers, Exchange or mail, SQL, VPN, Wi-Fi (RADIUS), printers, certificate services, line-of-business apps and anything using LDAP or Kerberos.
    • Run dcdiag and repadmin /replsummary. Fix replication problems before you start.
  2. Plan.
    • Choose the path (new server, new domain or forest, or Entra ID) and the cut-over date.
    • Decide the naming, DNS and IP changes, and whether you need SID history so users keep access to resources during the move.
    • Define the batches (pilot group first) and the rollback for each.
    • Agree a change window and who communicates with users.
  3. Prepare the target.
    • Build the new domain controllers or the new forest, with DNS and time sync.
    • Create the OU structure, security groups and delegation model. Rebuild GPOs rather than copying every old one.
    • Set up trusts between old and new if both will run in parallel. Test name resolution both ways.
  4. Migrate in stages.
    • Groups first, then users, then service accounts, then computers and servers.
    • Pilot with IT, then one department, then everyone else.
    • Migrate profiles and re-join computers. Test file access, printing, VPN and mail after each batch.
  5. Cut over.
    • Move the FSMO roles (if replacing servers), repoint DNS and DHCP, and update applications to use the new domain controllers.
    • Run both environments side by side for a defined period. Keep the old one read-only where possible.
  6. Decommission.
    • Confirm nothing authenticates against the old controllers. Check logs for a few weeks.
    • Demote the old domain controllers, remove them from sites and DNS, and clean up metadata.
    • Back up the final state before you delete anything and keep it for the period your policy requires.

Active Directory migration project plan

If your manager asks for a project plan, use the six steps as phases and put these items under each one.

PhaseDeliverableDone when
AssessInventory of objects, dependencies and replication healthEvery AD-dependent system has an owner
PlanTarget design, batch schedule, rollback plan, communicationsPlan is signed off, change window booked
PrepareTarget domain or controllers built, trusts and DNS testedA test user can sign in and reach resources across the trust
MigratePilot, then batches, with a test script per batchEach batch passes the test script
Cut overRoles moved, DNS and apps repointedNo authentication hits the old controllers for an agreed period
DecommissionOld controllers demoted, documentation updatedOld environment is removed and backed up

Migrate Active Directory to a new server (same domain)

This is the simplest path: the domain stays the same and you replace the servers underneath it. Use it when you retire Windows Server 2012 or 2016 domain controllers.

  1. Join a new Windows Server to the domain and promote it to a domain controller. Windows prepares the schema when you promote the first controller of a newer version.
  2. Check replication: repadmin /replsummary and dcdiag.
  3. Move the five FSMO roles to the new controller. In PowerShell: Move-ADDirectoryServerOperationMasterRole -Identity "DC02" -OperationMasterRole 0,1,2,3,4. Confirm with netdom query fsmo.
  4. Point DNS, DHCP and application settings at the new controller. Move the DNS server role if the old controllers hosted it.
  5. Demote the old controllers, then raise the domain functional level if your design calls for it.

Run the old and new controllers together for at least a few days. If Group Policy or file replication uses the legacy FRS service, move SYSVOL replication to DFSR first.

Migrate Active Directory to a new domain or forest

You choose this path after a merger, a spin-off, or when the old domain design cannot be fixed in place. It is more work because accounts get new SIDs.

  • Create a trust between the source and target so both sides can see each other's objects.
  • Use SID history. Migrated users keep their old SID as an extra value, so they still reach file shares and other resources that have not moved yet. Plan to clean it up when migration ends.
  • Migrate groups before users so access follows the people as they move.
  • Re-join computers to the new domain and translate local profiles and permissions so users keep their data.
  • Handle passwords on purpose. Either migrate them with a tool that supports it, or issue resets with a communication plan.
  • Update service accounts last, one at a time, with the application owner present.

Migrate Active Directory to Microsoft Entra ID

Moving to Entra ID (formerly Azure AD) is usually a hybrid project first, not a switch. Your on-premises AD stays the source of truth while you sync identities to the cloud.

  1. Clean up AD first: remove stale accounts, fix duplicate attributes, and set a consistent UPN suffix that matches a domain you can verify in Entra ID.
  2. Choose a sync tool. Microsoft Entra Connect Sync is the long-standing option. Microsoft Entra Cloud Sync uses a lightweight agent and cloud-managed configuration, and it supports multiple disconnected forests. Microsoft's decision guide lists which features each supports. Check it before you pick.
  3. Sync a pilot group, confirm sign-in, then widen the scope.
  4. Make devices hybrid joined (Cloud Sync can synchronize computer objects for hybrid join when device sync is on) or join new devices to Entra ID directly.
  5. Move applications to modern authentication one by one. Servers and apps that need Kerberos or LDAP keep AD in place.

Many companies stay hybrid for years. That is a valid end state. Removing the last on-premises domain controller only makes sense when nothing needs it any more.

Active Directory migration tools

There is no single official tool for every scenario. What exists:

  • Active Directory Migration Tool (ADMT). Microsoft's free tool for moving objects between domains and forests. Check Microsoft's support policy before you rely on it. As of the 12 February 2026 revision, Microsoft says ADMT has not been updated for Windows 10, Windows 11 or Windows Server 2016, 2019 and 2022, support cases are handled on a best-effort basis, and the ADMT 3.2 code base is deprecated with no further fixes. It also lists known issues, such as ADMT failing where Credential Guard is on. Lab it first.
  • PowerShell. The ActiveDirectory module (Get-ADUser, New-ADUser, Move-ADObject and others) covers inventory, bulk creation and cleanup. It does not move passwords or SID history for you.
  • Commercial migration tools. Vendors such as Quest (On Demand Migration) and BitTitan publish migration guides and tools for directory and tenant moves. Capabilities change, so compare them against your scenario before you buy.
  • Microsoft Entra Connect Sync and Cloud Sync. For syncing to Entra ID, not for moving AD between domains.

Common mistakes

  • Starting without fixing replication or DNS first.
  • Forgetting service accounts and the applications that hard-code a domain controller name.
  • Copying every old GPO into the new domain instead of rebuilding the ones you still need.
  • Decommissioning the old controllers before checking logs for authentication that still hits them.
  • Leaving SID history in place forever.

Related reading: Active Directory Certificate Services (migrate or rebuild the certificate authority deliberately), Active Directory security, cleaning up Active Directory, how to add a Mac to Active Directory and connecting PostgreSQL to Active Directory.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Start your free trial

No credit card required
Full access to all features

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

Add the new server as a domain controller, check replication, move the five FSMO roles to it, repoint DNS and applications, then demote the old controller. The domain itself does not change.

Clean up AD, sync identities with Microsoft Entra Connect Sync or Cloud Sync, move devices to hybrid join or Entra join, and move apps to modern authentication step by step. Most companies stay hybrid for a long time.

Create a trust, migrate groups first and then users, keep SID history during the move, re-join computers and translate profiles, and handle passwords by migration tool or reset.

ADMT is Microsoft's free tool but its code base is deprecated and Microsoft supports it on a best-effort basis. PowerShell handles inventory and bulk work, and commercial tools from vendors such as Quest and BitTitan cover more scenarios.

Related

From the blog

The related industry news, interviews, technologies, and resources.