SharePoint Online is often one of the most business-critical workloads in a Microsoft 365 tenant, supporting intranets, departmental collaboration, document management, knowledge repositories, automated processes, and content shared through Microsoft Teams. During a merger, acquisition, divestiture, or tenant consolidation, organizations frequently assume that moving SharePoint sites and documents to another tenant will preserve the existing experience. In practice, successful migration involves much more than transferring files because a SharePoint site is an interconnected ecosystem where documents depend on metadata, content types, permissions, search configurations, sharing links, custom applications, and automated workflows.
Moving content without planning for these underlying dependencies can leave users with inaccessible documents, broken business processes, inconsistent search results, or an intranet that no longer reflects the organization’s structure. While Microsoft provides a native cross-tenant SharePoint migration capability for supported scenarios, enterprise IT teams must understand the distinction between migrating raw site content and recreating the complete SharePoint experience in the destination tenant. This article examines the architectural, technical, and governance considerations that enterprise IT teams should address before migrating SharePoint Online between Microsoft 365 tenants.
The Cross-Tenant Migration Model & Dependencies
Microsoft’s native cross-tenant SharePoint migration capability supports moving several site types between tenants—including M365 Group-connected team sites, modern communication sites, and classic sites. However, migrating a Teams-connected SharePoint site does not automatically move associated Teams channels or conversations. Teams requires its own distinct migration strategy.
| Component | Planning & Migration Expectation |
| Documents & Folders | Supported content and folder structures migrate subject to service limitations. |
| File Versions & Basic Metadata | Preserves version history, created/modified dates, and author properties. |
| User & Group Permissions | Continuity depends strictly on accurate identity mapping and target group provisioning. |
| Existing Sharing Links | Supported file links redirect to target locations, subject to migration and access rules. |
| Hub Site Relationships | Requires manual re-registration and re-association in the target tenant. |
| Custom Metadata & Term Sets | Custom columns, content types, and managed metadata term sets must be validated separately. |
| Document ID Functionality | Requires target service configuration and validation rather than assuming automatic continuity. |
| Workflows & SPFx Apps | Classic workflows (2010/2013) do not auto-transfer; custom SPFx solutions require redeployment. |
Rebuilding Information Architecture & Permissions
Hub Sites & Navigation
Hub sites organize modern intranets through shared navigation, branding, and search boundaries. Moving an individual site does not automatically re-establish its hub association.
To rebuild your architecture cleanly:
- Inventory the source architecture: Document registered hubs, associated sites, site owners, and shared navigation.
- Design the target state: Map source hubs to target hubs and decide whether to preserve or modernize navigation.
- Configure & validate: Register hub sites in the target tenant, re-establish associations, and verify search boundaries and access permissions.
Identity Mapping & Unique Permissions
Permissions are among the highest-risk aspects of a tenant migration. Matching names is not enough—a user named [email protected] must be mapped explicitly to [email protected] via an authoritative identity mapping register.
Before migrating, inventory libraries with broken permission inheritance, guest user access, and orphaned content owned by former employees. Validate access using test personas (Owners, Members, Visitors, and External Guests) rather than relying solely on administrator confirmation.
Metadata, Document IDs, and Customizations
- Metadata & Taxonomy: Custom columns, content types, and taxonomy term sets (Managed Metadata) power views, compliance rules, and search refiners. Establish a metadata baseline prior to cutover to verify that file properties carry over accurately.
- Document ID Continuity: If your organization relies on Document IDs for regulatory traceability or links embedded in external systems, treat Document ID preservation as an explicit acceptance criterion.
- Modernizing Workflows: Legacy SharePoint Designer workflows are not supported as active destination workflows. Cross-tenant migrations offer the ideal opportunity to modernize legacy automation into Power Automate.
- SPFx & App Deployment: SharePoint Framework (SPFx) solutions require a release-management approach: verify source code, target App Catalog deployment, API permissions in Microsoft Graph, and tenant-specific configuration settings before cutover.
Migration Waves & Prioritization Matrix
Not every site should be migrated in the same wave. Categorize your site inventory by complexity and risk profile:
| Migration Category | Characteristics | Recommended Priority |
| Standard Collaboration | Simple permissions, standard libraries, low complexity | Early pilot / Wave 1 |
| Departmental Repositories | Custom metadata, established ownership, moderate risk | Wave 2 |
| Hub Sites & Intranets | Shared navigation, branding, central architecture | Coordinated, architecture-led wave |
| Document Repositories | Complex metadata, Document IDs, formal compliance rules | Dedicated validation wave |
| Highly Customized Sites | SPFx apps, custom forms, legacy workflows, API calls | Early assessment, controlled wave |
| Regulated Repositories | Retention policies, sensitivity labels, audit mandates | Compliance-led planning & explicit sign-off |
SharePoint Cross-Tenant Readiness Checklist
Before approving production cutover, ensure your team completes key verification milestones across six critical domains:
- Architecture & Discovery: Inventory all sites, hub relationships, site owners, and native tool prerequisites.
- Identity & Permissions: Pre-create target identities/groups, validate mapping files, and test guest access policies.
- Metadata & Document Identity: Provision term sets, document custom schema dependencies, and build a URL/ID cross-reference strategy.
- Links & Applications: Audit sharing link redirection, rebuild/modernize legacy workflows, and deploy SPFx packages to the target App Catalog.
- Governance & Compliance: Re-align sensitivity labels, DLP rules, retention policies, and tenant sharing boundaries.
- Testing & Cutover: Execute a multi-site pilot, reconcile post-migration content counts, and secure formal business-owner sign-off.
How Olive + Goose Can Help
Navigating a cross-tenant Microsoft 365 migration requires a balance of deep technical architecture, security governance, and hands-on execution. At Olive + Goose, our enterprise migration specialists partner with your IT leadership to eliminate risk and protect operational continuity.
We support enterprise organizations across every phase of the migration journey:
- Discovery & Migration Assessment: Complete structural audits, customization analysis, and risk-prioritized wave planning.
- Target Architecture & Governance Design: Designing future-proof hub hierarchies, identity mappings, and security baseline policies.
- Custom Solution Remediation: Modernizing legacy SharePoint Designer workflows to Power Automate and redeploying complex SPFx packages.
- Migration Execution & Cutover Support: Hands-on execution, automated reconciliation, pilot testing, and post-migration stabilization.
Whether preparing for a merger, acquisition, divestiture, or tenant consolidation, contact Olive + Goose today to discuss your SharePoint migration strategy.
Explore Our Microsoft 365 Cross-Tenant Migration Series
Catch up on earlier insights from our tenant-to-tenant migration guidance:
