{"id":741,"date":"2026-10-06T16:39:10","date_gmt":"2026-10-06T15:39:10","guid":{"rendered":"https:\/\/www.mrpaulclarke.co.uk\/?page_id=741"},"modified":"2026-10-06T17:13:20","modified_gmt":"2026-10-06T16:13:20","slug":"case-study-migrating-from-on-prem-file-server-to-microsoft-365","status":"publish","type":"page","link":"https:\/\/www.mrpaulclarke.co.uk\/?page_id=741","title":{"rendered":"Case Study – Migrating from On Prem file server to Microsoft 365"},"content":{"rendered":"\r\n

☁️ Migrating an On-Premises File Server to Microsoft 365<\/h1>\r\n\r\n\r\n\r\n

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?<\/strong><\/p>\r\n\r\n\r\n\r\n

This project involved an organisation with an ageing on-premises file server that needed replacing.<\/p>\r\n\r\n\r\n\r\n

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.<\/p>\r\n\r\n\r\n\r\n

The result was a migration from traditional network file shares to SharePoint Online and OneDrive<\/strong>, ultimately allowing the physical file server to be decommissioned completely.<\/p>\r\n\r\n\r\n\r\n\r\n

\r\n\r\n\r\n

📈 The Project at a Glance<\/h3>\r\n\r\n\r\n\r\n
\r\n\r\n\r\n
\r\n\r\n

🖥️ START<\/strong>
Ageing Server
Network Shares<\/p>\r\n\r\n<\/div>\r\n\r\n\r\n\r\n

\r\n\r\n

🔍 AUDIT<\/strong>
Review Data
Clean Up<\/p>\r\n\r\n<\/div>\r\n\r\n\r\n\r\n

\r\n\r\n

☁️ MIGRATE<\/strong>
OneDrive
SharePoint<\/p>\r\n\r\n<\/div>\r\n\r\n\r\n\r\n

\r\n\r\n

✅ RESULT<\/strong>
Server
Decommissioned<\/p>\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div><\/div>\r\n\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n

🖥️ The Challenge<\/h2>\r\n\r\n\r\n\r\n

The organisation had a physical on-premises server providing traditional network file storage through Home<\/strong> and Public<\/strong> shares.<\/p>\r\n\r\n\r\n\r\n

The Public share contained the majority of the company’s shared information, while individual user data was stored separately.<\/p>\r\n\r\n\r\n\r\n

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.<\/p>\r\n\r\n\r\n\r\n

Remote access was also becoming increasingly important, highlighting the limitations of relying on a physical file server located in the office.<\/p>\r\n\r\n\r\n\r\n\r\n

\r\n\r\n\r\n
\r\n\r\n\r\n

⚠️ Existing Problems<\/h3>\r\n\r\n\r\n\r\n
    \r\n
  • Ageing physical server hardware<\/li>\r\n
  • Operating system approaching end of support<\/li>\r\n
  • Dependence on traditional network shares<\/li>\r\n
  • Remote file access more complicated than necessary<\/li>\r\n
  • Years of accumulated company data<\/li>\r\n<\/ul>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n\r\n
    \r\n\r\n\r\n

    💡 The Opportunity<\/h3>\r\n\r\n\r\n\r\n
      \r\n
    • Microsoft 365 already in use<\/li>\r\n
    • OneDrive already available<\/li>\r\n
    • SharePoint Online already available<\/li>\r\n
    • Improve access to company information<\/li>\r\n
    • Potentially remove the server completely<\/li>\r\n<\/ul>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n\r\n\r\n
      \r\n

      Replacing the old server with another server would solve the immediate hardware problem, but it wasn’t necessarily the best long-term solution.<\/strong><\/p>\r\n<\/blockquote>\r\n\r\n\r\n\r\n\r\n

      \r\n\r\n\r\n\r\n\r\n

      🔍 1. Audit the Existing Data<\/h2>\r\n\r\n\r\n\r\n

      The first step was to understand exactly what was stored on the existing file server.<\/p>\r\n\r\n\r\n\r\n

      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.<\/p>\r\n\r\n\r\n\r\n

      Staff were involved in reviewing the data so that unnecessary information wasn’t automatically transferred into the new environment.<\/p>\r\n\r\n\r\n\r\n\r\n

      \r\n\r\n\r\n
      \r\n\r\n\r\n

      📁 Keep<\/h3>\r\n\r\n\r\n\r\n

      Current business information that was still actively required.<\/p>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n\r\n

      \r\n\r\n\r\n

      📦 Archive<\/h3>\r\n\r\n\r\n\r\n

      Information that needed to be retained but wasn’t required for everyday use.<\/p>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n\r\n

      \r\n\r\n\r\n

      🗑️ Remove<\/h3>\r\n\r\n\r\n\r\n

      Duplicated, superseded and unnecessary information that didn’t need to be migrated.<\/p>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n\r\n\r\n

      \r\n

      There is little value in moving years of unnecessary data into a new platform simply because it happens to exist on the old server.<\/strong><\/p>\r\n<\/blockquote>\r\n\r\n\r\n\r\n\r\n

      \r\n\r\n\r\n\r\n\r\n

      👤 2. Configure OneDrive<\/h2>\r\n\r\n\r\n\r\n

      With the existing data understood, the next stage was to configure OneDrive<\/strong> for the individual users.<\/p>\r\n\r\n\r\n\r\n

      OneDrive provided the new location for user-specific information that didn’t need to form part of the company’s shared document structure.<\/p>\r\n\r\n\r\n\r\n

      Important user folders such as Desktop, Documents and Pictures<\/strong> were synchronised with Microsoft 365 rather than remaining dependent on an individual PC or the old file server.<\/p>\r\n\r\n\r\n\r\n\r\n

      \r\n\r\n\r\n

      💻 Easier PC Replacement<\/h3>\r\n\r\n\r\n\r\n

      Synchronising these folders also meant future PC replacements would be considerably easier.<\/p>\r\n\r\n\r\n\r\n

      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.<\/p>\r\n\r\n\r\n<\/div><\/div>\r\n\r\n\r\n\r\n\r\n

      \r\n\r\n\r\n\r\n\r\n

      👥 3. Prepare SharePoint<\/h2>\r\n\r\n\r\n\r\n

      The next stage was to prepare SharePoint Online<\/strong> for the company’s shared information.<\/p>\r\n\r\n\r\n\r\n

      The existing Public share contained information that needed to be accessed by multiple members of staff, making SharePoint the appropriate destination.<\/p>\r\n\r\n\r\n\r\n

      A SharePoint site and document structure were prepared, and the appropriate members of staff were given access.<\/p>\r\n\r\n\r\n\r\n\r\n

      \r\n\r\n\r\n
      \r\n\r\n\r\n

      👤 OneDrive<\/h3>\r\n\r\n\r\n\r\n
        \r\n
      • Individual user files<\/li>\r\n
      • Desktop<\/li>\r\n
      • Documents<\/li>\r\n
      • Pictures<\/li>\r\n<\/ul>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n\r\n
        \r\n\r\n\r\n

        👥 SharePoint<\/h3>\r\n\r\n\r\n\r\n
          \r\n
        • Shared company documents<\/li>\r\n
        • Common folders<\/li>\r\n
        • Business information<\/li>\r\n
        • Files accessed by multiple users<\/li>\r\n<\/ul>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n\r\n\r\n
          \r\n\r\n\r\n\r\n\r\n

          🚚 4. Migrate the File Server Data<\/h2>\r\n\r\n\r\n\r\n

          Once SharePoint had been prepared, the required shared data could be moved from the existing server.<\/p>\r\n\r\n\r\n\r\n

          Microsoft’s SharePoint Migration Tool<\/strong> was used to migrate the required folders and files from the on-premises file server into SharePoint Online.<\/p>\r\n\r\n\r\n\r\n

          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.<\/p>\r\n\r\n\r\n\r\n\r\n

          \r\n\r\n\r\n

          🔧 Migration Process<\/h3>\r\n\r\n\r\n\r\n