SharePoint or OneDrive: The Question That Decides It
They are the same platform with different ownership. That one difference determines where every document should live.
Rajiv KumarSeptember 12, 20225 min read
OneDrive for Business is a SharePoint site collection owned by one person. Everything practical follows from that — including why team documents stored in personal OneDrive disappear when someone leaves.
"Should this go in SharePoint or OneDrive?" is asked constantly and answered inconsistently, which is why organisations end up with critical documents in someone's personal storage and personal drafts cluttering a team site.
The technical answer is straightforward, and it is not about features. SharePoint and OneDrive are the same platform. OneDrive for Business is a SharePoint site collection with a single owner. Everything about how they behave follows from that one fact.
The same engine, different ownership
When a user is licensed, they get a personal site collection. It has a document library, version history, sharing controls and search — because it is SharePoint. What differs is who owns it: one named individual, rather than a group.
That ownership difference produces every practical distinction:
| OneDrive for Business | SharePoint site | |
|---|---|---|
| Owner | One person | A group or team |
| Default access | Owner only | Site members |
| When the owner leaves | Retention period, then deletion | Unaffected |
| Metadata columns | Not typically used | Core capability |
| Content types | Not used | Available |
| Retention and records | Applied to the individual | Applied to the site |
| Surfaced in Teams | Only via chat file sharing | Directly as a channel tab |
The question that actually decides it
Not "is this important?" or "will others need it?" — both lead people astray. The question is:
If this person left the organisation tomorrow, should this document leave with them?
If no, it belongs in SharePoint. That is the whole rule, and it holds up because it is about ownership rather than sensitivity or size.
A confidential HR policy belongs in SharePoint, because the organisation owns it even though few people should read it. A rough draft of a presentation belongs in OneDrive, because it is genuinely the author's working material, even if it will eventually be shared.
What this means in practice
OneDrive is right for work in progress before it has an audience, personal notes, drafts, and material genuinely belonging to one person's role.
SharePoint is right for anything a team relies on, anything with a review or approval process, anything subject to retention, and anything that must survive staff changes.
The failure mode nobody plans for
The reason this matters is departure. When an employee leaves and their licence is removed, their OneDrive enters a retention period and is then deleted.
Organisations discover the consequences at the worst time. The process documentation that one person maintained; the spreadsheet that fed a monthly report; the folder the whole team had a link to. All of it lived in personal storage because it started as one person's work and was never moved.
Two mitigations are worth having in place before you need them:
- Configure OneDrive access delegation. SharePoint admin settings let you nominate a manager or secondary owner to receive access when an account is deleted. This is worth configuring in every tenant.
- Set a retention policy on OneDrive. Retention preserves content beyond deletion, giving a genuine window to recover it rather than a scramble.
Sharing behaves differently, and that is the point
A OneDrive file shared with twelve people is not a team document. It is a personal file with twelve permissions attached, and it remains dependent on the owner's account. The link works today and stops working when they leave.
A SharePoint library shared with the same twelve people is a team asset whose permissions come from membership. Someone joining the team gets access automatically. Someone leaving loses it. The document persists regardless.
This is why "but I shared it with everyone" is not a substitute for putting it in the right place.
Common mistakes and better practice
- Using OneDrive as the team drive. The most common and most damaging pattern. It works until the owner leaves.
- Choosing by sensitivity. Confidential organisational documents belong in SharePoint with restricted permissions, not in personal storage.
- Sharing a OneDrive folder with a whole department. Create a site. Membership is what makes access durable.
- Not configuring access delegation. Do this before the first departure, not after.
- Moving files by download and re-upload. This loses version history and metadata. Use Move to, which preserves them.
- Assuming Teams files are in OneDrive. Files in a Teams channel live in the team's SharePoint site. Files shared in a private chat live in the sender's OneDrive — a genuinely important distinction.
Troubleshooting
| Symptom | Cause | Resolution |
|---|---|---|
| Shared link stopped working after a colleague left | File was in their OneDrive | Recover via access delegation or retention, then move it to a site |
| Files in a Teams chat cannot be found in the team site | Chat files live in the sender's OneDrive | Expected; share through the channel for team-owned files |
| Version history lost after reorganising | Moved by download and re-upload | Use Move to, which preserves history |
| Retention policy does not appear to cover a document | Policy scoped to SharePoint, file is in OneDrive | Extend the policy scope, or move the content |
| Sync client stops syncing a folder | Access removed, or the source was deleted | Confirm the source still exists and permissions still apply |
Frequently asked questions
Is OneDrive really just SharePoint?
Architecturally, yes. OneDrive for Business is a SharePoint site collection provisioned per user. The interface and defaults differ; the underlying platform does not.
What happens to OneDrive content when someone leaves?
It enters a retention period after the licence is removed and is then deleted. Access delegation and retention policies both extend the recovery window, but only if configured beforehand.
Where do Teams files actually live?
Channel files are in the team's SharePoint site. Files shared in a private chat are in the sender's OneDrive. This catches people out regularly.
Can content be moved without losing version history?
Yes. The Move to command preserves version history and metadata. Downloading and re-uploading does not.
Should personal drafts be in SharePoint for safety?
No. Genuine work in progress belongs in OneDrive. Moving everything into team sites makes them harder to navigate and buries the documents that matter.
A rule that survives contact with reality
Feature comparisons do not settle this question, because the platforms share almost all their features. Ownership settles it.
Ask whether the document should leave with the person. If it should not, it belongs somewhere the organisation owns. Applied consistently, that one question prevents the departure-day scramble that most organisations experience at least once.
