How to Copy SharePoint Pages Between Microsoft 365 Tenants
Question details
The user needs to move or copy SharePoint pages from one Microsoft 365 organization's tenant to another.

- Product
- Microsoft SharePoint
- Device & OS
- not provided
- Scenario
- Performing a cross-tenant migration of SharePoint site pages between two distinct Microsoft 365 organizations.
- Observed behavior
- Standard page-copy commands, such as the Copy-SPOPersonalSitePage cmdlet, fail to transfer pages because they are restricted to operating within a single SharePoint tenant.
Ensure you have Global Administrator or SharePoint Administrator credentials for both the source and target Microsoft 365 tenants before initiating any cross-tenant migration tasks.
Use a Third-Party Tenant Migration Tool
The most efficient and reliable method for cross-tenant SharePoint migrations, ensuring complex page structures are preserved.
Because native PowerShell cmdlets like Copy-SPOPersonalSitePage are restricted to intra-tenant transfers, moving pages between completely different Microsoft 365 tenants requires external solutions. Specialized third-party tools provide the necessary mapping features to bridge distinct Microsoft 365 environments safely.
Choose a reputable Microsoft 365 migration software provider that explicitly supports cross-tenant SharePoint migrations (e.g., ShareGate, AvePoint, or BitTitan).
Launch your chosen migration tool and sign in with Global Administrator credentials for both the source Microsoft 365 tenant and the destination Microsoft 365 tenant.
Configure the tool by mapping the source SharePoint site URLs to your new destination site URLs, and ensure user identity mappings are set up correctly.
Select a single SharePoint page to migrate first. Execute a test run to verify that web parts, layouts, and formatting transfer correctly to the target tenant.
Once verified, start the bulk migration process for all required pages. Review the post-migration error logs provided by the tool to catch any failed transfers.

Manually Recreate SharePoint Pages
Use this manual approach if you only need to copy a small number of simple pages and do not want to purchase third-party software.
Looking for a Lightweight Alternative for Your Daily Office Tasks?
While migrating complex SharePoint environments requires specialized IT tools, your everyday document editing shouldn't be complicated. WPS Office provides a free, highly compatible, and lightweight alternative to Microsoft Office for creating and managing your workflow.
- 1. Download the installer: Visit the official WPS Office website and click the download button for your operating system.
- 2. Install the software: Run the lightweight installer and follow the quick on-screen instructions to set up the suite.
- 3. Open your documents: Launch WPS Office and instantly open your existing Word, Excel, and PowerPoint files with full format retention.

Frequently Asked Questions
Can I use PowerShell to copy pages between different Microsoft 365 tenants?
No. Standard PowerShell cmdlets, including Copy-SPOPersonalSitePage, are designed exclusively for operations within the same SharePoint tenant. They cannot authenticate or transfer data across tenant boundaries.
Will page version history transfer during a cross-tenant migration?
If you recreate pages manually, version history is entirely lost. If you use a premium third-party migration tool, you can usually configure the software to retain and transfer page version history to the new tenant.
Is there a native Microsoft tool for cross-tenant SharePoint migrations?
Microsoft provides native cross-tenant migration capabilities primarily for Exchange mailboxes and OneDrive for Business. However, comprehensive SharePoint site and page migrations between tenants typically require third-party solutions.
Do I need to migrate custom web parts separately?
Yes. Custom web parts built using the SharePoint Framework (SPFx) must be separately deployed to the target tenant's App Catalog before you migrate the pages that utilize them; otherwise, the web parts will fail to load on the copied pages.




