Should you store files in Teams or SharePoint?

It is the same storage either way. Every Team has a SharePoint site behind it, and the Files tab in Teams is simply a view of that site's document library. So the question is not which one to store files in; it is how you structure the sites, who owns them and how permissions are set, which is where businesses actually go wrong.

This confuses people for a good reason: the two products look completely different and are marketed as if they were separate. Teams presents as a chat application with files attached. SharePoint presents as an intranet with document libraries. Underneath, when someone creates a Team, Microsoft 365 quietly creates a group, a mailbox, and a SharePoint site, and the Files tab points at that site. Save a document in Teams and it is in SharePoint. Open the same document in SharePoint and it appears in Teams. There is one copy.

Once that clicks, the practical guidance falls out easily. Use Teams as the working surface for anything with a conversation attached: an active project, a department's day-to-day, a client engagement with ongoing back-and-forth. People are already in Teams, and files sitting next to the discussion get used. Use the SharePoint view when you want structure the Teams interface does not show well: multiple libraries, metadata, document sets, a landing page, or a reference area that is read far more often than it is discussed.

The exception worth learning is OneDrive, which genuinely is separate storage rather than another view. OneDrive is personal: drafts, working files, things not yet shared. The test is ownership, not sensitivity. If the business would need the document after the person left, it does not belong in OneDrive, and that single sentence prevents most of the problems small businesses create for themselves. A related trap sits inside Teams itself: files attached to a chat rather than posted in a channel go to the sender's OneDrive, so a document that feels shared is actually personal content with a link handed out.

Now the structural mistake that causes most long-term pain, and it is common enough to be almost universal. Businesses migrating from a file server create one big SharePoint site and put a folder in it for each department, because that mirrors the old drive and feels safe. It is the wrong shape, because permissions in SharePoint are designed to be set per site, not per folder deep inside one. You end up managing a thicket of broken permission inheritance, nobody can see who has access to what, and every new arrangement is another exception. The right pattern is a site per meaningful area of work, each with its own owner and its own access list.

Ownership is the other half of the structure question and the half nobody assigns. Every Team and every site should have a named owner responsible for who can reach it and whether it is still needed. Sites without owners are where permissions drift, guests outlive their projects and sensitive material quietly becomes visible to more people than intended. Two named owners each is a sensible rule, so a departure never leaves an orphan.

Two operational points that matter more than the Teams-or-SharePoint question. First, backup: Microsoft protects the platform but your Teams and SharePoint content is your responsibility, and deleting a Team removes its site and files after a finite recovery window. We back client tenants up daily with Veeam to a separate data centre with thirty days of history, covering mail, files, Teams and SharePoint, precisely because the platform's own safety net is not one. Second, external sharing: the default settings determine whether staff can share anything with anyone by link, and that default deserves a deliberate decision rather than whatever it was on the day the tenant was created.

The honest caveat is that structure is easier to design than to change. Moving content between sites later breaks links, resets permissions and irritates everyone, so the hour spent agreeing the shape before a migration is worth several days afterwards. If you are still on a file server, that hour is the single most valuable part of the whole project. If you want the structure designed properly rather than copied across, call 1800 456 567.