SharePoint, OneDrive or Teams: what goes where?

OneDrive is personal storage for your own drafts and working files. SharePoint is the business's storage for anything the organisation owns. Teams is a working surface that displays SharePoint content beside the conversation about it. One test settles most cases: if the business would need this document after you left, it does not belong in OneDrive.

The confusion is Microsoft's doing, not yours. Three products, overlapping interfaces, all syncing to the same folder icon in Windows Explorer, and no clear moment where anyone explains the difference. So people improvise, and the improvisation is predictable: everything ends up in OneDrive because it is the path of least resistance, and the business slowly builds its records inside individual staff members' personal storage.

That is the failure mode worth naming, because it is invisible until it is expensive. A business whose documents live in OneDrive has tied its records to people rather than to functions. When someone leaves, their OneDrive is retained briefly and then deleted, and recovering what the business needs becomes a scramble against a clock during a period when nobody is at their best. Even before that, the quiet cost is that nobody can find anything they did not personally create.

So the ownership test does the real work: would the business need this if the person left tomorrow? Client correspondence, project documents, contracts, procedures, quotes, designs, anything that constitutes a record. Yes means SharePoint, in a site with an owner and an access list. No means OneDrive is fine: half-finished drafts, personal notes, the expense receipts you are about to submit, the presentation you are still ashamed of.

Teams then sits on top of SharePoint rather than beside it. Every Team has a SharePoint site behind it, and the Files tab is a view of that site. Use Teams as the working surface where a conversation and its documents belong together, because that is where people already are and files next to the discussion actually get used. Drop into the SharePoint view when you need structure the Teams interface hides: multiple libraries, a landing page, metadata, or an area read more often than discussed.

One trap inside Teams deserves calling out because it undermines the whole model quietly. A file posted in a channel goes to that Team's SharePoint site, as expected. A file dropped into a one-to-one or group chat goes to the sender's OneDrive and is shared by link. It feels identical to the person sending it and it is not: that document is now personal content with permissions attached, and it will leave with them. If something matters, post it in a channel.

One more distinction is worth teaching because it prevents a specific and expensive confusion: syncing is not backing up. A synced folder in File Explorer looks exactly like local storage, which leads people to assume there are now two copies. There are not; there is one copy shown in two places, and a deletion or an encryption propagates to both within seconds. Microsoft protects the platform, and your content remains your responsibility, which is why an independent backup of SharePoint and OneDrive sits alongside all of this rather than being implied by it.

Making this stick is more about defaults than instruction. Two rules on one page will be read; a governance document will not. Set the structure so the right place is the obvious one, sync the important SharePoint libraries to people's machines so they appear in Explorer beside OneDrive, and make sure new starters are shown the pattern in their first week, because habits form immediately and are difficult to shift later.

New starters are where this is won or lost, and it costs ten minutes. Someone joining a business copies whatever they see in their first fortnight, so if nobody shows them the pattern they will default to saving in OneDrive because it is the folder with their name on it. Ten minutes during induction, showing where business documents live and why, is worth more than any amount of retraining a year later.

The honest caveat is that some scattering is inevitable and chasing perfection is a poor use of anyone's time. The goal is that the documents which matter, the ones a client, an auditor or a court might ask for, are consistently in business storage with an owner. If that is true, a certain amount of mess in personal drives is survivable. If it is not true, no amount of tidiness elsewhere helps. If you want the structure and the one-page rule set up together, call 1800 456 567.