Sites and OneDrive
- File counts and total bytes
- Libraries, lists, and account identity
- Source URLs and persisted assessment assets
BridgeAD discovers sites and OneDrive accounts, records readiness findings, freezes the approved scope, provisions destinations, transfers supported content through Microsoft Graph, maps resolvable permissions, and reconciles each migration item after baseline, delta, or cutover passes.
A migration scope is created from a persisted assessment run. Operators can include or exclude specific sites and OneDrive accounts, validate destination mappings, review aggregate file and byte volume, and freeze the selection before creating a job.
Illustrative values; the interface displays customer-specific assessment data.
The transfer engine operates on SharePoint drives, items, permissions, and supported generic lists. It does not claim that copying files recreates every site-level application or tenant governance control.
| Area | Status | BridgeAD handling | Important boundary |
|---|---|---|---|
| Sites and libraries | Supported | Discovers source sites, provisions or resolves destination sites, enumerates drives, and copies supported folders and files. | Site pages, navigation, themes, templates, SPFx extensions, and application-specific configuration require separate recreation or validation. |
| OneDrive accounts | Supported | Discovers OneDrive accounts and resolves each source UPN to an explicit or platform identity mapping before copying into the destination drive. | The destination identity and OneDrive must exist and be provisioned. Unmapped accounts are blocked or reported. |
| Large and resumable files | Supported | Uses Graph upload sessions for large content, bounded concurrency, retry handling, and persisted delta tokens for resumable enumeration. | Microsoft Graph and SharePoint service limits still apply. Unsupported content is surfaced as an item outcome. |
| Versions, metadata, and timestamps | Configurable | Can copy supported metadata, preserve available timestamps, and recreate a configured depth of recent version history. | Version depth is bounded and selected per job; unsupported fields and application metadata are not implied. |
| Conflicts | Configurable | Choose rename, overwrite, skip, or keep-newest behavior when a destination file already exists. | Keep-newest compares available source and destination modified timestamps; missing timestamps fall back to source overwrite. |
| Permissions | Mapped principals | Maps supported principals through BridgeAD object mappings, applies resolvable permissions, and records unresolved identities. | Anonymous and organization-wide sharing links are not copied. Tenant policies and access governance remain administrator owned. |
| Lists | Supported subset | Recreates supported generic lists and compatible column and item data selected in the job. | Complex apps, custom forms, workflows, lookups, unsupported field types, and solution-specific behavior require manual remediation. |
| Delta, cutover, and validation | Supported | Runs incremental passes from persisted Graph state, supports a final source-frozen cutover pass, and reconciles source and destination counters. | Cutover mode assumes change freeze ownership outside the tool. Mismatches and unresolved principals require sign-off decisions. |
The assessment persists inventory and findings so scope selection is based on known source state rather than estimates. Results can be reviewed in the product and exported for migration planning.
SharePoint and OneDrive permissions are identity-dependent. A content job should not start until destination principals, site mappings, OneDrive accounts, and Graph application roles are verifiably ready.
BridgeAD keeps assessment, scope, migration, and validation related so an operator can explain why an object was included, where it was mapped, what happened during transfer, and what remains unresolved.
Inventory sites, OneDrive accounts, volume, paths, shared items, lists, and readiness findings.
Filter or explicitly select assets, map destinations, validate accounts, and persist the approved definition.
Provision targets and copy supported content, versions, metadata, lists, and mapped permissions.
Resume from Graph state, copy changes, enforce the agreed source freeze, and complete the final pass.
Compare counters, review skipped files and principals, export results, and approve remediation or sign-off.
The migration plan should explicitly assign SharePoint application behavior and Microsoft Purview configuration. Those areas are tenant-scoped or solution-specific and cannot be inferred from a successful file copy.
A completed assessment becomes the source for a persisted scope. Operators can select all discovered objects, apply filters, or choose explicit sites and OneDrive accounts. Destination mappings and validation results are stored with the frozen scope.
Yes. Drive enumeration uses persisted Graph delta state, large files use upload sessions, and item state is recorded. Retries and later passes can continue without intentionally restarting every completed item.
No. BridgeAD handles a supported generic-list subset. Complex field types, custom forms, workflows, solution-backed lists, and application behavior require assessment and a separate remediation plan.
No. Assessment counts items with sharing links or non-inherited sharing and surfaces sample findings. Anonymous and organization-wide links are not portable as stable principals and must be recreated under destination governance.
The final pass is explicitly marked as a cutover pass and assumes the source is frozen read-only under the customer change plan. It uses the same resumable state, then records cutover completion for audit and evidence.
Teams channel files and recordings depend on SharePoint and OneDrive, while every permission and personal drive depends on destination identity readiness.