You need to move files from a network file share to SharePoint. The task often fails because of broken permissions, long file paths, or duplicate content. This article provides a practical checklist for SharePoint owners to plan the migration from start to finish.
Many organizations migrate file shares to SharePoint to improve collaboration and access control. Without a proper plan, you risk data loss, permission errors, and user confusion. This checklist covers assessment, preparation, migration steps, and post-move validation.
Use this guide to avoid common mistakes and ensure a smooth transition. You will learn how to map permissions, handle file naming constraints, test the migration, and train your team.
Key Takeaways: File Share to SharePoint Migration Checklist
- SharePoint admin center > Migration center: Start the migration using the built-in Migration Manager for file shares and other sources.
- SharePoint site collection maximum size 25 TB: Ensure your target site does not exceed the storage limit; plan for multiple sites if needed.
- SharePoint file path limit 400 characters: Shorten folder and file names before migration to avoid sync and access errors.
Why File Share to SharePoint Migration Requires a Plan
A file share is a network drive that stores files on a central server. SharePoint is a cloud-based collaboration platform. The two systems handle permissions, file paths, and metadata differently.
File shares use NTFS permissions with user and group access control lists. SharePoint uses SharePoint groups and Microsoft 365 group permissions. Directly copying files does not transfer permissions. You must map NTFS permissions to SharePoint groups manually or with a migration tool.
File shares allow long file paths up to 32,767 characters. SharePoint enforces a 400-character path limit including the site URL. Files with paths longer than 400 characters will fail to upload or sync. You must rename or reorganize those files before migration.
Common Migration Tools
Microsoft provides the SharePoint Migration Tool and Migration Manager in the SharePoint admin center. Third-party tools like ShareGate, Metalogix, and AvePoint offer more advanced permission mapping and reporting. Choose a tool that supports your file share size and permission complexity.
Steps to Plan and Execute the Migration
- Assess the source file share
Inventory all folders, files, and permissions on the file share. Use a tool or script to export the folder structure, file count, total size, and permission details. Identify files with paths longer than 400 characters, files with invalid characters like # % & : < > ? / \ |, and duplicate files. - Design the SharePoint site structure
Decide whether to use one large team site or multiple sites. Each SharePoint site collection can hold up to 25 TB of content. For large file shares, consider splitting content into separate sites by department or project. Create a site hierarchy that mirrors the logical structure of the file share. - Map permissions
Export NTFS permissions from the file share. Create SharePoint groups that match the access levels: Owners, Members, Visitors. Map each NTFS group or user to the appropriate SharePoint group. For example, the Accounting NTFS group becomes the Accounting Members SharePoint group with Edit permission. - Clean up content before migration
Remove obsolete files, temp files, and duplicates. Rename files and folders that exceed the 400-character path limit. Replace invalid characters in file names. Run a test migration on a small folder set to validate the process. - Run a pilot migration
Migrate a small representative folder structure to a test SharePoint site. Verify that all files transfer correctly, permissions apply as expected, and file paths are valid. Check for broken links, missing metadata, and sync errors. - Execute the full migration
Use the SharePoint Migration Tool or your chosen third-party tool to migrate the entire file share. Schedule the migration during off-peak hours to minimize user impact. Monitor the migration progress in the tool dashboard. - Validate the migrated content
After migration, run a validation script or manual check. Compare file counts between the source and target. Test permissions by signing in as a member user and attempting to access restricted folders. Verify that all file previews, thumbnails, and search indexing work. - Communicate with users
Send an email to all affected users explaining the new SharePoint site location, how to access it, and how permissions work. Provide a training session or quick reference guide. Update bookmarks and shortcuts from the old file share to the new SharePoint URL. - Decommission the old file share
After a transition period of two to four weeks, confirm that no users need the old file share. Take a final backup of the file share. Remove access to the network drive and archive or delete the data.
Common Migration Problems and How to Avoid Them
File path length exceeds 400 characters
This is the most frequent migration failure. File shares allow very deep folder structures. SharePoint limits the full path including the site URL to 400 characters. Use a tool to identify paths longer than 380 characters. Rename folders to shorter names or flatten the folder structure before migration.
Permissions do not match after migration
NTFS permissions use SIDs (security identifiers) that do not exist in SharePoint. Migration tools map NTFS groups to SharePoint groups by name. If the group name does not exist in Microsoft 365, the permission is lost. Create all required Microsoft 365 groups before migration. Use a mapping file to ensure every NTFS group has a corresponding SharePoint group.
Files with invalid characters fail to upload
SharePoint does not allow these characters in file or folder names: ~ # % & { } \ : < > ? / | “. Use a PowerShell script or migration tool to rename files before migration. Replace invalid characters with underscores or hyphens.
Duplicate files cause confusion
File shares often contain multiple copies of the same file. SharePoint does not automatically deduplicate. Use a deduplication tool before migration or plan to manually clean up duplicates after migration. Set up versioning in SharePoint to track changes to a single file.
| Item | File Share | SharePoint |
|---|---|---|
| Permission model | NTFS ACLs | SharePoint groups and Microsoft 365 groups |
| File path limit | 32,767 characters | 400 characters |
| Storage limit per location | Limited by server disk space | 25 TB per site collection |
| File versioning | Not built-in | Built-in version history |
| Co-authoring | Not supported | Supported for Office files |
| Access from outside network | VPN required | Any internet connection |
Now you have a complete checklist to plan a file share to SharePoint migration. Start with the assessment step to understand your source data. Use the SharePoint Migration Manager for a simple migration or a third-party tool for complex permission mapping. Always run a pilot migration before the full move.
After migration, monitor the SharePoint site for sync errors and permission issues for at least two weeks. Train your users on how to use the new SharePoint site, including how to upload files, co-author documents, and use version history. Consider enabling SharePoint Auto-Expiration policies to automatically archive old content after a set period.
One advanced tip: use the SharePoint Migration Tool’s incremental migration feature to copy only changed files after the initial migration. This reduces the final cutover time and ensures that any files updated during the migration window are captured.