Implemented scope
Implemented within documented permissions, object or content types, service limits, options, and validation paths.
Resources
AD migration guides for evidence-led planning.
Use these AD migration guides to evaluate fit, identify unsupported assumptions, and prepare a more useful migration discussion.
Evidence policyBridgeAD does not publish unverified customer counts, review scores, or performance benchmarks. Field evidence and methodology will be disclosed for any claim involving customer scale, success rate, or performance metric.
Evaluation library
Start with the decision you need to make.
These resources are public technical summaries. Environment-specific permissions, procedures, test cases, and runbooks are produced for an approved assessment or engagement.
Workload directoryOpen resource
Capability, prerequisite, and exclusion matrix
Compare Active Directory, Entra ID, Exchange, SharePoint, OneDrive, and Teams scope.
AssessmentOpen resource
Sample readiness assessment
See how ready, review, remediation, and deferred findings become an execution scope.
ArchitectureOpen resource
Security and deployment boundary
Review content handling, operational metadata, secrets, responsibility, and required egress.
PlatformOpen resource
Governed migration workflow
Understand discovery, mapping, frozen scope, execution, reconciliation, and evidence.
CommercialOpen resource
Packaging and pricing approach
See which topology, volume, fidelity, deployment, and responsibility variables affect scope and price.
Guides and checklists
Plan the migration before you shortlist tooling.
Standalone technical guides written for delivery teams. No sign-up required.
GuideRead the guide
Choosing an ADMT alternative
Where ADMT stops, what a modern replacement must cover, and how to compare without inheriting hidden risk.
GuideRead the guide
Quest Migration Manager alternative
Why teams evaluate alternatives to established tools, what to require, and how to compare on evidence rather than feature lists.
GuideRead the guide
BitTitan MigrationWiz alternative
When a program outgrows a content-copy model — AD depth, deployment control, and governance-grade evidence.
ChecklistRead the checklist
Active Directory migration checklist
Phase-by-phase: discovery, assessment, mapping, dry runs, pilot waves, validation, rollback, and decommission.
ChecklistRead the checklist
Microsoft 365 tenant-to-tenant migration checklist
Identity, Exchange, SharePoint, OneDrive, Teams, domain cutover, and validation gates in delivery order.
GuideRead the guide
SID history migration explained
How SID history preserves resource access, what it requires, where it breaks, and when to restamp ACLs instead.
GuideRead the guide
Cloud migration assessment
Turn read-only discovery into a scoped, costed plan with readiness findings and a bounded pilot boundary.
GuideRead the guide
Enterprise cloud migration
Why large programs are governance problems first — controlled waves, approvals, rollback ownership, and audit evidence.
Workload guides
Review the owning service before combining the program.
Each guide states the implemented path, required permissions, source and destination readiness, service-specific workflow, validation evidence, and manual boundary.
Claim definitions
What each status commits us to.
Status applies only to the stated capability, prerequisites, and exclusions. A supported connection or object type does not make every artifact in that Microsoft workload supported.
Dependency-gated scope
Implemented, but availability depends on Microsoft API approval, Graph endpoint stability, licensing, tenant state, or completion of another workload.
Topology-specific risk
Implemented with environment-dependent behavior that requires representative validation, success criteria, change control, and rollback ownership.
Not automatically included
Assigned to native tooling or an administrator, or not automated in the current release. It must not be represented as part of the supported path.
Publishing discipline
Qualifications stay next to the claim.
BridgeAD public material follows four rules so technical evaluators can distinguish product behavior from delivery assumptions.
- A status applies to a precise object, content type, option, or workflow
- Permissions, tenant conditions, service limits, and exclusions sit beside the relevant claim
- Representative product views are labeled and never presented as customer evidence
- Customer counts, certifications, partner designations, benchmarks, and guarantees require approved evidence before publication
Recommended first pilot
Keep the first proof bounded.
The recommended pilot verifies the operating loop before expanding object volume or workload breadth.
ConfigureTenant, roles, MFA, agent, connections.
DiscoverRead-only inventory and findings.
MapCSV, duplicates, target validation.
Dry runReview assumptions and stop conditions.
PilotBounded wave, reconcile, export evidence.