Migrate SharePoint 2010 Groups and Permissions to SharePoint Online Using AvePoint
Question details
The user is looking for documentation and guidance on how to properly transfer SharePoint 2010 groups, memberships, and site permissions to SharePoint Online using the AvePoint migration tool.

- Product
- SharePoint 2010 / SharePoint Online / AvePoint
- Device & OS
- not provided
- Scenario
- Migrating access controls, groups, and user permissions from an older SharePoint on-premises environment to Microsoft 365.
- Observed behavior
- Seeking the correct procedure and official documentation for ensuring permissions are accurately mapped during the third-party migration process.
Ensure you have administrative access to both your SharePoint 2010 on-premises environment and your destination SharePoint Online tenant, and verify that your users are properly synced to Microsoft Entra ID (Azure AD) before beginning the migration.
Contact AvePoint Support for Official Migration Documentation
Because AvePoint is a third-party migration product, the most accurate and up-to-date procedures for migrating complex elements like groups and permissions will come directly from their official support channels.
Migrating permissions from on-premises SharePoint to Microsoft 365 requires specific mapping of legacy accounts to cloud identities. Third-party tools handle this mapping differently.
To ensure compliance and accuracy, it is highly recommended to follow the software vendor's proprietary guidelines rather than generic migration advice.
Navigate to the official AvePoint website and log into your customer or partner portal using your organizational credentials.
Locate the 'Support' or 'Help Center' section in the navigation menu and search for 'SharePoint 2010 to SharePoint Online migration guide'.
Look specifically for documentation regarding user mapping, group migration, and permission conflict resolution within the AvePoint FLY migration tool (or your specific AvePoint product).
If specific documentation on groups and permissions isn't found, open a support ticket detailing your current SharePoint 2010 setup and destination tenant to receive specialized guidance.

Leverage IT Community Forums for Practical Guidance
Other organizations frequently perform similar complex migrations and share their step-by-step experiences, custom mapping scripts, and solutions to common permission errors on community forums.
Need a Lightweight Alternative for Document Management? Try WPS Office
While managing complex SharePoint and cloud migrations, your team still needs reliable tools to handle daily document tasks. WPS Office provides a free, lightweight, and highly compatible alternative to Microsoft Office, ensuring your team stays productive without heavy resource overhead during IT transitions.

Frequently Asked Questions
Does the official Microsoft SharePoint Migration Tool (SPMT) migrate permissions?
Yes, the official Microsoft SharePoint Migration Tool (SPMT) can migrate files, lists, and permissions from SharePoint 2010/2013 to SharePoint Online. However, you must ensure that your on-premises Active Directory is properly synced with Microsoft Entra ID so the tool can map the permissions correctly.
What happens if a SharePoint 2010 user doesn't exist in Microsoft 365 during migration?
During migration, if an on-premises user account cannot be mapped to an active identity in Microsoft 365, their permissions generally will not transfer. Depending on the migration tool and its configuration, the tool may drop the permissions or map the orphaned user's files and permissions to a designated default admin account.
Can I migrate SharePoint permissions without migrating the underlying content?
Most migration tools generally require that permissions be migrated alongside or immediately after the content (sites, lists, libraries) is provisioned in the destination environment. Check your specific vendor documentation for 'permissions only' or incremental migration features.
Why use a third-party tool like AvePoint instead of Microsoft's free tools?
Third-party tools often offer more granular control, detailed pre-migration reporting, advanced scheduling options, and complex identity mapping capabilities. These are especially useful for large-scale migrations that involve heavy customizations, legacy workflows, or strict regulatory compliance requirements.




