The office file server is often the last thing keeping a business tied to a server room. Moving it into SharePoint and OneDrive lets staff reach files from anywhere and removes hardware to maintain. It goes well when it is planned as a redesign and badly when it is treated as a copy.
OneDrive, SharePoint and Teams
OneDrive holds each person's own working files. SharePoint holds files that belong to a team or the whole business. Teams sits on top of SharePoint, so files shared in a team live in a SharePoint site. Decide what goes where before moving anything.
Clean up first
A file server collects years of duplicates, old projects and folders nobody owns. Archive or delete what isn't needed before the move. Moving everything just moves the mess.
Rethink the structure
One giant shared drive with deep folders doesn't translate well. Split it into sites by team or function, such as finance, operations and projects, each with its own owner and members. Keep the folders inside each site shallow.
Fix permissions on the way
Permissions on old file servers are usually tangled. Set access at the site level by group, and avoid sharing individual folders and files where you can. This matters even more if you plan to use Copilot, which can surface anything a person has access to.
What doesn't move well
Very long file paths, some file types, databases, and applications that expect a mapped drive letter need attention. Large design and video files may sync slowly. Test these before committing.
Run it in stages
Move one team at a time. Make the old location read-only once a team has moved, so nobody keeps working in the wrong place, and keep it for a set period before switching it off.
Remember backup
Files in SharePoint are no longer covered by the server's backup. Arrange a Microsoft 365 backup before the old server is retired.
Want Microsoft 365 set up and run properly? Managed Microsoft 365
All resources