Decide what is ready before deciding when to migrate.
A BridgeAD assessment turns topology, object inventory, mapping quality, dependencies, permissions, and operating constraints into a scoped pilot recommendation.
An evidence pack, not a generic score.
The example below illustrates report structure. Names and figures are fictional and are not presented as a customer result or performance benchmark.
Source and target connections validated; agreed OUs and object classes inventoried.
Trust, permissions, collision behavior, and rollback procedure require lab validation.
Exchange item-level transfer is outside current generally available BridgeAD scope.
Automated domain-join workstation handling is planned and excluded from the pilot.
What the review needs.
Assessment depth depends on access and evidence. Read-only discovery is preferred; workshop-only assessments carry more assumptions and lower confidence.
- Source and destination forest/domain topology
- Trusts, DNS, network paths, and agent placement
- Object classes, counts, exclusions, and stale-object policy
- Target OU, naming, UPN, and identity mapping rules
- SID history, ACL, password, and coexistence requirements
- Change windows, approvals, rollback thresholds, and owners
- Microsoft 365 workloads requested and expected depth
- Security, residency, deployment, and evidence requirements
Outputs your team can act on.
Final deliverables are agreed before data collection so stakeholders know which decisions the assessment must support.
Readiness register
Validated prerequisites, assumptions, risks, blockers, evidence, and accountable owners.
Pilot boundary
Included objects, excluded workloads, success criteria, stop conditions, and rollback exercise.
Execution outline
Recommended mapping, dry-run, pilot, reconciliation, and approval sequence.
Start with a 45-minute topology review.
No production access is required for the initial scoping conversation.