Migrating a child Active Directory into a parent domain
Users need to keep their child domain logins while accessing parent systems, but split email environments break directory visibility. Because Exchange Online does not know about them, remote mailboxes cannot see on-prem contacts. This stops administrators from recreating distribution groups in the cloud, since on-prem users still need to email those groups.
Core Friction Pattern
Analysis of 8 peer accounts across online developer and community forums reveals that “Migrating a child Active Directory into a parent domain” repeatedly surfaces due to edge-case mismatches between standard defaults and real-world environments. Standard troubleshooting frequently falls short, compelling practitioners to develop custom workarounds.
+5 alternative community-tested workarounds cataloged below.
What the numbers show
Counted from the threads quoted below. How we count
- The most recent one is from October 2026.
- This comes up 102.4× more often in r/msp than across the site as a whole.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
Migrating a child Active Directory into a parent domain
- 1Creating on-premises contacts with matching SMTP addresses for remote usersDid this help you?
- 2Syncing contacts to the cloud directory with proper routing addressesDid this help you?
- 3Rebuilding the user profile entirely from scratchDid this help you?
- 4Performing a full device wipe and OS reinstall (Autopilot)Did this help you?
- 5Purchasing paid migration tools to automate and script the processDid this help you?
- 6Creating custom pre-flight scripts to backup data, suspend encryption, and manually remap cloud file syncsDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“How would we go about migrating the child co AD (users/workstations) into the parent co so that they could continue to login with the child co domain and gain access into the parent co systems?”source ↗
“A onprem Mailbox can see all the contacts and regular members while a remote mailbox from domain 1 can only see the normal mailboxes and not the onprem contacts I created.”source ↗
“Unfortunately I cannot recreate the distribution group in exchange online since also people from onprem exchange needs to mail to the group.”source ↗
“contacts won't show up for remote mailboxes because exchange online doesn't know about them.”source ↗
“For some reason it requires then disconnecting the computer from Entra, login with a local admin, and then rejoin it. Everything except Chrome data and extensions have converted so far.”source ↗
“If they are not syncing OD its easy but if they are at all we have had trouble. We did 2 domain to intune and the onedrive was the biggest problem, but did not use the paid version.”source ↗
“Last time I used Profwiz (easily 5 years ago) it "worked" but then wouldn't allow me to log the new Entra user in. I fucked with it for HOURS that night and decided to revert this test user back only to find it had overwritten the original profile and thus "burned the boats".”source ↗
“With ImmyBot's migration tool, it actually completely deleted the old profiles and there is nothing you can do about it that I've found.”source ↗
“From experience we had issues with machines that were win10 upgrade to win11 When the ad profile was migrated into the entrance profile, OneDrive would not sign in and we ultimately had to recreate the profile after deleting some registry keys”source ↗
Where this came up
People with this problem also raised
Related community dilemmas clustered by discussion consensus
How to migrate company email from Google Workspace to Microsoft 365
Migrating email between cloud office platforms requires moving all messages while managing user accounts and running both systems concurrently during the transition. Without a clear migration path, businesses risk losing access to their company email for sending and receiving, resulting in months of locked-out accounts and disrupted operations.
Moving a virtual domain controller without a USN rollback
Official guides offer conflicting advice on how to move a virtual machine domain controller to new hardware safely. This leaves administrators stuck guessing whether they have to completely demote and rebuild the DC from scratch.
Gotchas when migrating user files to OneDrive
Standard migration tools often skip orphan files and local computer directories, forcing sysadmins to run time-consuming scripts across thousands of users to move the remaining data. Once migrated, traditional recovery workflows break because admins can no longer rely on file server backups like Veeam to restore overwritten files. It also remains unclear whether the cloud client forces users to re-authenticate automatically when their domain password changes.
How to migrate remote management platforms without rebuilding everything
Forcing a migration between management platforms requires completely rebuilding years of established policies, scripts, automation, and patching across thousands of endpoints. This massive operational friction drains engineering resources and leaves teams exhausted by repeated, vendor-pushed transitions.
Why is it so hard to export and switch accounting software?
Legacy platforms limit data exports to basic CSV or Excel formats that lack clean mapping structures, forcing businesses to rebuild historical records and redo years of bank reconciliations from scratch. This friction prevents companies from switching to better tools without losing critical transaction history or spending weeks fixing reconciliation discrepancies.
What to do with an old 401k account
You should track down and move your old accounts, because many plans charge monthly maintenance fees that can eventually drain your balance to zero. Finding them might require calling your former employers directly to regain access. Be careful where you move the money, as rolling a 401k into a Traditional IRA makes future Backdoor Roth contributions tax-heavy and unfeasible.