Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


Jonah Scott
2026-11-20T12:51:45Z
One issue that deserves attention during a SharePoint tenant migration is what happens to existing permissions. A document library may contain folders accessible only to specific departments, project teams, or external collaborators. If these access rules are not reviewed before the move, employees may find that they cannot open important files, while other users may receive access they should not have.

Before migration, administrators should prepare a permission inventory for important sites, libraries, folders, and individual documents. Identify site owners, Microsoft 365 groups, external guests, and users who are changing accounts as part of the tenant transition. It is also useful to document unique permissions and sharing arrangements instead of assuming that every item follows the site's default access settings.

The SysInfo SharePoint Migration Tool  can transfer supported SharePoint content, including sites, generic lists, document libraries, custom columns, and metadata. However, its documented limitations state that SharePoint permissions are not migrated. Administrators should therefore plan to configure the required permissions separately in the destination tenant.

When evaluating a sharepoint migration tool (spmt), check its actual permission-handling capabilities. Some migration solutions support identity mapping or permission transfer in particular scenarios, while others focus primarily on content. These differences can affect the overall migration plan, especially when several departments share the same SharePoint environment.

A practical approach is to create a permission matrix before moving the data. Record who needs access, the level of access required, and whether external sharing should continue. After migration, test access using representative user accounts rather than relying only on an administrator's view.

The Microsoft SharePoint migration tool selected for a project should also be assessed for its handling of file versions, metadata, lists, and workflows. Content migration and permission configuration are separate tasks, and both need validation before users begin working in the new tenant.

A suitable sharepoint data migration tool should fit into a broader migration checklist that includes access reviews, content verification, and post-migration testing.

How does your IT team handle unique folder permissions and external sharing when moving SharePoint sites between tenants?
Sponsor
Forum information
Scroll to Top