Case study: file server to SharePoint migration
No new server, no VPN and no lost workday.
A small public agency that handles health information came to Wahaya IT in 2020 with no backup and a file server everyone could open. When the server was due for replacement, we moved its 350 GB of files to Microsoft Teams, SharePoint and OneDrive during the agency’s holiday closure. Staff came back to the same files and no server to maintain.
Small public agency, client since 2020
See the results- In 2020No backup, open file permissions and two weeks for a new account
- The move350 GB to Teams and SharePoint, and 22 computers joined to Entra ID
- ResultNo server, server backup or VPN to pay for, and same-day accounts

The situation
What we found when we took over.
The agency had about 10 users, a file server in the office and Microsoft 365. The table shows what we found in 2020 and where each item stands now.
New accounts
What we found in 2020: A new user account took nearly two weeks with the previous provider.
Where it stands now: New accounts are created the same day.
Backup
What we found in 2020: There was no backup in place.
Where it stands now: We added backup when we took over, including Microsoft 365 backup.
File access
What we found in 2020: Everyone could open everything on the file server, with no separation of data.
Where it stands now: Each team sees only its own files, with access set by Teams membership.
Accounts
What we found in 2020: The office server’s accounts weren’t synced with Microsoft 365.
Where it stands now: One synced account per person, protected by MFA, Conditional Access and device compliance.
Remote access
What we found in 2020: Files on the office server could only be reached from outside over a VPN.
Where it stands now: Files are in Teams, SharePoint and OneDrive, so there’s no VPN to run.
The agency has since doubled, from about 10 users to about 20.

Preparing and running the file server to SharePoint migration.
Fix the foundation first, then move when the hardware was due.
Connected the accounts
In 2020 we synced the office server’s accounts to Microsoft 365 with Azure AD Connect, so each person had one account, and added backup.
Locked down the files
We reviewed who could open what on the file server, so the new setup could give each team access only to its own files.
Skipped the new server
When the server was due for replacement, we recommended not replacing it. The files belonged in Microsoft 365 the agency already paid for.
Moved over the holiday
While the office was closed between Christmas and New Year’s, we moved 350 GB to Teams, SharePoint and OneDrive and joined all 22 computers to Entra ID.
The results
No server, no VPN and same-day accounts.
-
No lost workday
Staff came back after the holiday, signed in to computers already joined to Entra ID and opened their files normally.
-
No server to replace or maintain
The agency skipped the hardware purchase and no longer pays to run a server or back it up.
-
No VPN
Staff reach their files through Microsoft 365 from anywhere, so there’s no VPN to pay for or run.
-
Access by team, checked at every sign-in
Each team sees only its own files, and every sign-in passes MFA, Conditional Access and a device compliance check.
-
New accounts the same day
A new account took nearly two weeks with the previous provider. Now it’s done the same day, as the agency doubled to about 20 users.
What to expect in a Microsoft 365 migration
Moved while the office was closed for the holidays.
350 GB.
Small public agency
About 10 users in 2020, about 20 now.
Client since 2020
We took over from another provider.
See what Microsoft 365 Business Premium secures for an organization like this one.
What to take from it
Don’t replace a server just because it’s old.
When a server is due, ask what it still does. If it mostly holds files and sign-ins, Microsoft 365 may already cover both. Moving can remove the hardware, the server backup and the VPN at once, and staff can reach their files from anywhere. Keep a server only for what truly needs one.
Permissions first
Fix who can see what before you move.
Moving files with everyone-can-open-everything permissions just moves the problem to the cloud. We reviewed access first and built the new Teams and SharePoint sites around team membership. For an organization handling health information, that separation matters as much as the move itself.
Why we didn’t replace the server
The best server replacement was no server.
The server held files and sign-ins. The agency already paid for Microsoft 365, which can do both, so a new server would have meant buying hardware, backing it up and running a VPN to keep doing a job Microsoft 365 could take over. Because the accounts had been synced and the permissions reviewed ahead of time, the move itself was the easy part: one closed week, and staff came back to the same files.
All 22 computers were already joined to Entra ID when staff returned.
Files opened normally.
If this sounds like you
Is your server due for replacement?
We check what it still does
We list what runs on the server and what Microsoft 365 could take over.
We fix permissions first
We set who can see what before anything moves, and you decide when the move happens.
Questions about moving off a file server
Can SharePoint and Teams replace a file server?
For most small offices, yes. Shared folders become Teams and SharePoint sites, personal files move to OneDrive, and access is set by team. Keep a server only for an application that truly needs one.
How do you migrate a file server to SharePoint?
Fix permissions first, then move, because open permissions on a file server stay open in the cloud. Decide who should see what, build the Teams and SharePoint sites around those teams and pick a time the office is closed. File shares become Teams and SharePoint sites, and personal files move to OneDrive. Wahaya IT did this for a small public agency and moved 350 GB during its holiday closure.
Do we still need a VPN after moving to Microsoft 365?
Often not for files. Teams, SharePoint and OneDrive are reached securely over the internet, protected by MFA and sign-in checks. You may still need a VPN for other systems that live in the office.
What does Entra join mean?
Entra ID is Microsoft’s cloud sign-in service, formerly Azure Active Directory. An Entra-joined computer signs in with the person’s Microsoft 365 account instead of an office server, so it doesn’t need the server to log in.
How do you move to Microsoft 365 without downtime?
Plan it for a time the office is closed, fix permissions before the move, and have every computer ready before staff return. One small agency moved 350 GB and joined 22 computers during its holiday closure, and staff came back to their files. See what to expect in a migration.
Tell us when your server is due.
-
15 minutes
Tell us what runs on it today and who can open what.
-
We’ll tell you whether you need another one.
-
If we’re not the right fit, we’ll say so.







