SOURCE-CHECKED · BUSINESS DOCUMENTS
OneDrive vs SharePoint: move team files before a coworker leaves
Move team documents from work OneDrive to SharePoint with the right history, access and replacement links, including files left by a departing employee.
Put operating documents that the team must maintain in its SharePoint libraries. If those files currently live in a coworker’s work OneDrive, move them while authorized access is available, preserve the history the team needs, and replace the links people use. Personal drafts can stay in the individual’s library.
This guide covers a move within the same Microsoft 365 organization. It does not cover personal OneDrive accounts or moves between organizations.
Find where the files live
A folder that appears in the OneDrive sync app is not necessarily stored in someone’s OneDrive. The app syncs files from both OneDrive and SharePoint. Check the file’s web location before treating a desktop folder name or icon as evidence of its owner.
Microsoft describes OneDrive as the place for an individual’s files and new private work, and SharePoint libraries as shared places for team files. In a group-connected team site, membership is managed through the Microsoft 365 group. Files in a standard Teams channel use the associated SharePoint site; private and shared channels have separate sites. These distinctions help you choose the destination that matches the file’s intended readers. Microsoft’s file collaboration guidance
Map each file before moving it
A single “team files” folder is too broad for this example. The onboarding procedure should be editable by team members, while the staffing workbook should be limited to managers. The welcome PDF needs a named guest who can view it. A personal scratch draft has no team destination.
| Example file in a coworker’s work OneDrive | Proposed destination | Intended access | Required history or value |
|---|---|---|---|
onboarding-checklist.docx |
Team Operations library | Team members edit | Three versions; Priority=High |
welcome.pdf |
Partner documents library | Named guest views | One version required |
staffing.xlsx |
Managers restricted library | Managers edit only | Five versions |
scratch-notes.docx |
Stays in personal OneDrive | Author only | No team transfer |
The downloadable team-file transition CSV contains this illustrative plan, including each selected operation and its expected documented or reasoned outcome. For example, a one-version approved PDF can use Copy to; the three-version editable procedure needs Move to and a compatible destination. The version counts are example requirements, not Microsoft minimums. Actual URLs and observed results are blank, with NOT_RUN status.
Use it as a worksheet, not an import file. Replace the illustrative filenames and counts with your own inventory. Keep the selected operation, expected outcome and observed result separate: a documented Move to rule cannot establish that your particular transfer has completed.
Move the procedure with its history and column value
For the onboarding checklist, first confirm that the destination is the team’s intended library and that it has a column able to hold Priority=High. The required value needs a destination before the move, followed by a value check afterward. Microsoft says only supported properties are preserved when moving to a different destination, and associated values for managed metadata are not retained. A lower version limit at the destination can also produce a warning about lost versions. Microsoft’s OneDrive-to-SharePoint move instructions; Microsoft’s SharePoint move and copy guidance
In the modern web interface, select the file, choose Move to, find the destination under Quick Access or More places, and select Move here. If the expected site is missing, Microsoft suggests pinning it to Quick Access; tenant restrictions can also affect which sites appear. Resolve the destination before selecting another site simply because it is visible. Microsoft’s OneDrive-to-SharePoint move instructions
For this procedure, inspect the destination’s version history and confirm that Priority still reads High. Microsoft’s Move to guidance says a move transfers version history, while Copy to takes only the latest version. During a move, the source remains until the operation completes; it then goes to the source recycle bin. Do not treat the initial presence of a source file as proof that a move failed. Microsoft’s SharePoint move and copy guidance
The welcome PDF calls for a separate choice. If one version is sufficient, copying an approved PDF may be reasonable. Decide which location becomes the authoritative copy and stop parallel edits before replacing the email link. Otherwise, two live locations can leave the team unsure which PDF to send. Keep the staffing workbook out of the broadly editable procedure library: its destination and manager access need separate verification.
Share each destination for its audience
Moving a file and granting access are separate tasks. At each destination, use Manage access to review direct access and existing links, then create the link or invitation that matches the manifest. Microsoft’s sharing guidance
For the procedure index, People with existing access works when the team members already have permission; that link grants no new access. For the welcome PDF, open Share, select Can view, open Link settings, choose People you choose, apply it, add the guest’s email and copy the link. This is the named-recipient option also described as “Specific people” in Microsoft’s administrator guidance. An organization link excludes external guests; Anyone can be forwarded. Share the intended PDF instead of the team’s master folder. Microsoft’s sharing instructions
A guest’s denial can also come from sharing controls beyond the link itself. Microsoft says the tenant and site settings combine, with the more restrictive setting governing external sharing. Guest access is a separate question from team membership. If the named guest cannot open the PDF, check the link recipient and the applicable sharing settings before widening access. Microsoft’s external sharing overview; Microsoft’s sharing guidance
For staffing.xlsx, verify both sides of the boundary: an intended manager can edit it, and an ordinary team member cannot open it. A successful preview from your own administrator account does not establish either recipient result.
Replace links where work happens
The example manifest names three places that need attention: the procedure index and pinned Teams post for the checklist, and the client welcome email template for the PDF. A managers’ bookmark may also need updating. Record each old link location, place the new destination link there, and test it as the person who will use it.
Do not assume every old link will break or every old link will keep working. Its behavior may vary. Check the old and new paths separately with an intended team member, the named guest where relevant, and an account that should be denied. Record what each account actually reached, including whether it had view or edit access. Only then change that worksheet row from NOT_RUN to a result supported by the trial.
For the procedure, the complete transition record should identify its destination URL, the required versions, the surviving Priority value, and the index and pinned post that now use that URL. For the PDF, record the named recipient and view permission. For the staffing workbook, include the denied ordinary member. Those records answer different questions; a single “moved” checkbox cannot represent all of them.
Act before account deletion
Do this work while the team still has authorized access to the coworker’s business files. Blocking sign-in or removing a license is not the event that starts Microsoft’s OneDrive deletion cleanup; deleting the Microsoft Entra account is. Microsoft describes a default 30-day retention period that an organization can configure, so “we have 30 days” is not a dependable deadline without checking the tenant’s settings. Retention policies and holds can also change timing. Microsoft’s OneDrive retention and deletion guidance
Manager access is automatically delegated by default, but the setting should be checked. A secondary owner can receive access when no manager is specified. If delegation is disabled or both are missing, there may be no automatic access warning. Microsoft also describes a 93-day recycle-bin period after deletion, during which shared content is unavailable, and a separate 93rd-day archival path for unlicensed accounts. These are reasons to establish the real account state and deadline, not reasons to defer the move. Microsoft’s OneDrive retention and deletion guidance
If the coworker has already left, ask an administrator for authorized access to the legitimate business files and confirm the actual deadline. Avoid granting the whole team access to the person’s entire private OneDrive. Use authorized reader accounts to test the destination; deleting an account or removing access is not a test step.
Common questions
Does a OneDrive icon mean the file belongs to the coworker?
No. The OneDrive sync app also displays synced SharePoint content. Check the file’s web location to identify its store. Microsoft’s file collaboration guidance
Why can’t the guest open the welcome PDF?
Check the guest’s email under People you choose and confirm view access. Then check the organization and site’s external-sharing settings. An organization link alone excludes the guest. Microsoft’s sharing guidance; Microsoft’s external sharing overview
What if the intended SharePoint site is missing?
Open the intended site and pin it to Quick Access, then return to the Move to dialog. If no other sites are available, have the administrator check cross-site move restrictions. A similarly named site is not a substitute: compare the actual destination before moving the procedure. Microsoft move instructions
Microsoft documentation checked October 7, 2026. These are documented instructions and an illustrative transfer analysis; no tenant move or recipient test was performed.