Cross Tenat Sharepoint Migration

Question

I need to carry out a cross tenant migration for SharePoint.

The process noted in Cross-tenant SharePoint site migration overview (preview) - Microsoft 365 Enterprise | Microsoft Learn is in Private Preview.

Is Microsoft going to enable this for Public Preview any time soon?

I would rather not have to sell my house to pay for a third party application to carry this out.

I have been advised that the pre-requisits are:

• Microsoft SharePoint Online Powershell. Confirm you have the most recent version installed. Download SharePoint Online Management Shell from Official Microsoft Download Center
• Confirm that the source SharePoint tenant does not have Service encryption with Microsoft Purview Customer Key enabled. If enabled on Source tenant, the migration will fail. Learn more on Service encryption with Microsoft Purview Customer Key
• Source SharePoint sites must be set to Read/Write. If set to Read only, the migration will fail.

However, I have downloaded and installed the most recent module.

Running Get-SPOSite | Select-Object Url, CustomerKeyEnabled I have established that no Service Encryption keys are enabled.

Attempting to establish trust between the tenants using Set-SPOCrossTenantRelationship I continually recieve the below:

This halts the Cross Tenant Migration imediately for SharePoint migration.

This contradicts that only the pre-requisits mentioned are required. Takes me to the statement:

To wrap this up, would I require a Enterprise License Agreement Plan to access this feature which is currently in "Private Preview"?

This is essentially moving data within Microsoft data centers, between two tenants that I administer. Is there a trime frame when this feature will be in Public Preview?

Answer 1

Hi @Marc Thornton - IT Server & Cloud Engineer ，

Welcome to Q&A forum!

As of now, the Cross-Tenant SharePoint migration feature is still in private preview and there is no information available regarding when it will be available for public preview.

Due to the limited information we can find, it is not possible to test and reproduce this issue at this time.

To help you better, we recommend you directly create a support ticket from Microsoft 365 Admin Center. The support team over there has the correct escalation channel, they can involve more resource and investigate the behavior from back end as fast as possible. They also can check the behavior on your end remotely. For reference: Get support - Microsoft 365 admin | Microsoft Docs, you can select online support or phone support to have a live chat with the support engineers.  

Good day!

---

If the answer is helpful, please click "Accept as Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.