☁️ Migrating an On-Premises File Server to Microsoft 365
When an ageing file server reaches the end of its life, the obvious solution is to replace it. But what if you don’t actually need another server?
This project involved an organisation with an ageing on-premises file server that needed replacing.
Rather than simply purchasing another server and recreating the existing environment, I looked at whether the Microsoft 365 services the business was already paying for could provide a better long-term solution.
The result was a migration from traditional network file shares to SharePoint Online and OneDrive, ultimately allowing the physical file server to be decommissioned completely.
📈 The Project at a Glance
🖥️ START
Ageing Server
Network Shares
🔍 AUDIT
Review Data
Clean Up
☁️ MIGRATE
OneDrive
SharePoint
✅ RESULT
Server
Decommissioned
🖥️ The Challenge
The organisation had a physical on-premises server providing traditional network file storage through Home and Public shares.
The Public share contained the majority of the company’s shared information, while individual user data was stored separately.
The server hardware and operating system were reaching the end of their supported life, so a decision needed to be made about what would replace them.
Remote access was also becoming increasingly important, highlighting the limitations of relying on a physical file server located in the office.
⚠️ Existing Problems
- Ageing physical server hardware
- Operating system approaching end of support
- Dependence on traditional network shares
- Remote file access more complicated than necessary
- Years of accumulated company data
💡 The Opportunity
- Microsoft 365 already in use
- OneDrive already available
- SharePoint Online already available
- Improve access to company information
- Potentially remove the server completely
Replacing the old server with another server would solve the immediate hardware problem, but it wasn’t necessarily the best long-term solution.
🔍 1. Audit the Existing Data
The first step was to understand exactly what was stored on the existing file server.
Like many long-running file servers, it had accumulated years of files and folders. Some information was still actively used, some needed to be retained, and some was duplicated, superseded or simply no longer required.
Staff were involved in reviewing the data so that unnecessary information wasn’t automatically transferred into the new environment.
📁 Keep
Current business information that was still actively required.
📦 Archive
Information that needed to be retained but wasn’t required for everyday use.
🗑️ Remove
Duplicated, superseded and unnecessary information that didn’t need to be migrated.
There is little value in moving years of unnecessary data into a new platform simply because it happens to exist on the old server.
👤 2. Configure OneDrive
With the existing data understood, the next stage was to configure OneDrive for the individual users.
OneDrive provided the new location for user-specific information that didn’t need to form part of the company’s shared document structure.
Important user folders such as Desktop, Documents and Pictures were synchronised with Microsoft 365 rather than remaining dependent on an individual PC or the old file server.
💻 Easier PC Replacement
Synchronising these folders also meant future PC replacements would be considerably easier.
Rather than manually transferring a user’s Desktop, Documents and Pictures from one computer to another, their Microsoft 365 account could reconnect them with their synchronised data.
👥 3. Prepare SharePoint
The next stage was to prepare SharePoint Online for the company’s shared information.
The existing Public share contained information that needed to be accessed by multiple members of staff, making SharePoint the appropriate destination.
A SharePoint site and document structure were prepared, and the appropriate members of staff were given access.
👤 OneDrive
- Individual user files
- Desktop
- Documents
- Pictures
👥 SharePoint
- Shared company documents
- Common folders
- Business information
- Files accessed by multiple users
🚚 4. Migrate the File Server Data
Once SharePoint had been prepared, the required shared data could be moved from the existing server.
Microsoft’s SharePoint Migration Tool was used to migrate the required folders and files from the on-premises file server into SharePoint Online.
The migrated data was then checked to make sure the required folders and files had transferred successfully before staff began working from the new location.
🔧 Migration Process
- Prepare the SharePoint destination
- Migrate the required server data
- Review the migrated folder structure
- Validate files and permissions
- Confirm the new data was ready for users
💻 5. Sync SharePoint to the PCs
With the company data successfully migrated, the next stage was to make the transition as straightforward as possible for the users.
The SharePoint document library was synchronised to the users’ computers using the OneDrive client.
This allowed the shared company files to appear within File Explorer, providing staff with a familiar way of navigating folders and opening documents.
💡 Familiar for the User, Different Behind the Scenes
Staff could continue using File Explorer in much the same way they had before.
Behind the scenes, however, those files were now stored within Microsoft 365 rather than depending on a physical server in the office.
🔒 6. Disable the Old File Shares
Once the SharePoint data had been migrated, synchronised to the PCs and confirmed as working correctly, the old server shares could be disabled.
This was an important part of the cutover.
If the old shares had remained available, there was a risk that somebody would continue saving files into the old location, resulting in different versions of the company’s data existing in two places.
A migration isn’t complete while users can still accidentally continue working in the old system.
💾 7. Move the Sage Backup into OneDrive
With the file shares successfully migrated, there was one additional piece of data that needed to be considered: the Sage backup.
The Sage backup location was changed to the appropriate user’s Documents folder.
Because that Documents folder was already being synchronised by OneDrive, the Sage backup was then automatically copied into Microsoft 365.
☁️ A Simple Change With a Useful Benefit
The Sage backup continued to be created in a familiar local folder, while OneDrive provided an additional synchronised copy within Microsoft 365.
🖥️ 8. Decommission the Server
At this stage the server was no longer providing the file services the business depended upon.
User data was being handled through OneDrive, shared company information had been moved into SharePoint, the SharePoint libraries were available through File Explorer and the Sage backup had been moved into a OneDrive-synchronised location.
With the old shares disabled and the new environment confirmed as working, the physical server could finally be decommissioned.
The end result wasn’t a newer file server. It was no file server at all.
📈 The Benefits
🌍 Work From Anywhere
Staff were no longer dependent on the office file server to access their Microsoft 365 data.
↩️ Version History
Previous versions of documents could be recovered if files were accidentally changed or overwritten.
🗑️ File Recovery
SharePoint and OneDrive provided additional recovery options for accidentally deleted files.
💻 Easier PC Replacement
Important user folders could be reconnected through OneDrive rather than manually copied between computers.
👥 Familiar File Access
Synchronising SharePoint libraries allowed staff to continue accessing shared information through File Explorer.
🖥️ Less Infrastructure
The business no longer needed to maintain a dedicated physical server simply to provide file storage.
💷 The Business Outcome
No replacement file server. No additional Microsoft 365 licences. No additional third-party cloud storage.
Because the organisation already had suitable Microsoft 365 licensing, the project made better use of services it was already paying for.
There was no requirement to purchase a replacement physical server and no need to introduce an additional third-party cloud storage platform such as Dropbox.
💷 NO NEW SERVER
Avoided replacement hardware costs
☁️ EXISTING LICENSING
Used Microsoft 365 already in place
🖥️ LESS INFRASTRUCTURE
Less hardware to maintain and replace
The savings weren’t limited to the initial cost of purchasing a new server. Removing the server also reduced the ongoing infrastructure associated with maintaining, supporting, backing up and eventually replacing physical hardware.
Sometimes the most cost-effective infrastructure upgrade is removing infrastructure you no longer need.
🛠️ Technologies & Skills
- Microsoft 365
- SharePoint Online
- Microsoft OneDrive
- SharePoint Migration Tool
- File Server Migration
- Data Auditing
- Data Clean-Up
- Permissions Planning
- OneDrive Folder Protection
- SharePoint Synchronisation
- File Explorer Integration
- Server Decommissioning
☁️ Still Running an Ageing File Server?
If your business already uses Microsoft 365, replacing an ageing file server with another physical server may not be your only option.
I can review your existing environment, identify what genuinely needs to remain on-premises and look at whether services such as SharePoint and OneDrive could provide a simpler and more cost-effective alternative.
