Microsoft 365 Tenant-to-Tenant Migration Planning and Support
Move SharePoint, OneDrive, Teams, and other Microsoft 365 workloads between tenants with a clear scope and fewer surprises at cutover.
Mergers, acquisitions, divestitures, and tenant consolidation all end in the same place: people, content, and permissions have to move from one Microsoft 365 tenant to another while the business keeps working. I help plan that move, coordinate the workloads, and validate the result.
16+ years with SharePoint and Microsoft 365 100 TB+ of content assessed and migrated across projects Microsoft 365 Certified: Administrator Expert Based in Vancouver, BC Remote across Canada
When a tenant-to-tenant migration comes up
- Two companies are merging, or one has acquired another, and both run their own Microsoft 365 tenant.
- Part of the organization is being divested and needs its own Microsoft 365 environment.
- Several tenants grew up over the years and you want to consolidate them into one.
- A restructuring moves a department or subsidiary into a different tenant.
Microsoft 365 workloads I can help migrate
I've worked on several Microsoft 365 tenant-to-tenant migration projects, with my strongest hands-on experience in SharePoint Online, OneDrive, and Microsoft Teams.
I also help organizations plan and deliver broader Microsoft 365 migrations involving services such as Exchange Online, Microsoft Entra ID, and related workloads.
Every tenant migration is different. During discovery, I review which workloads need to move, their dependencies, available migration methods, licensing requirements, and the responsibilities involved.
For each workload, we agree on the migration approach, what's included, what may need to be recreated or reconfigured, and how the results will be validated.
The goal is a coordinated migration that preserves the information and functionality your organization needs, while making limitations and risks clear before cutover.
What needs to be assessed before moving tenants
- Users and identity
- Who moves, how source accounts map to target accounts, and which groups and memberships have to exist on the other side.
- Domains
- Which domains move, when, and what depends on them, such as sign-in names and email addresses.
- Permissions and sharing
- Site and library permissions, sharing links, and guests, and how access will be checked after the move.
- Teams content
- Channels, files, chats, and meetings have different migration requirements and tool limits, so each is planned on its own.
- Apps and workflows
- Power Apps, Power Automate flows, and custom solutions are not automatically migrated with SharePoint sites. Depending on the workload and migration tools, they may need separate migration, reconfiguration, reconnection, or rebuilding.
- Licensing, tools, and compliance
- Target licences, the migration method for each workload, and any retention or compliance requirements that apply in both tenants.
How I approach a tenant-to-tenant migration
- 1
Discovery
Which workloads and users are in scope, the deadline, and the business reason for the move.
- 2
Workload and dependency assessment
What each workload contains, what depends on it, and which migration method fits.
- 3
Migration strategy
Waves, identity and permission mapping, coexistence, and who is responsible for what.
- 4
Pilot and validation
Where feasible, pilot the chosen migration approach with a small set of users or content. Validate the results and address issues before the main cutover.
- 5
Migration execution and cutover
Execute the agreed migration sequence, whether phased or coordinated, with appropriate validation and checks at each stage.
- 6
Post-migration support
Fixing access and content issues that users find, and a handover to your team.
What you receive
The exact set depends on the engagement. A typical planning engagement includes:
- An inventory of the workloads in scope
- A migration scope and a responsibility matrix
- The approach for mapping identities and permissions
- A migration wave plan
- Cutover and validation checklists
- The risks that need a decision before cutover
Relevant migration experience
I've worked on several Microsoft 365 tenant-to-tenant migration projects, with my strongest hands-on experience in SharePoint Online, OneDrive, and Microsoft Teams.
Across my broader migration work, I've assessed and migrated more than 100 TB of content.
The SharePoint migration consulting page explains my general migration approach, and the case studies demonstrate related migration and governance experience.
Frequently asked questions
Can you migrate our SharePoint sites, OneDrive files and Microsoft Teams to another tenant?
Yes. These are my strongest areas of tenant-to-tenant migration experience. I assess the workloads, their dependencies, and the migration methods before recommending a plan.
Can you also help with Exchange Online and other Microsoft 365 workloads?
Yes. I can help plan and support broader Microsoft 365 migration requirements. The implementation scope, technical dependencies, and responsibilities for each workload are defined during discovery.
Will Microsoft Teams chats, channels and files all move automatically?
Not necessarily. Different types of Teams content have different migration requirements and tool limitations. I review what needs to move, what can be migrated, and what may require separate handling or reconfiguration.
How do you handle permissions and user identities during migration?
I review source and target identities, group membership, sharing requirements, and access dependencies. The migration plan includes the mapping and post-migration validation, so access can be checked against business requirements.
Can we migrate in phases instead of moving everyone at once?
Depending on your environment and the migration approach, a phased migration may be possible. I assess coexistence requirements, dependencies, cutover timing, and validation before recommending the migration sequence.
Related
Planning a Microsoft 365 tenant-to-tenant migration?
Whether you're consolidating tenants, supporting a merger, or moving part of your organization into a new Microsoft 365 environment, I can help assess the technical scope and plan the transition. Tell me which workloads need to move, approximately how many users are involved, and your target timeline.
Discuss a tenant-to-tenant migration