Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Note
Cross-Tenant SharePoint migration is currently in a private preview stage of development. As an unfinished project, any information or availability is subject to change at any time. Support for private-preview customers will be handled via email. Cross-Tenant SharePoint migration is covered by the preview terms of the Microsoft Universal License Terms for Online Services.
This is Step 1 in a solution designed to complete a Cross-tenant SharePoint migration. To learn more, see Cross-tenant SharePoint migration overview.
- Step 1: Connect to the source and the target tenants
- Step 2: Establish trust between the source and the target tenant
- Step 3: Verify trust has been established
- Step 4: Precreate users and groups
- Step 5: Prepare identity mapping
- Step 6: Start a Cross-tenant SharePoint migration
- Step 7: Post migration steps
Before you begin
- Microsoft SharePoint Powershell. Confirm you have the most recent version installed. If not, Download SharePoint Management Shell from Official Microsoft Download Center.
- Be a SharePoint admin or Microsoft 365 Global admin on both the source and target tenants
Important
Microsoft recommends that you use roles with the fewest permissions. This helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role.
Connect to both tenants
Sign in to the SharePoint Management Shell as a SharePoint admin or Microsoft 365 Global admin.
Run the following entering the source tenant URL:
Connect-SPOService -url https://<TenantName>-admin.sharepoint.comWhen prompted, sign in to the source tenant using your Admin username and password.
Run the following entering the target tenant URL:
Connect-SPOService -url https://<TenantName>-admin.sharepoint.comWhen prompted, sign in to the target tenant using your Admin username and password.
Important
Microsoft 365 Multi-Geo customers: You must treat each geography as a separate tenant. Provide the correct geography-specific URLs throughout the migration process.