Dedicated Cross-Tenant SharePoint Migration: Step-by-Step, Licensing, and Post-Move Remediation

-

Dedicated cross-tenant SharePoint migration is the workload-specific method for moving SharePoint sites between tenants using SharePoint Online PowerShell. Use it when you need to migrate shared sites (including Teams-connected SharePoint sites), which are out of scope for Orchestrator.

Scope and key constraints

·       Up to 4,000 SharePoint migrations can be scheduled at a time.

·       One-and-done: no incremental/delta passes; redirects are left behind.

·       Supported site types include group-connected sites (including those associated with Teams), modern non-group sites, classic sites, and communication sites.

·       This does not migrate Teams content, channels, or associated structure; for Teams-connected sites, only the SharePoint site content is migrated.

·       Do not precreate target SharePoint sites; if the site already exists, the migration fails (no overwrite/merge).

·       Limits: 5 TB per site and 1 million items per site. Path length limit is 400 characters.

Licensing note (SharePoint shared data migration)

Microsoft describes Cross-Tenant Shared Data Migration licenses (for SharePoint) as currently available only to Enterprise Agreement customers, and offered per 100 GB of data moved. Confirm the latest licensing and purchasing model with your Microsoft account team.

Step-by-step: connect, establish trust, map identities, and start site moves

# 1) Connect to the SharePoint admin endpoints
Connect-SPOService -Url https://<TenantName>-admin.sharepoint.com

# 2) Establish trust (run on both source and target)
Get-SPOCrossTenantHostUrl
Set-SPOCrossTenantRelationship -Scenario MnA -PartnerRole Target -PartnerCrossTenantHostUrl <TargetCrossTenantHostUrl>
Set-SPOCrossTenantRelationship -Scenario MnA -PartnerRole Source -PartnerCrossTenantHostUrl <SourceCrossTenantHostUrl>

Then, after uploading the required identity mapping data and validating compatibility, start your moves, for example:

Start-SPOCrossTenantSiteContentMove -SourceSiteUrl <sourceSiteUrl> -TargetSiteUrl <targetSiteUrl> -TargetCrossTenantHostUrl <targetHostUrl>

Post-move remediation (plan this, do not improvise)

Microsoft calls out several categories that often require recreation or reconfiguration after SharePoint site migration: classic workflows (2010/2013), apps, Power Apps/Power Automate connections, web parts that reference other services, and sensitivity label behavior. Plan a remediation sprint and test the high-value business processes that depend on these components.

Source links (Microsoft Learn)

·       https://learn.microsoft.com/en-us/microsoft-365/enterprise/cross-tenant-sharepoint-migration?view=o365-worldwide

Comments

Post a Comment

Popular posts from this blog

Skype for Business, Lync and Exchange Web Services (EWS) and different DNS Domains- Exchange crawling e.g. for presence

-
Image
Hi all, (This is an updated version 2.2: 09 .07.201 5 ) This blog entry is valid for Lync 2010, Lync 2013 and Skype for Business Server. Generally, I'll write a new blog article, since the conversion history over multiple device and other service have change with Skype for Business 2015 Server. Once this written, I post the link here. there is always confusion in how Lync is crawling Exchange Web Services (EWS). Generally it is necessary to understand how DNS must be implemented: Just remember, identify if you have DNS Split configuration, different internal and external DNS names and what are your SMTP and SIP Domains. Very often you find in Lync/ Exchange deployments an issue, where the Lync configuration show up with empty: EWS Internal URL EWS External URL and EWS Information = EWS not deployed Therefor Exchange Web Service are not connected deployed and several Lync Integration Features are not working, e.g. Presence Information based on your Outlook Calendar....
Read more

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modif...
Read more

Exchange x500 address x500:/o=ExchangeLabs

-
Image
 You have Exchange Hybrid in place. Now you wonder about an address with you see on-premises with all users. This address has the following format: x500:/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOxxxxxx)/cn=Recipients/cn=234xxxx This address is now found in the Exchange proxyAddresses in On-Premises as well as in Entra ID. Additionally you will see them in msExchShadowProxyAddresses The ExchangeLabs is Microsoft internal Exchange Online Organization and therefore needed. This x500 address is created in Exchange Online and sync'ed via Azure AD Connect (Entra ID Connect) back on-premises. If you delete this address on-premises, the connection between will sync this Cloud leading attribute back to on-premisses. If you have multiple Domains and Active Directories connected to your Tenant, this x500 address from your tenant will be added to ALL users. Also to users which are from an local AD without Exchange / Exchange Hybrid. As long AAD Connect/ Entra ID Connect will...
Read more