Put files in a SharePoint team site when the business needs a team to maintain them over time. Use OneDrive for an individual’s working material and occasional sharing. The useful question is who must be able to manage the file next month if its creator is unavailable.
This distinction concerns the working home of the file. It does not mean that every document should be visible to the whole company, or that sharing a OneDrive document is inherently wrong.
Choose by responsibility and audience
Microsoft describes OneDrive as individual storage and team sites as a home for regularly shared work with shared ownership. Both can support collaboration; neither location automatically supplies the right access rules. Microsoft’s file-storage guidance.
| Situation | Starting choice | Decision to document |
|---|---|---|
| An employee’s early draft, shared briefly for comments | OneDrive | When does it become a team record? |
| A department’s active procedures, templates or project files | SharePoint team site | Which team maintains the library and its membership? |
| A restricted finance or personnel collection | A separately restricted location | Who is authorized, and who periodically checks access? |
| Documents exchanged with one customer | A deliberately scoped collaboration location | Can that customer see only the intended material? |
| A finished record under a retention requirement | The organization’s approved records location | Which retention, deletion and access rules apply? |
These are starting choices, not instructions to move sensitive records without their owner’s approval. Your organization’s retention, contractual and information-classification requirements may determine the final location.
Teams is an interface, not one storage bucket
A file appearing in Teams does not tell you who controls its storage. Microsoft explains that files uploaded to a channel are stored in SharePoint, while a file uploaded into a chat is stored in the uploader’s OneDrive and shared with the conversation. A link to an existing file can simply point to its existing location. Check the actual location instead of assuming that posting a link transfers responsibility. Microsoft: file storage in Teams.
Consider an illustrative sales team. A salesperson uploads the quarterly pricing workbook to a group chat. Colleagues can edit it, so the arrangement feels like team storage. But the working copy is tied to that upload location. The team should identify its approved pricing library, decide which copy is authoritative and assign people to maintain it before changing links.
Make the handover explicit
For each important collection, record five things: its working location, accountable business owner, people who can manage access, intended readers/editors, and the process for archiving or retiring it. A department name alone is insufficient if nobody can approve membership changes.
Then ask a colleague other than the creator to perform a normal task using their own account. Can they find the authoritative copy, edit it if appropriate and identify the owner? Can an authorized site owner manage membership? These checks expose a fragile handover without disabling anyone’s account as an experiment.
Move deliberately and test the result
- Inventory dependencies. Note links in Teams, bookmarks, recurring reports, automation and shared folders. Identify retention restrictions before moving or deleting anything.
- Prepare the destination. Confirm the site, library, owner and access groups. Do not use a broad company-wide group to solve a narrow access problem.
- Choose the move method with IT. Verify how that method handles version history, links, permissions and any limits for the particular source and destination.
- Test with intended users. Open the destination, edit a permitted file and check a restricted item with an appropriate test account. Confirm important links and workflows.
- Retire competing copies carefully. Tell the team which copy is authoritative. Remove or archive the old copy only after the owner approves and applicable retention requirements are addressed.
Keep this decision separate from a full Microsoft 365 migration. You may only need to correct the home of a few shared collections. For help mapping file ownership within your Microsoft 365 setup, start with the current locations and the five-field handover record when discussing email and Microsoft 365 support.
By mjunaid for TX Computing. Sources checked November 7, 2026. The cover is a generated conceptual illustration, not a customer installation.