Migrating a SharePoint subsite to another account or tenant can be a complex task, especially with Microsoft’s move toward a modern SharePoint architecture that discourages the use of subsites. However, many organizations still use subsites, and there are valid scenarios where you need to migrate a subsite from one SharePoint Online account to another.
This guide provides a step-by-step approach to help you successfully migrate a SharePoint subsite to another tenant or user account, covering manual and automated methods, best practices, and common pitfalls to avoid.
Why Migrate a SharePoint Subsite?
Several scenarios may require you to migrate a subsite to another account:
- Mergers and acquisitions
- Departmental restructures
- Compliance or governance requirements
- Moving from a subsite-based structure to a hub-site or flat structure
- Migrating between Microsoft 365 tenants
Challenges with Subsite Migration
Before starting the migration process, it’s essential to understand the limitations:
- SharePoint Online does not natively support subsite-to-subsite or subsite-to-site collection migrations.
- Metadata, permissions, and version history can be difficult to preserve.
- Custom scripts may be required to maintain structure and data integrity.
- Microsoft encourages a flat site structure using hub sites, making subsite migration a deprecated scenario.
Also read: How to Change SharePoint Site from Private to Public
Pre-Migration Checklist
Before you start the migration process:
- Perform a content audit on the subsite
- Remove unused lists, libraries, and workflows
- Review permissions and groups
- Determine the migration destination structure
- Inform users of the planned migration and expected downtime
- Back up all data
- Test migration on a sample subsite, if possible
Methods to Migrate SharePoint Subsite to Another Account
There is no direct solution to move SharePoint subsite to another account. Still, here are some practical methods which can help in this, i.e.
Method 1: Manual Migration Using Save as Template (Limited Use)
- Go to your subsite.
- Click Gear Icon > Site Settings > Save site as template.
- Check Include Content (optional).
- Download the .wsp template file.
- Go to the destination account’s SharePoint Admin Center.
- Upload the .wsp file under Solutions in the Site Collection settings.
- Create a new site using the template.
Method 2: Use Automated Migration Tools (Recommended for Accuracy)
SharePoint Online Migration Solution is a reliable and user-friendly solution designed to simplify the process of migrating SharePoint content between sites, site collections, or even across tenants. It supports the transfer of documents, lists, libraries, permissions, metadata, and version history with high accuracy.
The tool is especially useful for organizations looking to perform SharePoint Tenant to Tenant migration or consolidate content from multiple SharePoint sources. With features like incremental migration, detailed progress reports, and a user-friendly interface.
Method 3: PowerShell and PnP Scripts (Advanced Users)
If you’re experienced with scripting, you can use PnP PowerShell to extract and import content.
Step 1: Connect to Source and Export
Connect-PnPOnline -Url https://source.sharepoint.com/sites/yoursite -UseWebLogin
Get-PnPProvisioningTemplate -Out template.xml -IncludeAllTermGroups
Step 2: Connect to Target and Import
Connect-PnPOnline -Url https://destination.sharepoint.com/sites/newsite -UseWebLogin
Apply-PnPProvisioningTemplate -Path template.xml
Post-Migration Best Practices
After successfully migrating a SharePoint subsite:
- Verify permissions and access for users
- Recreate or update navigation links
- Test key lists, libraries, and workflows
- Update any Power Automate flows or connected apps
- Decommission or archive the old subsite
Read also: Set Retention Policy in SharePoint Online
Conclusion
Migrating a SharePoint subsite to another account or tenant is not straightforward due to platform limitations and Microsoft’s move toward modern architecture. However, using the right tools and approach, especially automated migration software, can ensure a smooth and accurate migration.
If you’re planning a migration, always perform a trial run, document your steps, and communicate with your stakeholders to minimize disruption.
Frequently Asked Questions (FAQs)
Q1. Can I migrate a subsite to another tenant directly?
Not directly with Microsoft tools. You need automated tools like ShareGate or use PowerShell scripts.
Q2: What happens to permissions after migration?
Permissions may break if users/groups are not mapped correctly. Use tools that allow permission mapping.
Q3: Can I migrate subsites in bulk?
Yes, automated tools support bulk migration.
Q4: Can I automate subsite migration?
Only partially. Scripting can automate content extraction, but tools like ShareGate are more efficient.
