SharePoint vs Teams vs OneDrive: getting your file structure right

Ask five people in the same business where a file "lives" and you'll usually get five different answers, and none of them will mention SharePoint. That's the root of most of the mess: people think of OneDrive, Teams and SharePoint as three separate places to store things, when really there's one storage engine underneath and two different front doors onto it.

In short: SharePoint is the single storage and permissions engine underneath Microsoft 365; OneDrive is your personal SharePoint site, and a Team's Files tab is just a SharePoint document library with a chat interface on top. The rule that keeps it tidy: personal drafts stay in OneDrive, shared work moves into the relevant Team's SharePoint library rather than being shared from someone's OneDrive, and company-wide reference material lives on a dedicated SharePoint communication site with no Team attached. Build Teams around ongoing departments and functions, not one-off projects, and rely on consistent naming and metadata columns rather than deeply nested folders.

What's the mental model that actually holds up?

SharePoint is the file storage and permissions engine for almost everything in Microsoft 365. It's not a separate product you opt into, it's the plumbing.

OneDrive is your personal SharePoint site. When you save a file to OneDrive, it's sitting in a document library that belongs to you alone, with permissions that default to nobody else. It's the right place for drafts, personal notes, half-finished work, anything that isn't ready for other people to see or touch.

A Team's "Files" tab in any channel is not separate storage either. It's a document library on a SharePoint site that gets created automatically the moment you create the Team, wrapped in a Teams-friendly interface so it feels like chat has its own filing cabinet. Open that same library in a browser instead of the Teams app and you'll see the familiar SharePoint furniture: libraries, columns, permissions, version history. Same files, same storage, different window onto it.

Once that clicks, most of the "which app do I use" confusion resolves itself. The question isn't SharePoint vs Teams vs OneDrive. It's: is this mine and not ready to share (OneDrive), or does a team need to work on it together (the Team's SharePoint library, via the Files tab or the site directly), or is it reference material the whole company needs without needing a chat channel attached (a dedicated SharePoint site)?

Where does it usually go wrong?

The most common mistake is saving shared work in personal OneDrive. Someone drafts a proposal, keeps refining it there because that's where they started, and never moves it. Colleagues can't find it without being sent a link, search doesn't surface it for anyone else, and if that person leaves the business, access has to be manually untangled from their departing account rather than simply continuing under the team's ownership.

The second is creating a new Team for every project, however small. Each Team spins up its own SharePoint site, its own permission group, its own Planner, its own channels. Do that for every two-week piece of work and within a year you've got dozens of Teams nobody remembers the purpose of, permissions granted to people who've since moved roles, and search results scattered across sites that all sound similar. Fragmentation, not consolidation, is the actual outcome of "just make a new Team for it."

The third is the opposite problem: one channel's Files tab used for everything, forever, with no subfolders or structure. It starts fine with a handful of documents and becomes, within a few months, an unsearchable dumping ground where finding anything means scrolling and guessing.

How should you structure it instead?

A sane default looks like this. OneDrive stays personal: drafts, working notes, anything not yet fit to share. Once a document needs another person's input, it moves into the relevant Team's SharePoint library, not a link shared from someone's OneDrive.

Teams themselves get built around ongoing work areas, not one-off projects: a Team per department, function or standing client relationship, with channels underneath for the individual threads of work. Each channel's library gets a consistent folder structure from day one, agreed once and then reused, rather than reinvented by whoever happens to upload the first file.

Company-wide reference material, policies, templates, the employee handbook, onboarding documents, doesn't need a Team or a chat channel attached to it at all. It belongs on a dedicated SharePoint communication site that anyone can browse without needing to be added to a Team's membership.

Naming and metadata over folder depth

Once the top-level structure is right, the detail that keeps it usable is discipline in how files are named and tagged. Consistent naming conventions matter more than most people expect, and metadata columns (client, status, document type, financial year) do more useful work than another three levels of nested folders ever will. Search in SharePoint is genuinely good, but only once there's something consistent for it to search against. Deeply nested folders with inconsistent naming defeat search just as effectively as no structure at all.

Getting it right from the start

This is exactly the kind of thing that's cheap to fix on day one and expensive to unpick two years and several thousand files later. As part of our Microsoft 365 onboarding and migration work, we help businesses design an information architecture across SharePoint, Teams and OneDrive that people actually stick to, because it was built around how they work rather than dropped in as a generic template. If your current setup already feels like the mess described above, our free assessment is a good place to start putting it right. Find out more about our Microsoft 365 & Azure services.