In this guide · 8 sections
- 01Should you move the file server to the cloud?
- 02Clean up before you migrate
- 03Limits that break migrations: names, paths and item counts
- 04Permissions: map folders to groups, not people
- 05How to run the migration, step by step
- 06Sync, offline access and the read-only archive
- 07Do it yourself or get help?
- 08Frequently asked questions
Short answer
Clean up and restructure first, then check names and paths against the platform's limits. Map permissions to a few groups, migrate with Microsoft's Migration Manager or Google's tools, move teams over one at a time, and keep the old server read-only as an archive for a few months before retiring it.
Should you move the file server to the cloud?
For most small offices on Microsoft 365 or Google Workspace, yes: storage is already included in your plan, and you remove a box that needs patching, backups and replacement every few years. There are exceptions.
Good fit for SharePoint or Drive
- Office documents, PDFs and images shared by a team
- Staff work from home or on the road
- The server or NAS is old or out of support
- Nobody is checking the server's backups
Think carefully if
- Very large files edited daily (video, CAD, big design files) on slow internet
- Line-of-business software that needs a mapped network drive
- Desktop databases such as old Access or accounting files shared over the network
- Millions of small files in deep folder trees
Not sure which platform to choose? Our Google Drive vs OneDrive vs Dropbox comparison covers the differences for small teams.
Clean up before you migrate
This is the step people skip and regret. Moving 15 years of clutter into the cloud makes searching worse and sync slower.
Pre-migration clean-up
If you hold personal data you no longer need, this is also a good moment to delete it under your retention policy. See our data retention policy template.
Limits that break migrations: names, paths and item counts
Windows file servers allow things the cloud does not. Run a scan before migrating so problems surface now, not as thousands of sync errors later.
| Limit | SharePoint / OneDrive | Google Drive shared drives |
|---|---|---|
| Blocked characters and names | Characters such as " * : < > ? / \ | and names like CON, desktop.ini or files starting with ~$ | Fewer restrictions, but avoid the same characters for compatibility |
| Path length | Long paths cause sync and Office app errors; limits differ by app | Deep nesting allowed (up to 100 levels) |
| Items | Microsoft recommends syncing no more than 300,000 items in total per device | Up to 500,000 items per shared drive |
| Single file size | Up to 250 GB | Large files supported; per-user upload limit of 750 GB a day |
Sources: Microsoft's OneDrive and SharePoint restrictions page and Google's shared drive limits. The simplest fix for path problems is flattening the structure: fewer nested folders and shorter folder names.
Permissions: map folders to groups, not people
File servers often have years of one-off permissions: this person can see that folder because someone asked in 2017. Do not copy that mess.
- Group by team or function: Finance, Sales, Operations, Management. Each gets its own SharePoint site or Google shared drive.
- Assign access to groups, not individuals, so new staff get the right access by joining a group.
- Keep sensitive areas separate: HR and payroll in their own site or shared drive with a small member list.
- Decide on external sharing before go-live: off by default for sensitive areas, links that expire for the rest.
Microsoft's SharePoint sharing links can quietly widen access over time. Our guide to cleaning up SharePoint and OneDrive sharing links shows how to check and tighten them after the move.
How to run the migration, step by step
For Microsoft 365, Microsoft's free Migration Manager in the SharePoint admin centre migrates file shares to SharePoint, OneDrive or Teams. It uses a small agent installed on a PC that can read the file share, supports files up to 250 GB, and produces reports of what moved and what failed. For Google Workspace, small offices usually upload through Drive for desktop into shared drives.
Create the destination sites or shared drives
Build the new structure and group permissions first, with nobody using them yet.
Run a scan or pilot migration
Migrate one small team's folder to find blocked names, long paths and permission surprises.
Do the bulk copy while people keep working
Copy everything once in the background. This can take days on a normal office connection.
Run a final incremental pass at cut-over
Pick a quiet evening, make the old share read-only, then copy only what changed since the bulk copy.
Switch each team over
Remove the mapped drive, show staff where their files are now and how to sync the folders they need.
Check counts and spot-check files
Compare file counts and sizes against your pre-migration record, and open a sample of files in each area.
Sync, offline access and the read-only archive
Staff often expect the cloud to behave exactly like the old S: drive. It almost does, with some differences worth explaining up front.
- Sync selectively: each person syncs only the libraries or folders they use, using Files On-Demand or streaming so files download only when opened.
- Shortcuts, not copies: show staff how to add a shared folder to their file explorer instead of downloading copies.
- Co-authoring: Office files can be edited by several people at once in the cloud; old "file is locked" habits change.
- Version history: accidental overwrites can be rolled back, which is one of the big wins over a file server.
Our guide to backing up Microsoft 365 and Google Workspace explains what the built-in recycle bins and version history do and do not cover.
Do it yourself or get help?
A few hundred gigabytes and a simple folder structure is a manageable weekend project for someone comfortable with admin consoles, following the steps above. The clean-up decisions take longer than the copying.
Get help if you have many years of nested folders, complex permissions, software depending on mapped drives, or personal data that needs tighter access. Our Backup & Ransomware Recovery package (S$290) sets up a proper backup of the new cloud storage and keeps the old archive safe; Microsoft 365 / Google Security Lockdown (S$590) covers sharing settings, permissions and MFA. For ongoing support costs in general, see how much IT support costs in Singapore.
Frequently asked questions
For most document storage, yes. SharePoint gives shared libraries with group permissions, version history and access from anywhere. It is a poor fit for very large files edited daily on slow connections, and for software that needs a mapped network drive or shares a database file over the network. Check those before you commit.
Microsoft's free Migration Manager, in the SharePoint admin centre, is designed for moving file shares to SharePoint, OneDrive and Teams. It runs a small agent on a PC with access to the share, supports files up to 250 GB, and gives reports on what moved and what failed.
Common causes are characters OneDrive does not allow in names, reserved names such as desktop.ini, very long folder paths, and too many items synced on one device. Microsoft recommends no more than 300,000 items synced in total. Rename problem files and flatten deep folder structures.
Not on its own. SharePoint, OneDrive and Google Drive have recycle bins and version history, which help with accidents, but deletions and ransomware can still spread and retention periods are limited. Keep a separate backup of your cloud data, and keep the old server's final backup for some time after migrating.
For a small office, planning and clean-up often take longer than the copy. The bulk copy depends on data size and internet upload speed and can run for days in the background. A final incremental copy and team-by-team switch-over can usually be done in an evening.