Sites and OneDrive
- File counts and total bytes
- Libraries, lists, and account identity
- Source URLs and persisted assessment assets
SharePoint and OneDrive
A SharePoint migration tool for assessed content scope.
The SharePoint migration tool 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. It works as a SharePoint to SharePoint migration tool between tenants and as a OneDrive migration tool for account-level document migration inside the same assessed scope. Certified content routes also cover OneDrive to Zoho WorkDrive migration, Google Drive to Zoho WorkDrive, Zoho WorkDrive to Google Drive migration, and Zoho WorkDrive to OneDrive migration.
Supported · scope Graph-based content transferSupported sites, document libraries, generic lists, and mapped OneDrive accounts can be migrated. Full-fidelity SharePoint application modernization, sharing links, pages, custom forms, workflows, extensions, and tenant governance remain separate work.
BridgeAD Cloud WorkloadsContent migration workspace
Content movement with visible progress and exceptionsSites and drives, transfer progress, mapped permissions, retries, delta passes, exceptions, and validation stay visible throughout delivery.
Product view · synthetic demonstration dataOperator experience
Turn assessment inventory into an executable scope.
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.
- Source and destination connection health and Graph consent checks
- Assessment runs with site, OneDrive, file, volume, path, and sharing findings
- Search, readiness, volume, department, license, and account filters
- Explicit source-to-destination site and OneDrive mappings
- Item progress, retries, delta and final cutover passes
- CSV assessment, validation, and completion evidence
Capability scope
Apply the right fidelity expectation to each content type.
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. |
| Google Drive (source and target) | Supported | Migrates Google Drive content into OneDrive or SharePoint, and OneDrive content into Google Drive: org-wide discovery of My Drives and Shared Drives via a customer service account with domain-wide delegation, resumable delta enumeration, Docs/Sheets/Slides export-conversion to Office formats, and write-back with folder provisioning, conflict policy, and timestamp preservation. | Both directions mail‑route-style certified against a live Workspace org. Export conversion is a disclosed transformation; ACLs, SharePoint sites/lists, and version history are not carried in either direction and must be re-established at the destination. |
| Zoho WorkDrive (source and target) | Supported | Migrates Zoho WorkDrive content into OneDrive or SharePoint, and OneDrive content into WorkDrive My Folders or Team Folders: discovery via a customer OAuth client, resumable folder-tree enumeration, streamed downloads, and write-back with folder provisioning and conflict handling. | Both directions certified against a live WorkDrive org. WorkDrive exposes no change feed, so re-runs re-enumerate under the job's conflict policy; WorkDrive-native documents (Writer/Sheet/Show) are reported per item; ACLs, SharePoint sites/lists, and version history are not carried in either direction. |
| 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 | Supported · 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 | Supported · 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 | Supported · 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 | Conditional · 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. |
Assessment evidence
Find migration blockers before data transfer.
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.
Transfer constraints
- Long paths and large files
- Unsupported or manual content categories
- Destination mapping and provisioning gaps
Sharing and governance
- Shared-item counts and sample findings
- Links that need destination recreation
- Manual pages, workflows, apps, and controls
Prerequisites
Prepare identities, destinations, and permissions first.
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.
Graph application and consent
- Source discovery and content-read roles granted
- Destination site, file, list, and permission roles granted
- Connection health and service-principal assignments checked
Mappings and provisioning
- Destination users and groups exist
- OneDrive accounts are licensed and provisioned
- Destination site URLs and naming rules are approved
Scope and change plan
- Assessment reviewed and migration scope frozen
- Conflict, version, metadata, and permission options agreed
- Baseline, delta, freeze, validation, and support owners assigned
Certified content routes
Migrate content between OneDrive, SharePoint, Google Drive, and Zoho WorkDrive.
Drive-content routes are certified against live organisations in both directions before they launch. The qualifications below are part of each route's published scope.
| Route | Status | Scope qualification |
|---|---|---|
| OneDrive to Zoho WorkDrive migration | Certified | Writes into WorkDrive My Folders or Team Folders. WorkDrive has no change feed — re-runs re-enumerate under the job's conflict policy. ACLs and version history do not carry. |
| Zoho WorkDrive to OneDrive migration | Certified | Discovery via the customer's own OAuth client, resumable enumeration, streamed downloads. WorkDrive-native documents (Writer/Sheet/Show) are reported per item; version history does not carry. |
| Google Drive to Zoho WorkDrive | Certified | Runs as two certified stages in one programme — Google Drive → OneDrive, then OneDrive → Zoho WorkDrive — each under its own route qualifications. Docs/Sheets/Slides export-convert to Office formats in the first stage. |
| Zoho WorkDrive to Google Drive migration | Certified | Same two-stage certified path in reverse — Zoho WorkDrive → OneDrive, then OneDrive → Google Drive — with timestamp preservation and conflict policy on each stage. |
| Google Drive ↔ OneDrive / SharePoint | Certified | Org-wide My Drive and Shared Drive discovery via a customer service account with domain-wide delegation, changes-API delta anchor, and export-conversion of Docs/Sheets/Slides. Google ACLs and version history do not carry; SharePoint sites and lists are drive-content scope only. |
Migration workflow
Use assessment state to drive each pass.
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.
Assess
Inventory sites, OneDrive accounts, volume, paths, shared items, lists, and readiness findings.
Freeze scope
Filter or explicitly select assets, map destinations, validate accounts, and persist the approved definition.
Baseline
Provision targets and copy supported content, versions, metadata, lists, and mapped permissions.
Delta and cutover
Resume from Graph state, copy changes, enforce the agreed source freeze, and complete the final pass.
Reconcile
Compare counters, review skipped files and principals, export results, and approve remediation or sign-off.
Delivery boundaries
Separate content transfer from site modernization.
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.
Supported content path
- Sites, libraries, folders, files, and mapped OneDrive
- Configurable metadata, recent versions, and conflicts
- Supported generic lists and mapped permissions
Site application fidelity
- Modern/classic pages, navigation, themes, and templates
- Custom lists, Power Automate, forms, and workflows
- SPFx, third-party apps, search, and solution integrations
Sharing and governance
- Anonymous and organization-wide sharing links
- Purview labels, retention, DLP, and eDiscovery
- Hub, external sharing, access review, and lifecycle policy
Frequently asked questions
SharePoint and OneDrive migration questions
How is the migration scope selected?
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.
Can BridgeAD resume a large transfer?
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.
Are all SharePoint lists supported?
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.
Are sharing links preserved?
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.
How is a final cutover pass different?
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.
Related services
Coordinate collaboration dependencies.
Teams channel files and recordings depend on SharePoint and OneDrive, while every permission and personal drive depends on destination identity readiness.