How to Migrate Users Between Domains in the Same Active Directory Forest
Question details
The user needs to retire two Active Directory domains and move a small number of users, computers, security groups, and distribution groups to another domain in the same forest while preserving permissions and Microsoft 365 mailboxes and licenses.
- Product
- Microsoft Active Directory, Microsoft 365, Azure AD Connect
- Device & OS
- not provided
- Scenario
- The administrator is consolidating two Active Directory domains into another domain in the same forest.
- Observed behavior
- Users, computers, groups, permissions, and Microsoft 365 mailboxes should remain intact after the migration.
Confirm the forest functional level, domain trust relationships, and the target organizational unit structure. Review Microsoft’s Active Directory Migration Tool guide and prepare a lab environment that mirrors the source and target domains before testing.
Test the Migration with Active Directory Migration Tool in a Lab
Use this solution before production to validate user, computer, and group migration behavior in a controlled environment.
Testing with the Active Directory Migration Tool reduces the risk of broken permissions, missing group memberships, or Microsoft 365 synchronization failures during a real domain consolidation.
Download Microsoft’s Active Directory Migration Tool guide from the Microsoft Download Center and install ADMT on a lab member server in the target domain.
Build a test environment that mirrors source and target domain controllers, group policies, and a test user account with a Microsoft 365 mailbox.
In ADMT, run the User Account Migration Wizard for a pilot user and select the target organizational unit.
Check the migrated user’s security identifier history, group membership, Exchange attributes, and sign-in behavior in the lab before production.
Update User Principal Names and Primary SMTP Addresses for Microsoft 365 Synchronization
Use this solution when migrated users must keep Microsoft 365 mailbox access and license assignment after moving to the target domain.
Review Permissions, Group Memberships, and SIDHistory Requirements
Use this solution to preserve resource access and reduce post-migration permission failures.
WPS Office: A Free Microsoft Office Alternative for Teams During Active Directory Domain Migration
WPS Office does not migrate Active Directory domains, but it gives your team a free, lightweight, familiar Microsoft Office-compatible suite for Word, Excel, PowerPoint, and PDF work while you complete the domain migration in Microsoft 365.
- 1. Download WPS Office: Visit the WPS Office download page and download the free installer for Windows, macOS, or mobile.
- 2. Open an existing document: Launch WPS Office and open a Microsoft Word, Excel, or PowerPoint file to confirm the ribbon layout and file compatibility.
- 3. Save in Microsoft format: Use File > Save As to keep the document in .docx, .xlsx, or .pptx format for users still on Microsoft 365.

Frequently Asked Questions
Can I migrate users between domains in the same forest without breaking Microsoft 365 mailboxes?
Yes, if the target domain is verified in Microsoft 365, the users’ UPNs and primary SMTP addresses are updated to the target domain, and Azure AD Connect synchronizes the changes successfully.
What is SIDHistory and should I use it during the migration?
SIDHistory preserves access to resources in the source domain during the transition. It can help avoid broken permissions, but it should be used only where required and after a security review.
Do I need to migrate computer accounts with ADMT?
Yes. Use the ADMT Computer Account Migration Wizard to move computers to the target domain so users can sign in with the new domain credentials and continue accessing domain resources.
How do I verify that Azure AD Connect has synchronized migrated users?
Open the Azure AD Connect Synchronization Service Manager, run Start-ADSyncSyncCycle -PolicyType Delta, and confirm that the migrated users show the target UPN and primary SMTP address in Microsoft 365.




