We're a hybrid organization with 10 branch offices, and each location currently has a file server containing roughly 2–3 TB of data. We're moving to the cloud and would like to place older data in Azure Archive while keeping files accessed within the last 180 days available to staff through Microsoft Teams. We have Microsoft 365 E5 licensing and about 18 TB of data in total. What tools, scripts, architecture, and migration practices would you recommend? I'd also appreciate examples of similar migrations and advice on avoiding common problems with Teams, SharePoint, synchronization, permissions, and user workflows.
4 Answers
Organize the destination around departments or business functions instead of putting everything into one Team and one SharePoint site. Give each logical group its own Team or site, with clearly defined libraries and permissions. Splitting the data sensibly makes governance easier and reduces the risk of huge libraries creating synchronization problems.
Bandwidth and staging design will have a major impact on the schedule. One approach is to synchronize the branch shares to virtual machines in Azure and use those machines as the source for Migration Manager. That avoids relying on slow branch-office connections during the final upload. In a well-connected environment, large transfers can run very quickly, but you should still plan for SharePoint throttling, file-path and filename restrictions, permissions cleanup, and validation after each migration wave.
ShareGate is one practical option for moving file-server content into SharePoint-backed Teams. It can help with mapping destinations, permissions, reporting, and staged migrations. Microsoft’s Migration Manager is another option worth evaluating, especially if you want to run the transfers from Azure-hosted staging machines.
Be careful about simply replacing the file servers with Teams and expecting users to work exactly as before. If everyone enables synchronization for large libraries, you can run into sync conflicts, client crashes, confusing offline copies, and unsupported file behaviors. Establish a clear workflow and consider limiting synchronization if users can work through the Teams and SharePoint web interfaces. Non-Office files such as PDFs may require downloading and re-uploading when users need to edit them, so test those workflows before committing.
The migration will go more smoothly if you first identify which files are active, stale, sensitive, or subject to retention requirements. Archive only content that can tolerate slower retrieval, and pilot the Teams experience with a few departments before moving all 18 TB.
For a Teams migration specifically, remember that the files are stored in SharePoint document libraries. The migration plan should therefore be designed around SharePoint sites, libraries, permissions, and metadata rather than treating Teams as a traditional file share.