Quick Answer: How to Approach a 100TB File Share Migration to SharePoint
A 100TB file share migration to SharePoint succeeds or fails before the first byte moves: classify and de-duplicate the estate, decide what goes to SharePoint versus Azure Files versus retirement, and only then run migration waves against a signed cutover plan. At that scale the constraint is not bandwidth. It is governance: permissions that no longer map to people, records that carry retention obligations, and shares nobody will claim. i3solutions plans and runs governed SharePoint migrations with senior, 100% U.S.-based SharePoint architects and consultants.
The Decisions That Shape a 100TB Migration
What actually belongs in SharePoint. At 100TB, a lift-and-shift produces the estate buyers later describe as a data dump. Collaborative documents belong in SharePoint. Large media, archives, and application data usually belong in Azure Files or blob storage. Duplicates, orphans, and expired records belong nowhere. Classification before migration is what separates a usable tenant from a bigger version of the problem you had, which is why data classification before SharePoint migration is its own discipline.
Permissions and ownership. Decades-old file shares carry permission structures that no longer describe the organization. The migration is the one moment you can reset to a governed model: site-per-workload, group-based access, and named owners. Recreating legacy ACLs in SharePoint recreates the audit findings that come with them.
Wave design and cutover. A 100TB estate moves in waves ordered by business risk, not alphabet: pilot with a real department, validate permissions and search, then scale with a rollback path per wave. Microsoft’s Migration Manager or SPMT handles the transfer; the wave plan decides what it transfers and in what order. The share stays read-only after its wave cuts over, then retires on a dated schedule.
Timeline and cost shape. Enterprise SharePoint strategy assessment engagements typically run four to six weeks elapsed time with two to three i3solutions consultants, and how those engagements are priced is covered in how Microsoft consulting engagements are billed; the assessment is where the wave plan, the target architecture, and the retirement list get signed. For regulated organizations, plan for the compliance load explicitly: regulated-enterprise migration practices typically absorb a 25 to 35 percent overhead on top of the base migration work, driven by control mapping and evidence requirements.
Retiring the File Servers: What Goes to SharePoint, What Goes to Azure Files, and What Is Deleted
As of September 2026, route file-server content four ways: documents people open, edit and share go to SharePoint within Microsoft’s published limits, content an application reads or writes as a file share goes to Azure Files, sites that still need a local server keep one as an Azure File Sync cache, and the rest is deleted under a signed decision. Route each share by how it is used, not by where it sits today, because an application that writes to a mapped drive breaks when its share lands in a document library.
| What the content is | Where it goes | Why |
|---|---|---|
| Documents people open, edit, co-author and share | SharePoint | Collaboration in Microsoft 365, inside the file size, path length and library limits below |
| Files an application, scheduled job or scanner reads or writes by share path | Azure Files | A cloud file share reached over SMB or NFS, for applications that expect shared file storage |
| Shares at a site that still needs local speed | Azure File Sync, with cloud tiering | A Windows file server kept at the site as a cache of an Azure file share |
| Duplicate, orphaned and expired content | Deleted | A signed decision per content class, not a migration step |
Check the SharePoint route against Microsoft’s published limits before a share is assigned to it. According to Microsoft’s SharePoint limits page, the limits include “250 GB – File upload limit.” and “The entire decoded file path, including the file name, can’t contain more than 400 characters for OneDrive, OneDrive for work or school and SharePoint in Microsoft 365.” (Microsoft Learn, SharePoint limits, read 2026-09-24). According to Microsoft’s SharePoint limits page, “a library can have up to 30 million files and folders”, and Microsoft adds: “For optimum performance, we recommend syncing no more than 300,000 files in a single OneDrive or team site library.” (Microsoft Learn, SharePoint limits, read 2026-09-24). According to Microsoft’s Migration Manager page, the file-share route has the same size ceiling: “We support files up to 250 GB in size for file share to Microsoft 365 migrations.” (Microsoft Learn, Migrate your file shares to Microsoft 365 with Migration Manager, read 2026-09-24). A share with files over that size, paths past that length, or a library its users will sync past that count is restructured before its wave or routed elsewhere; it is not a SharePoint wave as it stands.
Send to Azure Files what an application depends on as a share. Microsoft describes the service in these words: “Azure Files provides fully managed file shares in the cloud that you can access through the industry-standard SMB and NFS protocols.” Its list of uses includes “Replace or supplement on-premises file servers” and “Migrate applications that expect shared file storage to Azure without code changes.” (Microsoft Learn, What is Azure Files?, read 2026-09-24). Microsoft’s storage overview frames the same choice from the owner’s side: “You want to replace or supplement on-premises file servers or NAS devices.” (Microsoft Learn, Introduction to Azure Storage, read 2026-09-24). The test per share is simple: if a line-of-business application, a scheduled job or a scanner writes to it by path, it goes to Azure Files; if people are the only ones who open it, it goes to SharePoint, subject to the limits above.
Keep a local server only where a site needs one, and run it as a cache. Microsoft states that “Azure File Sync centralizes your organization’s file shares in Azure Files while keeping the flexibility, performance, and compatibility of on-premises Windows file servers.” and that “Each registered Windows Server syncs its data to and from a central Azure file share, and can optionally use cloud tiering to cache only the most frequently accessed files locally.” (Microsoft Learn, What is Azure File Sync?, read 2026-09-24). Of cloud tiering, Microsoft says: “When you enable this feature, it stores only frequently accessed (hot) files on your local server.” (Microsoft Learn, Understand Azure File Sync Cloud Tiering, read 2026-09-24). Microsoft’s migration guidance names the pattern directly: “Hybrid deployment: Use Azure File Sync to cache the content of Azure file shares on-premises and tier less frequently used files to the cloud.” (Microsoft Learn, Migration Overview for SMB Azure File Shares, read 2026-09-24).
Delete the rest only under a signed decision per content class. Who signs, and what is verified before anything is removed, is covered in our guide Which SharePoint Content to Migrate, Archive, or Retire.
Decide per share whether its permissions are kept or rebuilt
A share’s permissions follow opposite paths on the two destinations, so the wave plan has to know which path each share takes. On Azure Files the Windows permissions carry over. Microsoft states that “Azure Files supports Windows ACLs, and they must be set on the target share even if no AD integration is configured at migration time.” and advises: “If you’re migrating on-premises file servers to Azure Files, set the ACLs for the root directory of the file share before copying a large number of files, as changes to permissions for root ACLs can take a long time to propagate if done after a large file migration.” (Microsoft Learn, Migration Overview for SMB Azure File Shares, read 2026-09-24). Sign-in carries over as well: “Using identity-based authentication provides a seamless migration experience when replacing on-premises file servers, allowing end users to continue to access their data with the same credentials.” Microsoft adds: “For security reasons, use identity-based authentication to access SMB file shares instead of the storage account key.” (Microsoft Learn, Overview – Azure Files Identity-Based Authentication, read 2026-09-24). SharePoint is the other case: as the permissions paragraph above sets out, the share’s permissions are rebuilt on a governed model, not copied. Mark each share kept or rebuilt before the wave plan is signed, because the two paths are validated differently on cutover day.
When the tenant runs in GCC, GCC High or DoD
For Migration Manager, a government-cloud tenant changes which features are available, not whether the file-share route exists. Microsoft’s specialty environments table marks the File Share scenario as supported in GCC, GCC High and DoD, and states: “The Scans module for File Share scenario is not available in any specialty environment.” (Microsoft Learn, Specialty environments support, read 2026-09-24). In those clouds, plan the pre-migration scan of each share by other means, and confirm with Microsoft that Azure Files and Azure File Sync are available to your government subscription before any share is routed to them. A tenant consolidating Egnyte rather than file shares gets a different answer, set out in Egnyte to SharePoint Online: A Migration Checklist for Regulated Enterprises, because Microsoft states that Migration Manager only supports File Share migration for the Government cloud.
Retiring every server is the wrong frame in two cases: an application that needs a file server neither destination serves in the way its maker supports, and a site whose network link cannot carry its users’ traffic to the cloud. Azure File Sync keeps a registered Windows Server at the site by design, so in those places the case funds a smaller server, not none.
The Business Case to Retire the Servers, Line by Line
A retirement case gets approved when it lists what stops being paid for and what starts, not when it quotes a multiple. Build it as two lists of line items against the routing above, one for what leaves with the servers and one for what the destinations add.
What retires with the servers. List each item the organization stops funding once the last share cuts over:
- The hardware refresh the servers would otherwise need at the end of their current cycle.
- Operating system support for each server that retires. Microsoft’s Azure Arc guidance states: “Windows Server 2016 reaches end of support on January 12, 2027.” The option the budget holder will be offered instead is in the same guidance: “By using Azure Arc-enabled servers, you can enroll your existing Windows Server machines in Extended Security Updates (ESUs) after they reach end of support.” (Microsoft Learn, Prepare to deliver Extended Security Updates for Windows Server through Azure Arc, read 2026-09-24). A server that retires needs neither.
- The servers’ own backup and recovery: the jobs, the storage they write to and the restore tests.
- The read-only period for each share, which ends on the dated schedule the wave plan sets.
What the destinations add. List what the organization starts funding, and size the SharePoint line against Microsoft’s own allocation, not an estimate:
- SharePoint storage. According to Microsoft’s SharePoint limits page, total storage per organization on the enterprise plans is “1 TB + 10GB per license purchased”. The same page states “The total storage for your tenant isn’t unlimited.” and warns: “If your tenant continues to operate above your storage limits, you are at a risk of your environment being put into ‘read-only’ mode.” (Microsoft Learn, SharePoint limits, read 2026-09-24). Reclaiming space in a tenant that is already over quota is covered in SharePoint Storage Over Quota From Version Bloat and Dead Data: How to Reclaim It the Right Way in a Regulated Tenant.
- An Azure storage account for each Azure Files share, with identity-based access set up in place of the storage account key, as Microsoft advises above.
- The Windows servers that stay as Azure File Sync caches at the sites that need them.
- The one-time migration project: the assessment, the waves and the cutover.
SharePoint migration and storage prices are set out in How Much Does a SharePoint Migration Cost?, and the method for turning the two lists into a funded case is in SharePoint Modernization ROI: Business Case for Regulated Enterprises.
i3solutions plans and runs governed Azure and Microsoft 365 migrations with senior, U.S.-based engineers. The i3 Risk and Roadmap Assessment ROI variant is a one-week structured engagement that produces a business case anchored on the specific environment, the specific compliance frameworks, and the specific executive-cycle timing.
Contact a senior SharePoint architect to route your shares and build the retirement case your budget holder signs.
Frequently Asked Questions
How long does a 100TB migration to SharePoint take?
The honest answer is wave-dependent: the strategy assessment that produces the wave plan typically runs four to six weeks, and the migration itself is then paced by validation capacity, not transfer speed. Organizations that skip the assessment usually discover the timeline mid-flight instead of before it.
Should everything on the file shares go to SharePoint?
No. SharePoint is for collaborative content. Large media, cold archives, and application data typically route to Azure Files or blob storage, and a meaningful share of a 100TB estate is duplicate or expired content that should retire rather than migrate.
What breaks most often in large file share migrations?
Permissions and expectations. Legacy ACLs do not map cleanly to SharePoint groups, long paths and locked files stall transfers, and users who were not part of the pilot discover the new structure on cutover day. Wave design with a real pilot department addresses all three.
What does regulated-industry compliance add to the work?
Regulated-enterprise migration practices typically absorb a 25 to 35 percent overhead on top of the base migration work: retention mapping, evidence capture, and control validation that commercial migrations skip.
If a 100TB estate is on your roadmap and you need a plan your committee can defend, a SharePoint modernization discussion puts wave design, target architecture, and the compliance overhead against your actual estate. Schedule a SharePoint Migration Discussion.
