AD migration software for MSPs across client environments.
AD migration software for MSPs standardizes discovery, mappings, dry runs, pilot approvals, operator roles, exceptions, reconciliation, and evidence while keeping each client's topology and data boundary explicit.
Standardize the operating model, not the client's topology.
Templates should make prerequisites and decisions repeatable without assuming every forest, trust, identity rule, or Microsoft workload behaves the same way.
- Client tenant and privileged-role separation
- Agent pairing and connection validation checklist
- Reusable discovery and assessment sequence
- Mapping, CSV, and duplicate-validation workflow
- Dry-run and controlled-pilot entry criteria
- Exception, retry, and rollback decision ownership
- Audit exports and customer sign-off evidence
- Explicit Supported, Controlled pilot, Limited, and Planned scope
Qualify
Identify topology, supported scope, blockers, and delivery assumptions before quoting.
Deliver
Use role-scoped operators, controlled agents, repeatable gates, and client-specific rollback criteria.
Close
Reconcile outcomes, export evidence, record exceptions, and hand over operating decisions.
What is available today, and what is still being built.
Each row reflects the current client-supported feature matrix for the release used in delivery. Controlled-pilot and manual items are scoped per client, not assumed.
| Capability | Status | BridgeAD path | Boundary |
|---|---|---|---|
| Client separation | Supported | Separate customer tenants with role-scoped operator access to that client's projects, discovery, and jobs. | Cross-client views and a shared partner dashboard are not yet a single pane of glass. |
| Discovery and assessment | Supported | Repeatable discovery, readiness assessment, mapping, and dry-run sequence per client. | Assessment does not certify target topology readiness. |
| AD execution | Controlled pilot | Staged directory object operations with reconciliation and rollback controls. | Requires per-client topology-specific lab validation, change control, acceptance criteria, and named rollback ownership. |
| Evidence and sign-off | Supported | Audit exports, exception records, and completion evidence per client job. | Customer sign-off remains a client decision. |
| Partner marketplace | Planned | Not yet available; scoped through direct partner engagements. | A standardized connector catalog and cross-client pipeline experience remain areas for product investment. |
Common partner questions.
Can I manage all my clients from one dashboard?
Not yet. Each client runs in a separate tenant with role-scoped operator access. A consolidated cross-client view is planned; today each engagement is operated within its own boundary.
Can I white-label or resell BridgeAD?
Partner and reseller arrangements are scoped through a direct engagement. Use the partner contact route to discuss commercial and branding terms.
What does a controlled pilot require from my client?
Topology-specific lab validation, approved privileges and network paths, documented change controls, acceptance criteria, and named rollback ownership before any production execution.
How do I start a partner engagement?
Bring one representative client pattern — forest pair, trust configuration, and approximate object counts. We will map it to current platform boundaries and identify a repeatable service package.
Bring one representative client pattern.
We will map it to the current platform boundary and identify what can become a repeatable service package.