Microsoft is really good at convincing businesses that SharePoint and OneDrive are the modern answer to everything. Sometimes they're right. Sometimes they're very wrong. Here's how to figure out which camp you're in before you make a decision you'll regret.
If you're paying for Microsoft 365, you've probably heard the pitch: move everything to SharePoint and OneDrive, get rid of your file server, save money on hardware, and enjoy seamless collaboration from anywhere. It sounds compelling. And for some businesses, it genuinely is the right move.
But we've also helped businesses migrate to SharePoint and then spend the next year fighting it — dealing with sync problems, confused staff, files that won't open properly, permission structures that make no sense, and performance issues that only show up when you're trying to open a 400MB file over a hotel Wi-Fi connection.
We've also watched businesses stick with aging file servers long past the point where they should have moved some things to the cloud — paying for hardware maintenance, dealing with access headaches for remote workers, and missing out on real collaboration features that SharePoint does genuinely well.
The honest answer isn't "file servers are old and you should switch" or "SharePoint is too complicated and you should avoid it." The honest answer is that these are different tools, good at different things, and the right choice depends entirely on how your business actually works. Let's break it down.
Let's give credit where it's due. SharePoint and OneDrive — used together as part of Microsoft 365 — are genuinely excellent for certain use cases.
If you have employees working from home, multiple office locations, or out in the field, cloud file storage is a real advantage. Files are available from any device, anywhere, without a VPN. Sharing a document with a client or vendor is a link, not an email attachment. For a team that's not always in the same room, this is meaningful.
Co-authoring in Word, Excel, and PowerPoint is one of SharePoint's legitimate strengths. Multiple people can work on the same document simultaneously, see each other's changes in real time, and leave comments for each other. If your team regularly collaborates on documents — marketing materials, proposals, reports — this is a genuine productivity gain over the old "email the file back and forth" model.
Cloud storage means Microsoft handles the hardware, redundancy, and availability. You're not responsible for the server, the drives, the backups of the file server itself, or what happens if the building floods. That's a real reduction in operational burden, especially for smaller businesses without dedicated IT staff.
SharePoint connects natively with Teams, Outlook, and the rest of the Microsoft 365 ecosystem. A document library can surface directly in a Teams channel. A shared calendar can sit alongside shared files. If your business runs heavily on Microsoft tools, this integration is genuine.
Here's what the Microsoft sales deck doesn't emphasize.
SharePoint and OneDrive work through sync clients that keep a local copy of files on each computer. For most documents, this is fine. For large files — CAD drawings, video projects, high-resolution image libraries, large database exports, design files — it's a disaster in progress. Syncing a 2GB file takes time, eats bandwidth, and the OneDrive client is not always graceful about conflicts or failures. We've seen businesses lose hours of work to sync conflicts they didn't realize had happened.
SharePoint has a sophisticated permission system. That's a polite way of saying it's complicated. Permissions can be set at the site level, the library level, the folder level, and the file level — and they interact with each other in ways that are not always intuitive. We regularly encounter SharePoint environments where nobody is entirely sure who has access to what, because permissions got set ad hoc over time by people who didn't fully understand the model. In contrast, a well-configured file server has a permission structure that any IT person can audit and understand in fifteen minutes.
Certain applications — particularly older line-of-business software, accounting packages, and specialty industry tools — expect to work with files on a traditional file system path (like \\server\shared) and don't work correctly, or at all, with SharePoint. If your business relies on any software that opens files directly rather than through a browser or a sync client, you need to test carefully before migrating. We've had clients discover this problem after the move, which is not a fun place to be.
This is one people get wrong regularly. Microsoft 365, including SharePoint and OneDrive, is not backed up by Microsoft. Microsoft provides redundancy (so the service doesn't go down), but they don't provide backup (so you can recover from user error, malicious deletion, or ransomware). If someone deletes a folder and doesn't notice for 93 days — Microsoft's default retention window — that data is gone. You need a third-party backup solution for your SharePoint data, full stop. This is the same issue we cover in our post on whether Microsoft 365 backs up your data (spoiler: it doesn't).
SharePoint sync clients do maintain local copies of files, so you're not completely dead if the internet goes out. But collaboration features, version history, and anything not yet synced requires connectivity. For businesses in areas with unreliable internet, or for operations where internet downtime would be a meaningful disruption, this is a real consideration.
File servers — whether they're Windows Server, Linux-based, or a NAS like TrueNAS — have been the workhorse of small business file storage for decades. And despite what you may have heard, they're not obsolete.
On a local network, a file server is fast. Genuinely fast. Opening a 500MB file from a local gigabit network is effectively instant. Doing the same thing through SharePoint involves sync delays, upload/download cycles, and application overhead that can make large-file workflows genuinely painful. For businesses working with large files regularly — video, design, engineering, medical imaging — this matters a lot.
File servers present files the way operating systems expect to see them. Every application that can open a file works with a file server. There are no compatibility surprises, no sync client misbehavior, no "this application doesn't support network paths" edge cases. It just works.
A well-configured Windows or Linux file server has folder permissions that are easy to understand, easy to audit, and easy to change. You can look at a folder and immediately see who has access to it. Onboarding a new employee means adding them to the right groups. Offboarding means removing them. It's not glamorous, but it's reliable.
If your internet goes out, your file server keeps working. For businesses where internet outages happen — either due to infrastructure reliability or geographic location — local file access is a genuine business continuity advantage.
With cloud storage, the more you store and the more users you have, the more you pay. A file server has a fixed hardware cost that doesn't scale with headcount. For businesses with large storage needs or a lot of users relative to what they store, the economics can favor on-premises significantly.
File servers aren't without their own challenges. Let's be honest about those too.
Getting to a file server from outside the office typically requires a VPN. VPNs work fine when they're properly configured — but they add friction, they need to be maintained, and they're another thing that can break. Remote workers who need file access frequently find it less seamless than cloud alternatives. If your team is mostly remote or frequently traveling, this is a meaningful headache.
The server needs to be maintained, backed up, powered, and eventually replaced. If it fails, you're dealing with it. This isn't an argument against file servers — it's a real cost and responsibility that needs to be budgeted for. If you're already managing a server for other reasons, adding file serving to it is often negligible. If a file server would be your only reason to have a server, that changes the math.
Traditional file servers don't have co-authoring, version history with restore, or integrated commenting. Two people trying to edit the same file at the same time will lock each other out or create conflicting copies. If your team frequently collaborates on documents simultaneously, a file server alone doesn't solve that.
Most businesses shouldn't be choosing between SharePoint and a file server. They should be thinking about which types of files and workflows belong where — and many businesses end up using both.
Here's a practical framework for thinking through the decision:
And one more thing: if you already have Microsoft 365 licenses, you're already paying for SharePoint and OneDrive. You're not "wasting money" by also having a file server for the workflows where it fits better. The goal is to match the tool to the job, not to eliminate hardware because it feels old-fashioned.
If after thinking through all of this you've decided SharePoint makes sense for your business, we want to save you from a few common migration mistakes.
Don't just drag-and-drop everything. A file server that's been around for years often has deeply nested folder structures, inconsistent naming, files that haven't been touched in a decade, and permission structures that make no sense anymore. Migrating that structure wholesale into SharePoint means you've traded one mess for a different mess in a new location. Take the migration as an opportunity to clean up — consolidate, archive old content, simplify the structure.
SharePoint's 400-character path limit is real. If your file server has very deep folder structures with long names, you'll hit SharePoint's path length limit during migration. Files that can't migrate just get skipped, and you might not notice. Audit your longest paths before you start.
Plan for the transition period. During and after migration, people will look for files in the old location out of habit. A clear communication plan and a period of dual availability (read-only access to the old server while everyone gets used to the new location) reduces the chaos significantly.
Set up backup before you move anything. Remember: Microsoft doesn't back up your SharePoint data. Before you migrate a single file, make sure you have a third-party backup solution in place. We can't stress this enough.
If you're navigating a more complex transition — whether it's moving to SharePoint, moving between IT providers, or rethinking your overall infrastructure — our guide on surviving an IT provider transition covers the change management side of things in detail.
After 30+ years of helping small businesses with this exact question, here's the honest answer we give most of our clients:
If you have 20 or fewer employees, a mostly in-office team, and your business relies on any specialty software that opens files directly, a NAS (network attached storage device running something like TrueNAS) is probably still your best primary file storage. It's fast, reliable, straightforward to manage, and doesn't have the complexity overhead of SharePoint. Use OneDrive for individual users' personal work files and the documents that genuinely benefit from cloud access. You can have both.
If you have a distributed team, significant remote work, and your files are primarily standard Office documents and PDFs, SharePoint and OneDrive is probably the right primary home. Just budget for a proper backup solution and don't let the permission structure grow organically — set it up intentionally from the beginning.
If you're in the middle — some in-office, some remote, a mix of file types — a hybrid approach often makes the most sense. Some departments on SharePoint, specialized workflows on a NAS, with clear rules about what lives where. It sounds like more to manage, but it's often less painful than forcing everything into the wrong tool.
The technology question is secondary to the workflow question. Figure out how your team actually works first. Then choose the tools that fit that reality, not the other way around. If you want help thinking through your specific situation, that's exactly the kind of conversation we're happy to have — check out what we do or reach out directly.