How to Plan a File Share to SharePoint Migration

Moving files from a network file share to SharePoint requires a structured plan to avoid data loss, broken permissions, and user confusion. A direct copy-paste often fails because SharePoint has different storage limits, permission models, and file naming rules. This article explains the key planning steps, including inventory assessment, permission mapping, and site structure design. You will learn how to create a migration roadmap that minimizes downtime and keeps your team productive.

What Makes a File Share Migration Different From a Simple Copy

A file share is a folder on a server that users access through a mapped drive or UNC path. SharePoint stores files in a cloud-based document library with version history, co-authoring, and metadata columns. The two systems treat permissions, file paths, and storage limits differently:

• File path length: Windows file shares support paths up to 260 characters. SharePoint supports up to 400 characters but requires special handling for characters like # and %.
• Permission model: NTFS permissions apply to folders and files individually. SharePoint uses site-level groups (Visitors, Members, Owners) with optional unique permissions on folders.
• Storage limit: File shares are limited by server disk space. SharePoint sites have a default 25 TB limit per site collection in Microsoft 365.
• File types: SharePoint blocks certain file types by default, such as .exe, .bat, and .vbs. You must review the blocked file list before migration.

Understanding these differences helps you avoid migration failures. For example, a file named “Project Budget 2024#Final.xlsx” contains the # character, which SharePoint treats as a URL fragment. Renaming such files before migration prevents broken links.

Steps to Plan Your File Share to SharePoint Migration

1. Audit the current file share
   Run the SharePoint Migration Tool (SPMT) in scan mode or use a third-party tool like ShareGate to inventory all folders, file sizes, last-modified dates, and NTFS permissions. Export this data to a spreadsheet. Identify orphaned files older than three years and ask stakeholders whether those files can be archived or deleted.
2. Map permissions to SharePoint groups
   For each folder in the file share, list the NTFS security groups and individual users that have Read, Modify, or Full Control access. In SharePoint, map these to the default groups: Visitors (Read), Members (Contribute), and Owners (Full Control). If a folder needs unique permissions, plan to break inheritance on that folder and assign a separate SharePoint group. Document this mapping in the same spreadsheet.
3. Design the SharePoint site structure
   Create a site for each department or major project. Do not create one giant site with hundreds of libraries. For example, create “Finance” as a team site and “Marketing” as a communication site. Within each site, create document libraries that match the top-level folders from the file share. Use metadata columns such as “Project Name” or “Document Type” instead of deep folder hierarchies.
4. Choose a migration method
   Select one of these approaches:
   – Microsoft SharePoint Migration Tool (SPMT): Free tool that moves files to SharePoint or OneDrive. Supports incremental migration and permission mapping.
   – Third-party tool (ShareGate, Metalogix): Paid tools that offer advanced reporting, delta migrations, and version history preservation.
   – Manual upload: Drag and drop files through the browser. Only works for fewer than 100 files and no permission preservation.
5. Set up a migration schedule
   Plan a test migration with a small folder to verify file integrity and permissions. After the test passes, schedule the full migration in batches during off-peak hours. Allow two to four weeks for a file share with 500 GB of data. Inform users about the migration window and provide a read-only period for the source file share.
6. Validate the migration
   After each batch, compare file counts and folder structure between the source and destination. Use the SPMT report or a third-party validation tool. Check that permissions match the mapping spreadsheet. Test a sample of files by opening them in the browser and checking version history.

Common Mistakes to Avoid During Migration Planning

Copying the exact folder structure into SharePoint

File shares often have nested folders that are 10 levels deep. SharePoint performs best with flat folder structures and metadata. For example, instead of creating folders by year and then by month, add a “Date” column to the library and use views to filter by year. This reduces the number of folders and makes search faster.

Ignoring file name restrictions

SharePoint does not allow file names that start with a tilde (~), contain a hash (#), or end with a period. Use SPMT or a script to rename these files before the migration. Create a naming convention document that all users must follow after the move.

Migrating user permissions individually

In a file share, you might have 50 users with unique NTFS permissions on a single folder. In SharePoint, assign users to groups instead of setting individual permissions. Create a group called “Finance Readers” and add all users who need read access. This simplifies permission management and reduces the risk of broken inheritance.

Not planning for metadata and content types

File shares have no metadata columns. After migration, users lose the ability to sort by project name or document type unless you add those columns. Before migration, agree on a metadata schema with stakeholders. For example, add a “Department” column to the library and populate it during the migration using a CSV mapping file.

File Share vs SharePoint: Key Differences for Migration Planning

Item	File Share	SharePoint
Storage location	On-premises server hard drive	Microsoft 365 cloud datacenters
Permission model	NTFS ACLs on folders and files	Site groups and unique permissions on folders
File path limit	260 characters	400 characters
Version history	Not available by default	500 major versions per file
Co-authoring	Not supported	Supported for Office files
Metadata columns	Not available	Custom columns for filtering and sorting
Search	Windows Search or third-party	Microsoft Search across all sites
Blocked file types	No restrictions	Blocks .exe, .bat, .vbs, .cmd, .ps1 by default

You can now create a migration plan that covers inventory, permission mapping, site design, and validation. Start with a test migration of a single folder to confirm your approach works. After the full migration, enable version history and co-authoring to improve team collaboration. For large migrations over 10 TB, consider using the SharePoint Migration API with a third-party tool to handle incremental syncs and delta migrations.