SharePoint Migration Assessment: Scoping File Share Cutover with Migration Manager

Retiring on-premises file servers is a common milestone for organisations moving to Microsoft 365, and Western Australian government agencies and enterprises are increasingly doing so under cloud adoption mandates. The temptation is to treat a file share migration as a simple copy operation, moving folders wholesale from a network drive into SharePoint Online or OneDrive. In practice, legacy shares carry years of accumulated structure, permissions and naming conventions that do not translate cleanly into a cloud content service, and a disciplined assessment before cutover reduces both risk and rework.

A structured pre-migration inventory allows teams to understand the true shape of the data before any content moves, rather than discovering problems mid-cutover when users are already affected. SharePoint Migration Manager, available within the SharePoint admin centre, provides a practical mechanism for scanning sources, running scans and reporting on issues that would otherwise fail silently. This article outlines a methodical approach to assessment and remediation across three areas that consistently cause difficulty: permissions, versioning and unsupported characters.

Building an accurate inventory before you commit

The first step is to establish exactly what exists on the shares in scope, because most file servers contain a mixture of active project data, dormant archives and orphaned content that no longer has a business owner. A good inventory records total volume, file counts, the age distribution of content, the deepest folder paths and the largest individual files. This baseline informs realistic scheduling, licence planning and decisions about what should migrate, what should be archived elsewhere and what can be defensibly disposed of under a records retention framework.

Migration Manager supports this discovery work by allowing agents to scan file shares and generate reports without moving any data, so teams can validate assumptions before committing to a cutover window. The reporting highlights items that will not migrate as expected, which is far more valuable when reviewed during planning than when encountered during execution. Pairing that technical scan with input from business owners about which shares remain in active use produces a defensible scope, and it prevents the common outcome of migrating large volumes of data that no one has opened in years.

Remediating permissions and access models

File share permissions rarely map neatly to SharePoint, because NTFS access control is built around nested security groups and inheritance at the folder level, whereas SharePoint governs access through site collections, libraries and item-level sharing. Deeply nested folder permissions, broken inheritance and direct user assignments on individual folders are all warning signs that a straight lift-and-shift would recreate a fragmented and unmanageable access model in the cloud. Government and aged care organisations in particular carry sensitivity obligations that make a clear, auditable permission structure essential rather than optional.

The assessment phase is the right time to rationalise access by mapping existing share permissions to a smaller set of security groups, ideally driven by Microsoft Entra ID membership rather than ad hoc individual grants. Where a share has thousands of unique permission combinations, it is usually preferable to redesign the target site structure so that each library or folder aligns to a coherent group of users, then migrate content into that cleaner model. This approach takes more effort up front, but it produces an environment that administrators can maintain and audit over time, which matters far more than reproducing every historical exception.

Handling versioning, unsupported characters and path length

Versioning behaviour differs between file shares and SharePoint, and this catches teams by surprise when storage consumption grows unexpectedly after cutover. SharePoint libraries retain multiple versions of each document by default, so a share that previously stored only current copies can suddenly consume considerably more space once version history begins accumulating. During assessment, teams should decide how many major versions to retain per library, confirm whether existing duplicate copies stored as separate files should be consolidated, and account for the storage implications in capacity planning.

Unsupported characters and excessive path lengths are among the most frequent causes of migration failures, and they are entirely predictable once you know what to look for. SharePoint Online does not permit certain characters in file and folder names, including the quotation mark, asterisk, colon, angle brackets, question mark, forward and back slashes and the pipe symbol, and it rejects leading or trailing spaces and some reserved names. The combined length of the site path and file name is subject to a limit of 400 characters, and individual files have a maximum size of 250 gigabytes, so long historical folder structures and oversized archives both require attention before cutover. Migration Manager reporting identifies these conditions in advance, allowing teams to rename, restructure or exclude the affected items so the eventual migration completes cleanly.

Turning assessment into a controlled cutover

An assessment only delivers value when it feeds directly into an execution plan, so the findings on volume, permissions, versioning and naming should shape both the sequence and the timing of the cutover. Migrating in waves aligned to business units or shares allows validation at each stage, keeps any issues contained and gives users a predictable transition rather than a single disruptive event. It also creates natural checkpoints where the team can confirm that permissions resolved correctly and that content is discoverable in its new location.

Communication and validation are as important as the technical steps, because users judge a migration by whether they can find and open their documents afterwards, not by the elegance of the underlying process. A short freeze on the source share during final synchronisation, clear guidance on where content now resides, and a defined support window all contribute to a smooth transition. When assessment and remediation are completed thoroughly beforehand, the cutover itself becomes a controlled and largely uneventful exercise, which is precisely the outcome that agencies and enterprises retiring legacy file servers should expect.

References

• Invalid file names and file types in OneDrive and SharePoint (Microsoft)
• Migration Manager overview (Microsoft Learn)
• SharePoint limits and specifications (Microsoft)