SharePoint, a shared drive or Dropbox: where should company files live?

The deciding fact is usually money you have already spent. Most Microsoft 365 business plans include SharePoint and OneDrive storage, so a separate file server or a Dropbox subscription is a second system you pay for, back up and secure. That second system has to earn its place. Sometimes it does.

How the three compare

What the table can't show is how each one fails. A shared drive fails quietly: someone overwrites a file, nobody notices for a fortnight, and recovery depends on whether last month's backup actually ran. Dropbox fails at the edges: a contractor still holds a link to a folder from a finished project because nobody reviews a second sharing system. SharePoint fails when it is set up like a shared drive, with one giant library and permissions broken on hundreds of folders.

Where the alternatives still win

Be honest about these before you migrate.

• Large CAD and BIM sets on site networks. Drawing sets with linked references and very large models often open faster from a local server than from synced cloud storage. Many construction and engineering firms keep a server, or a dedicated tool, for design files and move everything else to SharePoint.
• Software that needs a drive letter. Some accounting, estimating and design packages expect a mapped path. Check each one before the old drive is switched off.
• Heavy sharing with outsiders who live in Dropbox. If your clients or consultants send everything through Dropbox, a shared folder for that exchange may be simpler than forcing them into guest accounts.

None of these is a reason to keep the whole company on a second system. They are reasons to carve out one library, one server share or one exchange folder, and say so in writing.

Where SharePoint earns its keep

For everyday documents (policies, project files, HR forms, board papers, client folders) SharePoint does three things the others can't easily match inside a Microsoft 365 business. Permissions follow the same accounts and groups as email and Teams, so a leaver loses access to files when their account is disabled. A Teams channel's Files tab is a SharePoint library, so the folder people already chat beside is the official copy. And search, approvals and Power Automate flows can work on those files without another connector.

Three SharePoint permission mistakes covers the structure that avoids this.

What migration actually involves

The copy itself is the easy part: Microsoft's free migration tools move the files and their metadata, though a file server has no version history to bring. The work is in the decisions before it.

Pruning is where people save the most. A shared drive that has run for ten years typically holds folders nobody has opened since they were created; moving them only moves the clutter. Agree a cut-over date per team, make the old location read-only on that date, and keep it available for a fixed period so nobody runs two copies.

For a 50–500 person business, plan it team by team over weeks rather than in one weekend. If you are also building an intranet, do the document structure first; our SharePoint intranet service treats them as one design.

What to do next

List every place company files live today, including personal Dropbox and USB drives. Mark the ones with a genuine reason to stay (large models, drive-letter software, outside partners) and plan the rest into SharePoint, one team at a time.