Active Directory Migration Tool is a Microsoft utility for migrating users, groups, and computers between Active Directory domains or forests. It can copy accounts and preserve selected attributes, translate security identifiers, and help map old permissions to new objects during directory consolidation or restructuring.
What ADMT Does in a Directory Migration
Active Directory Migration Tool sits in the middle of a directory consolidation project, where the core job is to move users, groups, and computers while keeping the business usable. Its value is not just account copying, it is the controlled translation of old directory relationships into the new domain or forest so logon, group membership, and mapped access continue to work.
That makes ADMT a migration utility with security consequences, because identity objects are also authorization objects. When the tool translates security identifiers and selected attributes, it is helping preserve access continuity across a structural change in the directory.
Why ADMT Is Used in Restructuring and Consolidation
ADMT is usually chosen when organisations need to merge forests, split domains, or modernise a legacy AD design without rebuilding every account from scratch. The practical attraction is that it can reduce manual re-provisioning, keep user access more stable during cutover, and support staged migration rather than a “big bang” rebuild.
In those projects, the tool becomes part of the directory change plan, not just a utility. A successful migration usually depends on clean source inventory, careful dependency mapping, and a clear view of what must move with the account, such as group membership, profile associations, and any permissions that must be re-established in the target domain.
Security Decisions Hidden Inside an ADMT Migration
The security significance of ADMT is that migration is also a privilege and trust transition. If security identifiers, service accounts, or delegated rights are carried forward too broadly, the target environment can inherit old access paths that no longer fit the new structure. The reverse problem also matters: if mappings are incomplete, users can lose legitimate access and create workarounds that weaken control.
ADMT projects often expose questions about trust configuration, inter-domain permissions, and the treatment of privileged or service-related accounts. Those choices determine whether the migration preserves intended access or accidentally extends it beyond the new security model.
For a broader view of how directory changes, forest design, and security controls fit together, the Active Directory Domain and Forest Migration Security Guide is the closest companion reference. If the migration is part of a wider directory strategy, the Directory Services and Cloud Directory Buyer's Guide helps frame the destination model as well as the move itself.
What to Check Before, During, and After the Move
Before using ADMT, organisations need a reliable inventory of the accounts, groups, computers, trusts, and dependent applications that will be touched by the migration. During the move, they need to watch for permission translation failures, stale trust assumptions, and any object that is still relying on the old domain for access decisions. After cutover, validation should confirm that inherited permissions are correct and that legacy mappings have not created residual access paths.
That post-migration review is especially important for service accounts and highly privileged objects, because they are the most likely to preserve access in ways the target design did not intend. A migration is complete only when the new directory state reflects the intended security model, not just when the objects have been copied.
Risk and Threat Considerations
Directory migration expands the attack surface temporarily because old and new trust relationships, migration permissions, and translated access paths can overlap. If those temporary bridges are not tightly controlled, an attacker who reaches the migration plane may gain a route from the source directory into the target environment or preserve access that should have expired.
Failure mechanism: Migration tools and trust relationships can preserve overbroad access, stale permissions, or privileged account exposure, which lets old authorization state survive into the new directory.
Impact: The result can be lateral movement, unexpected privilege retention, missed decommissioning of legacy access, or a compromised migration window that becomes a bridge into the consolidated environment.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-1 — Inventory and Control of Enterprise Assets | ADMT migrations depend on knowing which domain assets, accounts and hosts are in scope. |
| Recommendation — Maintain an accurate asset inventory before translating identities and permissions across domains. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | ADMT migrations often require account and secret lifecycle decisions during directory change. |
| AC-2 — Account Management | ADMT moves and maps directory accounts, making account lifecycle control central to the subject. | |
| AC-6 — Least Privilege | Migration permissions and translated access should be constrained to the minimum needed. | |
| Recommendation — Rotate or reissue credentials and remove obsolete authenticators after migration completes. Reconcile migrated accounts, disable obsolete ones, and verify ownership after cutover. Limit migration privileges and review translated access for excess entitlement. | ||
| ISO/IEC 27001:2022 | A.5.18 — Access rights | Directory migration changes who can access what, so access-right governance is directly implicated. |
| Recommendation — Review and recertify access rights after directory restructuring. | ||
Practitioner Guidance
Governance implication: Treat ADMT as a controlled security change, not just an IT project task. Ownership should cover identity translation, trust settings, service account handling, and the removal of legacy dependencies after cutover.
What to watch for: The biggest warning signs are unreviewed SID history use, broad migration privileges, and lingering source-domain dependencies after users have moved. Those are the conditions that most often turn a migration convenience into a long-lived access risk.
Related resources from NHI Mgmt Group
- Active Directory
- What is the main risk when migrating a Windows machine off Active Directory with a profile migration tool?
- What breaks when Active Directory migration carries old privilege into the target forest?
- How should security teams plan an Active Directory migration to avoid downtime and access failures?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org