Migrate File Shares to SharePoint Online and Preserve Permissions
Question details
Determine how to migrate an on-premises file share to SharePoint Online while preserving applicable folder permissions without Azure AD synchronization.

- Product
- SharePoint Online and SharePoint Migration Tool
- Device & OS
- not provided
- Scenario
- An organization wants to move a file share with complex folder permissions to SharePoint Online but cannot synchronize its on-premises identities with Azure AD.
- Observed behavior
- The goal is to migrate the files and map source permissions to appropriate SharePoint Online users and groups, then verify access at the destination.
Inventory the source folders, NTFS permissions, and users or groups that need access. Confirm that corresponding Microsoft Entra ID users and groups exist and that you have the required source and SharePoint permissions.
Migrate with SharePoint Migration Tool and validate permission mapping
Use Microsoft's migration tool for a file share migration, with a pilot to check which permissions can be mapped without directory synchronization.
SharePoint Migration Tool can migrate file shares to SharePoint Online. Source identities must map to valid destination identities for their permissions to be applied; complex NTFS permissions and inheritance may not translate exactly.
In the SharePoint admin center, open Migration and select the file share migration option to find SharePoint Migration Tool. Install and sign in to the tool with an authorized Microsoft 365 account.
Create or identify the destination users and groups in Microsoft Entra ID. In the tool's migration settings, review the user mapping options and provide a user mapping file where needed, following Microsoft's current mapping-file documentation.
In SharePoint Migration Tool, add a file share source and select a SharePoint site and document library as the destination. Choose a representative folder with both inherited and unique permissions, and enable the applicable permission migration settings.
Start the migration, then open the tool's reports to check for unmapped identities, skipped permissions, and file errors. In the destination library, use Manage access on the migrated folders to compare access with the source.
Update the mapping file or adjust SharePoint access through Manage access as needed. Test with representative user accounts, then add and run the remaining file share migration tasks.

Evaluate a specialized migration tool for complex permissions
Consider a third-party migration solution when the pilot reveals permission mappings or reporting needs that the Microsoft tool cannot meet.
Work with migrated Office files in WPS Office
WPS Office is a free, lightweight Office alternative with a familiar interface and support for common Microsoft Office formats, helping users transition to a new productivity suite. It does not migrate file shares or preserve SharePoint permissions.

Frequently Asked Questions
Can I migrate permissions without Azure AD synchronization?
You can map source users to existing Microsoft Entra ID identities without synchronization, using the migration tool's supported mapping options. Test a pilot and review reports because unmapped identities and unsupported permission patterns may not migrate.
Will SharePoint reproduce every NTFS permission?
Not necessarily. SharePoint and NTFS use different permission models, so deny rules, inheritance, and complex folder access may require redesign. Check migrated folders with SharePoint's Manage access controls and test representative accounts.
How do I find permission mapping errors?
After a pilot run, open the SharePoint Migration Tool reports and look for unmapped users, skipped permissions, and other migration errors. Compare the results with the source permissions and destination folder access.
Can I script a file share migration to SharePoint Online?
Yes. Microsoft provides SharePoint Migration Tool PowerShell cmdlets for scripted migrations. Follow Microsoft's current documentation for registration, task configuration, and execution, and validate permission mapping with a pilot before scaling up.




