SharePoint, OneDrive and file share migrations
Each scenario has its traps: accounts that change domain, OneDrive accounts the admin cannot open, file names SharePoint rejects. Pick yours to see the approach and what is preserved.
- SharePoint tenant to tenantSites, libraries and lists to another tenant, with versions, taxonomy and permissions, in several passes.
- OneDrive tenant to tenantOneDrive to OneDrive, or a departed employee’s OneDrive to a team site.
- File share to SharePointFile server or NAS to SharePoint or OneDrive, and back, with dates, authors and fixed file names.
- Restructure a tenantMerge, split or move libraries between sites in the same tenant, keeping their history.
- Mergers and acquisitionsAbsorb a subsidiary, carve out a divested business: SharePoint and OneDrive content in waves.
- Google Drive to SharePointMy Drive to OneDrive or SharePoint, Google Docs converted to Office formats.In development
Your case is not listed? A migration is always described as source and destination pairs: site, library, folder, OneDrive or file share. The features page shows what is kept for each combination.
Test it on your own tenant
The 14-day trial migrates 10% of every library, with versions, metadata and permissions. After you subscribe, an incremental run migrates the rest.