SharePoint vs OneDrive, and where the file actually lives

Here is the thing most comparison articles get wrong, and it matters: OneDrive for Business is SharePoint. Same service, same storage platform, same sync client, same permission model underneath. Microsoft gives every licensed person a personal SharePoint site and calls it OneDrive. That is the whole technical difference.

So when somebody asks which one to use, they are not really asking a technical question. They are asking an ownership question, and nobody has told them that is what they are asking.

The actual difference

A OneDrive is owned by a person. A SharePoint site is owned by a site, which in practice means a group of people with named owners.

That sounds like a small distinction until somebody resigns. When an account is deleted, its OneDrive goes into a retention window, typically thirty days unless you have changed it, and then the content is gone. Not archived somewhere clever. Gone. Every file in it, including the three spreadsheets the finance process quietly depended on, and including the folder somebody shared with four colleagues who had no idea whose drive they were working in.

A SharePoint site does not care who left. Membership changes, the container does not.

Why so much ends up in the wrong place

Not because people are careless. Because OneDrive is the path of least resistance and SharePoint, as most tenants have it configured, is not.

Saving to OneDrive takes zero decisions. Saving to SharePoint takes at least one: which site? And if the answer to that is unclear, because there are forty sites with names like "Team Site" and "Project", or because site creation was locked down two years ago and nobody has created one since, then the honest answer for the person with a file in front of them is "I will sort this out later".

They do not sort it out later. That is not a character flaw, it is how work goes.

If the right answer takes more decisions than the wrong one, the wrong one is your actual policy, whatever the document says.

A rule you can give people in one line

Here is the version we give clients, and it survives contact with real users because it is short:

If the work would continue without you, the file belongs in SharePoint. If it would not, OneDrive is fine.

That is it. It gets the common cases right. A proposal draft nobody else has seen: OneDrive. The same proposal once a colleague is editing it: SharePoint. Your notes from a client call: OneDrive, until somebody else needs them, at which point they were never really yours.

For the cases it does not settle, the three questions below, answered in order, do.

The sharing trap

The failure we see most often is not files in the wrong place. It is files in the right place shared the wrong way.

A SharePoint site has membership. You are in the group or you are not, and an owner can answer the question "who can see this" in about five seconds. A sharing link has none of that. Links accumulate silently, they survive the reason they were created, and six months later nobody can tell you who has access to the client folder without exporting a report.

Three settings worth checking this week, in order of how often we find them wrong:

• Default link type. If "Anyone with the link" is the default in your tenant, change it. Almost nobody wants anonymous links as the default, and almost everybody has them.
• Link expiry. Anonymous and organisation-wide links should expire. Thirty days is a reasonable starting point for external sharing, and you can extend it for the sites that genuinely need longer.
• Who can share. On the sites that hold client material, restrict sharing to owners. The friction is the point.

None of these are hard. All three need somebody to decide, which is why they are usually still at the default.

What about Teams?

Every Microsoft 365 group backed Team has a SharePoint site behind it, and the Files tab in a channel is a folder in that site. So "should this go in Teams or SharePoint" is the same non-question as the one in the title. It is already in SharePoint.

What matters is that a Team is a decent default container for an ongoing group of people with a shared purpose, and a bad container for a short project with three participants, because you will end up with four hundred Teams and no way to tell which ones are live. If you do not have a naming convention and an expiry policy for Teams, that is a more urgent problem than anything in this article.

What to do with the files that are already in the wrong place

Do not announce a migration. Migrations of this kind fail because they ask everybody to change everything at once, and the people with the most files in OneDrive are the people with the least time.

What works better:

1. 1.Find the shared ones first. Run a report of OneDrive files shared with more than two internal people. Those are the ones that are already functioning as team files. There are usually fewer than you fear.
2. 2.Give them somewhere to go. Create the sites before you ask anyone to move anything. An instruction to move a file to a site that does not exist yet is an instruction to do nothing.
3. 3.Move those, then stop. The long tail of genuinely personal files can stay where it is. It is where it belongs.
4. 4.Fix the leaver process. Whatever else you do, make sure that when somebody leaves, their OneDrive is reviewed by a human before the retention clock runs out. This single step has recovered more business-critical files than every migration we have run.

The one-sentence version

OneDrive is where a file lives while it belongs to one person; SharePoint is where it lives once it belongs to the work. Everything else, the sync client, the storage quota, the mobile app, is the same product.

If you are not sure which of your files are in which category, that is answerable in an afternoon with a sharing report and somebody willing to read it.