SharePoint vs OneDrive vs Teams: Where Should Files Go?

Of all the questions we get about Microsoft 365, one comes up more than any other: where is this file actually supposed to go? OneDrive, Teams and SharePoint all store documents, all sync, and all look interchangeable. They're not — and once you see the roles clearly, the answer takes about five seconds per file.

The confusion is Microsoft's fault, not yours. You're given three places that appear to do the same job, with no obvious guidance on which to use when. So people pick whichever is closest to hand, and a year later the company's documents are scattered across dozens of personal drives, half-abandoned teams and a SharePoint site nobody trusts.

Here's the mental model that fixes it: these aren't three competing filing cabinets. They're three roles in one system. OneDrive is for your personal working drafts. Teams is where a group actively collaborates. SharePoint is the organizational record. Get those roles right and search, permissions, versioning and offboarding all get dramatically easier. Get them wrong and every one of those becomes a slow-motion problem.

01OneDrive — your personal working drafts

Mine, for now

OneDrive for Business is your personal drive in Microsoft 365. It's tied to your account, follows you between devices, and is the right home for anything that is genuinely yours: early drafts, rough notes, working files that aren't ready for other eyes, prep for your own meetings.

The key property — and the one most teams miss — is that OneDrive belongs to a person, not the company. When that person leaves, their account is closed and their OneDrive goes with it. That's fine for drafts. It's a disaster for the only copy of a client contract.

02Teams — where the team works together

Ours, while we build it

Microsoft Teams is for active collaboration: the messy middle of a project, where a defined group is co-authoring documents, arguing in chat and iterating daily. The Files tab in each channel keeps the work next to the conversation about it, which is exactly where in-progress work should live.

Here's the part that unlocks everything: Teams doesn't store files at all. Every team has a SharePoint site behind it, and every file in a channel actually lives in that site's document library. The Files tab is a window into SharePoint. So "Teams vs SharePoint" is partly a false choice — the real question is whether a file belongs in a team's working site or in a curated, published library.

03SharePoint — the organizational record

Everyone's, for the long haul

SharePoint — the part of it beyond team sites — is where finished, official, published content lives: policies, handbooks, signed contracts, brand assets, templates, the intranet itself. It's structured deliberately, with proper libraries, metadata, permissions, version history and retention, so people can find the current truth without asking anyone.

Think of it as the difference between a workshop and a showroom. Teams is the workshop, full of sawdust and half-built things. SharePoint is the showroom: only the finished work goes in, and everything in it can be trusted.

---

The decision rule: me, we, everyone

Every file question collapses into one word:

• Me. Only I need this right now → OneDrive.
• We. A defined group is actively working on this → Teams (the relevant channel).
• Everyone. This is finished, official, or needed beyond the team → SharePoint.

Notice that files graduate. A proposal starts as "me" in OneDrive, becomes "we" the moment a colleague reviews it, and becomes "everyone" when it's signed and needs to be findable for years. Moving a file along that path isn't overhead — it's the system working as designed.

Where common files actually belong

Apply the rule to the files that cross your desk in a normal week and it looks like this:

The two mistakes that cause most of the mess

When we audit a Microsoft 365 tenant, the same two patterns show up over and over. Both are habits, not technical failures — which is good news, because habits can be fixed.

1. Everything lives in someone's personal OneDrive

This is the default failure mode, because OneDrive is the path of least resistance: it's right there, it syncs, and sharing a link feels like collaboration. But it means company documents are owned by individuals, permissions are a tangle of one-off sharing links, search can't see across the organization — and when the person who "owns" a document leaves, everyone scrambles to rescue files from a closing account. If a shared drive's worth of business records is sitting under one employee's name, that's not storage, it's a liability.

2. Channel sprawl

The opposite mistake: Teams gets adopted enthusiastically and with zero rules. Anyone can create a team, so everyone does. You end up with several near-identical marketing teams, project teams that outlived their projects years ago, and files scattered across so many channels that finding anything means asking in chat. Because every team is a SharePoint site under the hood, sprawl in Teams is sprawl in SharePoint — you're not avoiding the mess, you're just hiding it behind a different interface.

How governance makes the rule stick

The me/we/everyone rule is simple enough to teach in one meeting. What keeps it working six months later isn't the rule — it's a small amount of governance around it:

• Team provisioning: decide who can create teams, enforce a naming convention, and require an owner and a purpose for each one.
• Lifecycle: archive or expire teams when their project ends, so the workshop doesn't fill up with finished work.
• A publishing habit: when work is final, it moves from the team's site into the right SharePoint library — with the metadata that makes it findable.
• Permissions by role, not by person: access follows job function, so it survives every joiner, mover and leaver.
• One page of guidance: write the rule down, with your own examples, and put it where people will actually see it — on the intranet.

This is the unglamorous work that separates a Microsoft 365 tenant people trust from one they quietly route around. It's also the core of what we do: our SharePoint consulting engagements start with exactly this kind of information architecture and governance, and our Microsoft 365 integration work wires Teams, OneDrive and SharePoint into one coherent setup instead of three disconnected dumping grounds. And if you want more plain-English guides like this one, there's a growing pile on our blog.