Migration workloads

One operating model for identity and Microsoft 365 migration.

BridgeAD brings discovery, mapping, controlled execution, delta passes, exception handling, validation, and audit evidence into one workspace. Each workload page states the delivery boundary, required Microsoft permissions, and work that remains native or manual.

Plan an assessment See the operating model

BMigration control Environment connected

Program readinessScope before executionRepresentative operational view

Identity foundationMappings and dependencies reviewed

Ready

Mailbox wave 01Verification and delta configured

Validated

Collaboration contentSharing remediation identified

Review

Teams workspacesProtected API dependency recorded

Conditional

AssessmentExecutionValidationEvidence

Scope is explicitSupported, conditional, pilot, and manual work are separated.

Identity comes firstMappings and destination objects govern dependent workloads.

Delta is plannedRepeatable passes reduce the final change window.

Evidence is retainedPer-item outcomes, reconciliation, and operator actions remain inspectable.

Choose a workload

Start with the service that owns the data.

Microsoft 365 experiences cross service boundaries: Teams files live in SharePoint, meetings rely on Exchange, and every workload depends on destination identities. BridgeAD makes those dependencies visible before a migration wave is approved.

Controlled pilot

Active Directory

Discover and map users, groups, computers, OUs, contacts, and policies; validate duplicates and dry runs; then execute an agreed topology-specific pilot.

Explore Active Directory

Planning boundary

Microsoft Entra ID

Validate tenant connections, admin consent, target identity rules, mappings, role ownership, and hybrid sequencing before source changes begin.

Explore Entra ID

Supported

Exchange and Microsoft 365

Move mailbox content between Microsoft 365 tenants with folder-aware copy, delta passes, per-mailbox status, reconciliation, and DNS cutover checks.

Explore Exchange

Supported scope

SharePoint and OneDrive

Assess sites and drives, migrate supported files and libraries with resumable transfer, apply mapped permissions, and report sharing or content exceptions.

Explore SharePoint and OneDrive

API dependent

Microsoft Teams

Assess and reconstruct teams, channels, mapped membership, supported tabs, settings, and tags; coordinate files and meetings through their owning services.

Explore Microsoft Teams

Delivery sequence

A migration wave is more than a copy job.

BridgeAD treats readiness and validation as first-class stages. Operators can stop on unresolved prerequisites instead of discovering identity, consent, governance, or destination gaps after data has moved.

Discover

Inventory source objects, content volume, ownership, dependencies, and known constraints.

Map

Resolve source-to-target identities, names, destinations, permissions, and exceptions.

Prepare

Confirm licensing, consent, endpoints, capacity, policies, and rollback responsibilities.

Migrate

Run controlled waves with retries, checkpoints, throttling awareness, and operator visibility.

Validate

Reconcile outcomes, document unresolved items, approve cutover, and retain evidence.

Capability language

Read status labels as delivery boundaries.

Status is about the stated scope, not the Microsoft product as a whole. A supported workload can still include tenant configuration, compliance controls, or artifact types that require a native tool or administrator action.

Supported

Implemented delivery scope

Available within the documented object types, prerequisites, permissions, and validation path.