Discover
Inventory source objects, content volume, ownership, dependencies, and known constraints.
BridgeAD Cloud Workloads
Microsoft 365 migration workloads in one application.
The Microsoft 365 migration workloads application covers AD, Entra ID, Google Workspace, endpoints, servers, Exchange, SharePoint, OneDrive, and Teams — including certified any-to-any mailbox migration between Exchange Online, Gmail, IMAP, on-premises Exchange, and PST/EML archives. One M365 application replaces a stack of separate Office 365 migration tools.
Explicit delivery scopeControlled migration wavesReconciliation and evidence
BridgeAD Cloud WorkloadsMigration operations workspace
Programme control across every workloadProgramme phases, workload health, migration progress, throughput, exceptions, and operational evidence remain visible in one tenant workspace.
Product view · synthetic demonstration dataScope 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.
AD
Supported
IDActive 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 DirectorySupported · directory scope
GWMicrosoft Entra ID
Select named tenants, preview UPN transformations, migrate users and static security groups tenant-to-tenant, refresh attributes or membership on repeat runs, or provision Entra identities into AD.
Open the Entra workflowsSupported · directory scope
EPGoogle Workspace directory
Preview and sync Workspace users and groups into Entra ID, or provision them directly to on-premises AD through an assigned agent.
Review the Google directory workflowSupported
SVEndpoint migration
Run pre-flight checks, AD or Entra rejoin operations, cloud-native device conversion, Microsoft 365 app reconfiguration, BitLocker escrow verification, and per-device acceptance.
Review endpoint operationsSupported
MXIIS and SQL Server workloads
Move IIS sites and app pools or run preflight-gated SQL Server backup, restore, login, optional low-downtime, Agent job, and linked-server workflows.
Review server operationsSupported
EXGmail, IMAP & archive routes
Bring Gmail, IMAP-host, and archived mailboxes into Microsoft 365 (or export back out) over certified routes with fidelity contracts and custody evidence.
Explore routesSupported
SPMailbox migration — any to any
Move mailboxes between Exchange Online tenants and across providers — Gmail, IMAP, on-premises Exchange (EWS), and PST/EML archives — with delta passes, per-mailbox status, signed fidelity contracts, and custody evidence.
Explore mailbox routesSupported · scope
TMSharePoint 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 OneDriveSupported · structure
Microsoft Teams
Assess and reconstruct teams and channels (supported), enable channel-message import (conditional — requires Teamwork.Migrate.All protected-API approval), and re-create private chats as full-history OneDrive transcripts (conditional — requires Chat.Read.All approval).
Open the Teams workflowsDelivery 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.
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.
Conditional
External dependency
Availability depends on Microsoft API approval, tenant state, licensing, or another service.
Controlled pilot
Topology-specific validation
Requires a representative lab or pilot, explicit acceptance criteria, and an agreed rollback plan.
Manual / planned
Outside automated scope
Assigned to native tooling, administrator remediation, or a future validated release.
Common questions
Workload migration questions, answered.
Can we migrate a single workload without buying the whole platform?
Yes. Identity, Microsoft 365 content, endpoint, and server operations are enabled and delivered under their own assessed scope. Self-service availability and controlled-pilot requirements vary by workflow.
Do workloads migrate in a fixed order?
Identity moves first because every other workload depends on resolvable target accounts. After identity, Exchange, SharePoint, OneDrive, and Teams sequencing follows the dependency and cutover constraints identified during assessment.
Is an Office 365 migration different from a Microsoft 365 migration?
No — Microsoft 365 is the current name for the suite formerly branded Office 365. An Office 365 migration and an M365 migration describe the same tenant-to-tenant program.
What evidence do we get per workload?
Every workload produces discovery findings, mapping validation, baseline and delta pass results, reconciliation exports, and audit records, so completion is demonstrated rather than assumed.