"Half our client deliverables live in someone's OneDrive, and nobody else knows which folder." That single sentence, heard in some form at almost every mid-size organisation, is the reason OneDrive to SharePoint consolidation projects exist.
OneDrive for Business is built for individual work: drafts, personal notes, files in progress before they are ready to share. It is not built for team ownership. When project folders, client records, or department archives end up parked in a single person's OneDrive, the organisation loses continuity the moment that person changes role, goes on leave, or leaves the company. This guide walks through moving that content into a properly governed SharePoint Online team site.
What is OneDrive to SharePoint migration?
OneDrive to SharePoint migration is the process of relocating files and folders out of an individual's personal OneDrive storage and into a shared SharePoint Online site, where they become subject to group permissions, library structure, and retention policy rather than one person's account settings.
Step 1: Inventory before you touch anything
Before mapping a single folder, get a clear picture of what actually exists. Ask each affected user, or pull a report, covering:
- Total storage consumed per OneDrive account.
- Top-level folder structure and rough purpose of each folder.
- Any folders already shared with other staff, since those are the strongest signal that the content is really team content.
- File age and last-modified date, to separate active work from long-dormant archives.
The OneDrive usage reports in the Microsoft 365 admin center, or a script against the Microsoft Graph API, can produce this inventory across multiple accounts in one pass, rather than opening each account manually.
Step 2: Map folders to destination sites and libraries
This is the step most migrations rush, and the one that determines whether the result actually improves on the OneDrive mess. Resist the temptation to migrate each user's OneDrive as a single folder dropped into a library. Instead, group content by what it is, not by who currently holds it.
| OneDrive folder pattern | Better destination |
|---|---|
| "Client X" project folder | Client X site, Documents library |
| "Team templates" folder | Shared team site, Templates library |
| "Old projects" archive folder | An archive site, or Microsoft 365 Archive if the tenant has it enabled |
| Genuinely personal drafts | Left in OneDrive; not migrated |
Not everything in a OneDrive account needs to move. Genuine drafts and personal working files can stay exactly where they are.
Step 3: Run the move with metadata intact
A copy-paste through File Explorer or a browser download-and-reupload strips created-by and modified-by metadata, replacing it with the migrating admin's identity and today's date. That destroys the audit trail on every file. Use a migration approach, whether scripted against the Microsoft Graph API or a dedicated OneDrive migration tool, that explicitly preserves original author and timestamp metadata instead of resetting it, so the destination library reflects who actually created and last touched each file.
- Connect to the source OneDrive account and the destination SharePoint site.
- Select the mapped folder (from Step 2) as the source scope.
- Choose the destination library and target folder.
- Run the transfer with metadata preservation enabled.
- Spot-check a sample of files at the destination for created-by and modified-date accuracy.
How does permission handling change between OneDrive and SharePoint?
OneDrive permissions are file- and folder-level sharing links tied to an individual owner. SharePoint permissions are typically managed through site groups (Owners, Members, Visitors) applied at the library or site level. After the move, sharing needs to be re-established through the destination site's groups rather than recreated as individual file links, which is both more secure and far easier to audit later.
Step 4: Decommission the source
Once the destination content is confirmed complete and the affected users have had a chance to verify nothing is missing, remove the migrated content from the source OneDrive account. Leaving both copies in place indefinitely creates confusion about which version is authoritative and doubles the storage footprint for content that only needs to exist once.
- Set a short grace period (one to two weeks) before deleting the OneDrive originals.
- Communicate the new SharePoint location clearly, including any bookmarks or shortcuts that need updating.
- Check for embedded links to the old OneDrive location in other SharePoint documents, list items, or Site Pages. ShareMaster's Replace Master can find and update broken links pointing at the retired location across those SharePoint sites; links inside emails or Teams chat messages sit outside SharePoint's content model and need to be fixed at the source instead.
Summary
OneDrive to SharePoint consolidation is less about the file transfer itself and more about the mapping decision in Step 2. Get the destination structure right, preserve metadata during the move, and clean up sharing links and the source copy afterward, and the result is content that survives staff turnover rather than depending on it.