Projects that try to just “copy the file server to SharePoint” usually come back two weeks after the switchover: path length errors, Access databases that won’t open, broken Excel links and permissions where nobody knows who sees what. A share such as \\FS01\Common that has swollen over the years holds team documents, personal folders, application data and archives in the same tree. So the job is not copying but reclassifying data. Below we go through, in order, which data goes to SharePoint, which to OneDrive, which stays on premises and how the move is carried out in the field.
Inventory first, then the plan
A migration plan starts with a data inventory, not a list of shares. For each share, gather: total size, number of files and folders, distribution by last modified date, deepest folder level, longest path, file types, points where NTFS inheritance is broken and the business unit that owns the share. A share without an owner isn’t migrated; its owner is found first.
The last modified date is the main input to the decision. Moving data nobody has touched in years into an active workspace pollutes search and increases sync load. For this data, a separate archive site or a read-only archive on premises is often the better destination.
Migration Manager and the SharePoint Migration Tool (SPMT) produce scan reports, but taking the first snapshot with PowerShell gives you numbers to discuss before installing any tool:
$root = "\\FS01\Common"
Get-ChildItem -Path $root -Recurse -File -ErrorAction SilentlyContinue |
Select-Object FullName, Length, LastWriteTime, Extension |
Export-Csv C:\Migration\common-inventory.csv -NoTypeInformation -Encoding UTF8
# Summary by extension
Import-Csv C:\Migration\common-inventory.csv |
Group-Object Extension |
Sort-Object Count -Descending |
Select-Object -First 20 Name, Count
On large shares this script takes hours and silently skips folders where access is denied. A common mistake is taking the inventory with an account that lacks permissions, so the “missing” folders turn up on switchover night. Verify in advance that the account running it can read the whole tree.
Which data goes where: SharePoint, OneDrive, Teams or on premises
The rule is simple: data that belongs to a team and must stay when a team member leaves goes to SharePoint (usually the site connected to a Teams team), and one person’s working files go to OneDrive. User home folders (home drives) map naturally to OneDrive.
| Data type | Recommended destination | Note |
|---|---|---|
| Department share | SharePoint team site | Can be connected to a Teams team |
| Project folders | A site or library per project | Archived when the project ends |
| Personal home folder | OneDrive | Combined with Known Folder Move |
| Company-wide documents | Communication site | Most users only read |
| Data unchanged for years | Archive site or on-premises archive | Doesn’t bloat the active area |
| Access databases, CAD, PST | Stays on premises or a separate solution | See the explanation below |
Data that should not be moved
- Multi-user Access databases (.accdb, .mdb): File locking and concurrent writes work over SMB. Multi-user use through a synced library can corrupt the file.
- CAD projects with external references: AutoCAD xrefs and assembly files depend on absolute or relative paths. When the path changes, the references break. A solution that keeps SMB, such as Azure Files, is better suited to this data.
- PST files: Microsoft doesn’t support using PSTs over a network share, and the sync client can’t sync an open PST. PSTs are imported into the Exchange Online archive.
- Application data folders: Data that ERP, accounting and license servers keep on a share can’t be moved, because the application expects a UNC path.
An application folder doesn’t go into SharePoint. Period.
We cover the options for data that must keep SMB separately in our guide to a hybrid file server with Azure Files and Azure File Sync.
Technical limits: path length, characters, file types
The limit people hit most often in SharePoint and OneDrive is path length. The total decoded path (including the site address, library, folders and file name) cannot exceed 400 characters. Because the \\FS01\Common\... prefix on the file server is replaced by https://tenant.sharepoint.com/sites/Accounting/Shared Documents/..., a path that looks fine on premises can exceed the limit at the destination. The sync client keeps files on the user’s disk under C:\Users\user\Company Name\Site - Library\...; long path support in older applications on the Windows side causes additional problems here.
# Find long paths, taking the destination prefix into account
$prefix = "https://tenant.sharepoint.com/sites/Accounting/Shared Documents/"
Import-Csv C:\Migration\common-inventory.csv | ForEach-Object {
$relative = $_.FullName.Substring("\\FS01\Common\".Length)
[pscustomobject]@{ Path = $_.FullName; TargetLength = ($prefix + $relative).Length }
} | Where-Object TargetLength -gt 350 |
Export-Csv C:\Migration\long-paths.csv -NoTypeInformation -Encoding UTF8
Choosing 350 instead of 400 as the threshold leaves room in case the site or library name gets longer later. Other limits:
- The characters
" * : < > ? / \ |can’t be used in file and folder names; leading and trailing spaces aren’t accepted. - Names such as
.lock,CON,PRN,AUX,NUL,COM0–COM9,LPT0–LPT9,_vti_,desktop.iniand file names starting with~$are blocked. - The upper limit for a single file is 250 GB.
- Libraries have a 5,000-item list view threshold; if many files will be gathered in a single folder, plan views and indexed columns in advance.
Limits are updated over time. At the start of the project, check Microsoft’s “Restrictions and limitations in OneDrive and SharePoint” page again.
Mapping NTFS permissions to SharePoint permissions
NTFS allows inheritance to be broken at every level of the folder tree; over the years hundreds of exceptions build up on file servers. In SharePoint, permissions are given at site level: Owners, Members and Visitors. Exceptions can be managed at library level. Broken (unique) permissions at folder and file level, however, both complicate management and push you toward the number of broken permissions Microsoft recommends per library.
The mapping order that works in the field:
- List all folders in the inventory where inheritance is broken (those with
AreAccessRulesProtectedset toTruein theGet-Acloutput). - For each subfolder with a different access group, decide with the business unit whether it needs a separate library or a separate site. The “Payroll” folder in the accounting share should be a separate library or a separate site.
- Convert permissions granted directly to users in NTFS into groups. At the destination, Entra ID security groups or Microsoft 365 groups are used; synced on-premises AD groups can be used directly.
- Don’t copy broad permissions such as “Everyone” and “Domain Users” to the destination; redefine them through site membership.
Migration Manager and SPMT have an option to preserve file share permissions. This option maps ACLs only to identities that exist at the destination; without a user mapping file, local accounts and deleted SIDs aren’t moved. How to build the site, library and item-level model is explained in detail in our SharePoint permission model design guide.
Moving with Migration Manager and the SharePoint Migration Tool
Microsoft has two free tools for file shares. Scale decides the choice:
| Criterion | Migration Manager | SPMT |
|---|---|---|
| Management | SharePoint admin center | Desktop application |
| Scale | Multiple agents, parallel tasks | Single machine |
| Suitable scenario | Large migrations with many shares | Small or one-off migrations |
| Task input | Portal or bulk CSV | Interface, CSV/JSON or PowerShell |
In Migration Manager, agents are installed on Windows machines in the on-premises server infrastructure that have network access to the file server, and tasks are distributed from the admin center. Install the agent on a separate server on the same network, not on the file server itself, so the copy load doesn’t compete with the files users have open.
Recommended flow
- Scan: Run all sources in scan-only mode. The report shows long paths, invalid characters and inaccessible files.
- Fix: Shorten paths, correct names, delete unnecessary data or move it to an archive.
- First copy: Take the full copy while users are working on the file server.
- Incremental passes: Rerunning the same task moves only new or changed files.
- Switchover: The share is made read-only, the final incremental pass runs and users are pointed to the new location.
The failed item list in the task reports should be brought to zero before the switchover, or each item deliberately excluded. Transfer time depends on the number of files, the average file size and throttling on the tenant side. Don’t estimate the time; measure it on a pilot share and extrapolate to the remaining data. Small files move slowly.
The OneDrive sync client and moving users over
The OneDrive sync client gives users the drive-letter experience they are used to, but it doesn’t scale without limit. Microsoft recommends not exceeding 300,000 files in total across all synced libraries. Having everyone sync all the department sites quickly exceeds this limit, and complaints about high CPU and disk usage at sign-in hit the help desk in the first week.
- Files On-Demand should be on; a file is downloaded only when opened.
- Instead of syncing the whole library, have users add only the folders they need to their OneDrive with “Add shortcut to My files.”
- Redirect the Desktop, Documents and Pictures folders to OneDrive with Known Folder Move through Intune or Group Policy. Doing it at the same time as the home folder migration means users experience a single change.
- Prepare the Group Policy preferences and logon scripts that remove old drive mappings before switchover day.
Backup after the migration is a separate decision. SharePoint’s version history and recycle bin don’t replace a backup; you’ll find this topic in detail in our Microsoft 365 backup guide.
Switchover day checklist
- Scan reports clean for all shares; failed items at zero or deliberately excluded.
- Owners, members and visitors of the target sites verified with the business unit.
- Source shares read-only at NTFS level (not just the share permission; NTFS write permission also removed). Closing only the share permission doesn’t stop someone connected to the server over RDP from writing.
- Final incremental pass completed, source and destination file counts compared.
- Drive mappings removed; OneDrive shortcuts and Teams channels announced to users.
- An information note given to the support team about UNC links inside applications (linked Excel workbooks, macros, shortcuts).
- How long the old server stays read-only and its shutdown date decided; a final full backup taken before shutdown.
In environments using DFS Namespaces, the switchover is easier to manage: namespace targets can be changed to redirect users. Assess your current setup against the criteria in our article on DFS Namespace and DFS Replication design. If you’d like support with data classification and permission design, see our Microsoft 365 and cloud services page. Microsoft’s SharePoint Migration Tool documentation should be the reference for the tools’ current features. For document classification, revisions and access after the move, see our SharePoint document management setup service.
Frequently asked questions
Is it right to move the whole file server to a single SharePoint site?
No. A single site and single library lead to broken permissions, an overloaded sync client and hitting view thresholds. Splitting shares into separate sites and libraries by ownership and access group makes management easier.
Can users keep using the file server during the move?
Yes. The first full copy can be taken while users are working. Incremental passes before the switchover move only changed files; on switchover night the share is made read-only and the final incremental pass runs.
Should NTFS permissions be moved to SharePoint one to one?
The tools offer an option to preserve permissions, but moving deeply nested, item-level broken permissions as they are leaves an unmanageable structure in SharePoint. Redesigning permissions at site and library level, group-based, and moving exceptions into separate libraries is more sustainable.
When should the old file server be shut down after the migration?
After the shares are made read-only, they should stay accessible for a while; open requests and application dependencies should be monitored, then a final backup taken and the server shut down. Agreeing this period with business units in advance reduces surprises.