What is Quest Enterprise Reporter used for in an AD migration?

Enterprise Reporter discovers and documents the source Active Directory environment, including users, groups, OUs, computer objects, trust relationships, and workstation inventory. The discovery data informs migration roster sizing, wave planning, and prerequisite identification before any migration changes are made.

What is Quest RMAD-DRE and why use it during a migration?

RMAD-DRE (Recovery Manager for Active Directory, Disaster Recovery Edition) takes full AD backups with granular object-level recovery capability. Run before each migration wave, it provides a rollback path for any migration error. This is essential for enterprise migrations where a botched migration could affect thousands of users.

How does GPO Admin help with Active Directory migrations?

GPO Admin analyzes and compares Group Policy objects between source and target domains, identifying conflicts, deprecated settings, and policies that need to be recreated rather than migrated. Running this analysis early prevents post-migration policy failures that would affect every user in the new domain.

How many Quest products are typically needed for an enterprise AD and M365 migration?

It depends on scope. A straightforward tenant-to-tenant migration may only need ODM. A full enterprise migration with discovery, disaster recovery, GPO migration, AD migration, and cross-tenant O365 migration can use five or more Quest products coordinated together: Enterprise Reporter, GPO Admin, Migrator Pro, RMAD-DRE, and ODM.

How long does a 6,500-user enterprise AD and O365 migration take?

This engagement was structured across four phases: discovery, infrastructure and GPO analysis, AD migration execution, and O365 cross-tenant migration. Multi-phase enterprise migrations of this size typically run 6-12 months depending on stakeholder availability and the number of teams involved in prerequisite coordination.

Case study · Logistics

Enterprise AD Migration and Office 365 Cross-Tenant Migration for a Global Logistics Company

Migrating 6,500 users with Migrator Pro, RMAD-DRE disaster recovery, Enterprise Reporter discovery, GPO Admin policy migration, and ODM cross-tenant O365 migration.

TL;DR. Global logistics company, 6,500 users, corporate separation. Five Quest products coordinated: Enterprise Reporter for AD and workstation discovery, GPO Admin for policy analysis, Migrator Pro for AD migration, RMAD-DRE for disaster recovery protection, ODM for O365 cross-tenant migration.

What was the client environment?

A global logistics and transportation company with 6,500 users underwent a corporate separation requiring a full Active Directory migration, Office 365 cross-tenant migration, and comprehensive AD environment discovery. The project spanned multiple Quest product lines: Migrator Pro for Active Directory migration, RMAD-DRE for disaster recovery protection, Enterprise Reporter for AD and workstation discovery, GPO Admin for Group Policy analysis and migration, and ODM for O365 cross-tenant data migration. The engagement required coordination across the client's AD administrators, Exchange administrators, desktop team, and security team, with LeadThem Consulting managing the project from pre-sales through execution.

What made this migration challenging?

Enterprise logistics companies operate 24/7 global supply chains. Any identity or email disruption can cascade into missed shipments, broken tracking systems, and SLA violations across thousands of customers:

Full AD environment unknown. Before migrating 6,500 users to a new domain, the client needed comprehensive discovery of their Active Directory and workstation environments. Enterprise Reporter needed to read both source and target AD forests, requiring service accounts or trust relationships that the security team scrutinized heavily.
Multi-product coordination. The project required five Quest products working in sequence: Enterprise Reporter for AD and workstation discovery (ER-AD and ER-WFS), GPO Admin for Group Policy analysis and migration, Migrator Pro for AD migration, RMAD-DRE for disaster recovery, and ODM for O365 cross-tenant migration. Each product had its own prerequisites, service accounts, and deployment requirements.
Phased workstation migration. The client initially planned a single-phase migration but mid-project decided to split workstation migration into a separate second phase, requiring scope reassessment, budget reallocation, and timeline adjustment while keeping the identity and data migration on track.
Multi-team prerequisite coordination. Prerequisites were spread across four different client teams (AD Admin, Exchange Admin, Desktop, and Security), each with their own approval processes and timelines. Service accounts, remote access, test environments, and O365 licensing all needed to be coordinated across these teams.
Stakeholder budget concerns. The client's IT leadership raised concerns about the allocation of Quest project management hours, requiring detailed documentation of PM scope, budget separation, and value justification, all while maintaining project momentum.

How did LeadThem approach the migration?

Discover, protect, then migrate

Phase 1: Discovery with Enterprise Reporter. Deployed Enterprise Reporter for AD (ER-AD) to discover and document the source Active Directory environment, including users, groups, OUs, computer objects, and trust relationships. Deployed Enterprise Reporter for Workstations (ER-WFS) to inventory the workstation environment and assess migration readiness. Discovery data informed the migration roster, wave planning, and scope sizing for subsequent phases. Required service account access to read source AD forests, which triggered detailed security review.

Phase 2: Migration infrastructure and GPO analysis. Installed Migrator Pro and RMAD-DRE in the target domain. Configured RMAD to take full AD backups with daily scheduled runs, establishing a disaster recovery baseline before any migration changes. Ran GPO Admin analysis to document and compare Group Policy objects between source and target domains. Conducted prerequisite calls with AD Admin, Exchange Admin, and Desktop teams to validate readiness across all workstreams.

Phase 3: AD migration execution. Executed test user and group migrations with Migrator Pro to validate functional access in the target domain. Ran production migration of users, groups, and computer objects in coordinated waves. Verified application access, authentication, and group membership post-migration. Managed scope change when workstation migration was split into a separate phase.

