There is no direct effective way to meet your requirement. As a workaround, you could create a tenant and migrate the content to the new tenant.
However, in the manual method, users need to run PowerShell cmdlets scripts, which require great technical expertise. A minor mistake or mis-stype in these scripts can result in multiple errors and failures in this migration process. Moreover, PowerShell has its own limitations as it does not maintain the data integrity and folder structure or hierarchy. Moreover, it can hamper the running business by creating a temporary communication halt. Hence, organizations must understand the downtime and shortcomings involved in this manual approach. In this way, this becomes a tedious and time-consuming approach to follow for this data transfer operation.
Most customers work with Microsoft Consulting Services or a Microsoft partner to migrate tenants, including using third-party tools to migrate content.
You could refer to these articles for more details:
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
If the answer is helpful, please click "Accept 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.
HI Yi Lu,
I suggested above suggestion, we are planning to implement that, thank u