Phase 4: O365 cross-tenant migration. Configured ODM for cross-tenant migration of mailboxes, OneDrive data, and Teams. Ran initial syncs, delta syncs, and cutover syncs across the 6,500-user population. Coordinated cutover communications and provided post-migration support for authentication and mail flow issues.

What technical challenges did we solve?

Enterprise Reporter cross-forest discovery. Enterprise Reporter needed service accounts with read access to both source and target AD forests. The client's security team required detailed justification for each permission, particularly for ER-AD's ability to enumerate users, groups, and computer objects across forest boundaries. Our team provided comprehensive documentation that satisfied security review without compromising discovery scope.
RMAD-DRE as migration safety net. With 6,500 users depending on Active Directory for daily operations, any migration error could be catastrophic. Our team configured RMAD-DRE to take full AD backups before each migration wave, providing granular object-level recovery capability. Any migration issue could be rolled back to the exact pre-migration state without a full domain restore.
GPO Admin policy parity. Group Policy objects in the source domain had accumulated years of modifications and exceptions. GPO Admin was used early in the project to analyze and compare policies between source and target, identifying conflicts, deprecated settings, and policies that needed to be recreated rather than migrated. This early analysis prevented post-migration policy failures that would have affected all 6,500 users.
Mid-project scope split. When the client decided to separate workstation migration into a second phase, our project manager assessed the timeline impact, documented the scope change in RAID updates, provided revised effort estimates, and secured additional project hours proactively, keeping the identity and data migration on its original timeline while properly scoping the deferred workstation phase.
Four-team prerequisite orchestration. With prerequisites distributed across AD Admin, Exchange Admin, Desktop, and Security teams, our PM established a structured prerequisite tracking process with dedicated calls for each team. This prevented the common pattern where one team's delay cascades into blocking all other workstreams. Each team had clear ownership of their deliverables and visibility into cross-team dependencies.
Budget transparency under scrutiny. When the client's IT leadership questioned the PM hour allocation, our project manager provided detailed documentation showing the separation between PM and consultant budgets, referenced the pre-sales agreement, and offered direct engagement to address concerns. This transparent approach resolved the issue without escalation and strengthened the client relationship.

What were the results?

The global logistics company's 6,500 users were migrated across Active Directory and Office 365. Enterprise Reporter provided the comprehensive discovery that sized the migration accurately. GPO Admin ensured Group Policy parity between domains. Migrator Pro handled the AD migration with RMAD-DRE providing disaster recovery protection throughout. ODM delivered the O365 cross-tenant migration of mailboxes, OneDrive, and Teams data. When scope changes and budget concerns arose mid-project, LeadThem Consulting's structured project management kept all workstreams on track.

Which tools and technologies were used?

Quest Migrator Pro for Active Directory user, group, and computer migration
Quest RMAD-DRE (Recovery Manager for Active Directory, Disaster Recovery Edition)
Quest Enterprise Reporter for AD (ER-AD) for directory discovery and documentation
Quest Enterprise Reporter for Workstations (ER-WFS) for workstation inventory
Quest GPO Admin for Group Policy analysis and migration
Quest On Demand Migration (ODM) for O365 cross-tenant migration
Office 365 (Exchange Online, OneDrive, Teams)

Why LeadThem Consulting

Most migration partners know one or two Quest products. LeadThem Consulting's team delivered this engagement across five: Enterprise Reporter for discovery, GPO Admin for policy analysis, Migrator Pro for AD migration, RMAD-DRE for disaster recovery, and ODM for O365 cross-tenant migration. For this global logistics company, that meant a single project management team coordinating the full stack rather than handing off between specialists. When scope changes and stakeholder concerns emerged, our PM handled them with transparency and documentation, not escalation. The result: 6,500 users migrated with zero unplanned downtime and full disaster recovery protection throughout.

What is Quest Enterprise Reporter used for in an AD migration?: Enterprise Reporter discovers and documents the source Active Directory environment, including users, groups, OUs, computer objects, trust relationships, and workstation inventory. The discovery data informs migration roster sizing, wave planning, and prerequisite identification before any migration changes are made.
What is Quest RMAD-DRE and why use it during a migration?: RMAD-DRE (Recovery Manager for Active Directory, Disaster Recovery Edition) takes full AD backups with granular object-level recovery capability. Run before each migration wave, it provides a rollback path for any migration error. This is essential for enterprise migrations where a botched migration could affect thousands of users.
How does GPO Admin help with Active Directory migrations?: GPO Admin analyzes and compares Group Policy objects between source and target domains, identifying conflicts, deprecated settings, and policies that need to be recreated rather than migrated. Running this analysis early prevents post-migration policy failures that would affect every user in the new domain.
How many Quest products are typically needed for an enterprise AD and M365 migration?: It depends on scope. A straightforward tenant-to-tenant migration may only need ODM. A full enterprise migration with discovery, disaster recovery, GPO migration, AD migration, and cross-tenant O365 migration can use five or more Quest products coordinated together: Enterprise Reporter, GPO Admin, Migrator Pro, RMAD-DRE, and ODM.
How long does a 6,500-user enterprise AD and O365 migration take?: This engagement was structured across four phases: discovery, infrastructure and GPO analysis, AD migration execution, and O365 cross-tenant migration. Multi-phase enterprise migrations of this size typically run 6-12 months depending on stakeholder availability and the number of teams involved in prerequisite coordination.

Planning an enterprise AD and O365 migration?

LeadThem Consulting delivers full-stack migrations with Migrator Pro, Enterprise Reporter, RMAD-DRE, GPO Admin, and ODM, from discovery through cutover.

Schedule your migration assessment