Merger or acquisition
Bring people and workloads into a coordinated target environment.
Planning focus
Two organizations → agreed targetAlign identity, ownership and collaboration across organizations.
Begin with the business context
Different transitions.
Different migration decisions.
The destination design follows your operating model. Confirm who is moving, what needs to stay connected and who owns each decision.
Divestiture
Separate a business unit into its intended tenant context.
Planning focus
Parent organization → separated businessIdentify shared services, data boundaries and dependencies that remain.
Tenant consolidation
Reduce fragmentation across existing Microsoft 365 estates.
Planning focus
Multiple estates → a planned operating modelRationalize duplicate workspaces, access models and governance.
Map the relationships
Plan each workload
as part of the whole.
Explore the discovery, mapping and validation questions for your migration. This is a planning view, not a live tenant assessment.
Make identity the foundation of the move.
Content, collaboration and applications depend on users, groups and ownership. Agree the source-to-target identity model before defining migration waves.
01
Discover in the source
- Users, UPNs and domain context
- Security groups and Microsoft 365 groups
- Guests, sharing and permission references
- Owners and authentication dependencies
02
Map & prepare
- Source-to-target users and groups
- Domain and UPN changes
- Guest collaboration and ownership
- Permissions and application references
03
Validate in the target
- Target user and group readiness
- Effective access and ownership
- External collaboration behavior
- Application sign-in and dependencies
An identity mapping plan is a prerequisite for workload decisions. Copying content alone does not preserve every access relationship.
Move content with its context intact.
Plan source and target destinations alongside identity, information architecture and access. Decide how content, metadata and sharing will be checked after each wave.
01
Discover in the source
- Sites, libraries, lists and OneDrive accounts
- Files, versions and metadata
- Permissions and external sharing
- Pages, customizations and connected apps
02
Map & prepare
- Sites and target information architecture
- Source users and target OneDrive owners
- Content types and metadata mappings
- Sharing, URLs and dependency remediation
03
Validate in the target
- Content reconciliation and failed items
- Metadata and version behavior
- Permissions, owners and sharing
- Navigation, links and key user journeys
Migration fidelity and sharing behavior depend on the source, target design and selected tooling. Establish acceptance criteria before the pilot.
Plan the collaboration around the files.
Review the relationships between Teams, channels, groups, memberships and SharePoint-connected content. Document what the chosen migration approach supports.
01
Discover in the source
- Teams, channels and group relationships
- Membership, owners and guest access
- Files, tabs and connected SharePoint sites
- Apps, flows and third-party integrations
02
Map & prepare
- Target Teams and group structure
- Ownership and membership rules
- Connected sites and content destinations
- Workload-specific tooling and exceptions
03
Validate in the target
- Membership and effective access
- Files and collaboration journeys
- Tabs, apps and connected services
- Known limitations and business acceptance
Supported Teams fidelity depends on workload scope, tools and tenant configuration. Any unsupported elements need an agreed remediation or exception path.
Unpick tenant-specific dependencies.
Review Power Platform, SPFx and custom integrations as connected workstreams. Their configuration and authentication dependencies need their own migration decisions.
01
Discover in the source
- Power Apps, flows and Dataverse dependencies
- Connections, custom connectors and service owners
- SPFx packages, API permissions and App Catalog
- Custom APIs, external endpoints and hard-coded IDs
02
Map & prepare
- Target environment and deployment strategy
- Connections and environment variables
- Tenant URLs, identities and configuration
- Permissions, licensing and support ownership
03
Validate in the target
- App functionality and authentication
- Flows, connections and exception handling
- API access and deployed configuration
- Business-process tests and handover
Apps, flows and custom solutions should not be assumed to move automatically with SharePoint content. Implementation and specialist delivery are scoped explicitly.
From discovery to handover
Establish the path.
Prove it in the pilot.
Agree scope and responsibilities first. Use representative pilot evidence to refine the workload sequence, reporting and cutover decisions.
- 01
Discover & assess
Inventory both tenants, workloads, owners and dependencies. Agree scope and acceptance criteria.
Stage outputScope and risk register - 02
Map & prepare
Define identities, destinations, target configuration and remediation responsibilities.
Stage outputApproved mapping and target design - 03
Prove the pilot
Test representative users, content, access and connected business processes.
Stage outputPilot evidence and revised wave plan - 04
Migrate in waves
Sequence agreed workloads around dependencies, migration windows and business priorities.
Stage outputWave reports and exception tracking - 05
Validate & hand over
Reconcile the result, review user acceptance, stabilize and document ownership.
Stage outputAcceptance evidence and support handover
How migration waves are sequenced
Representative pilot
Test the selected approach against actual identities, content and business dependencies.
Controlled workload waves
Group users, sites or workloads by readiness, business priority and dependency.
Complex or critical workloads
Address blockers and rehearse acceptance checks before higher-risk moves.
Final transition & stabilization
Coordinate remaining changes, validation, support and agreed source-tenant cleanup planning.
Illustrative sequencing only. Wave design and timing depend on the assessment, tooling, access and business constraints.
Coordinate the transition
Cutover needs more
than a date in the calendar.
Agree readiness gates, decision owners and evidence before the business transition. Review the checks behind each gate.
Gate 01Identity & target readinessCan users and workloads operate in the destination?Explore readiness checks
- User and group mapping reviewed
- Target accounts and required access ready
- Agreed domain and UPN activities coordinated
- Application dependencies and service owners confirmed
Gate 02Business transitionCan the business work through the change window?Explore readiness checks
- Pilot findings addressed before the next wave
- Communications, freeze and support coverage agreed
- Delta or incremental moves planned where supported
- Go/no-go owners and escalation route documented
Gate 03Validation & contingencyIs there evidence for the transition decision?Explore readiness checks
- Source baselines and target checks defined
- Failed or skipped items have owners
- Business acceptance and exception criteria agreed
- Contingency options assessed where technically possible
Interruption, supported delta moves and contingency options must be assessed for the actual workload. A zero-downtime outcome is not assumed.
Make the work reviewable
Clear decisions.
A coordinated handover.
Define the outputs and acceptance criteria for the agreed work package, from assessment through delivery and stabilization.
Inspect a sample validation reportThe sample illustrates validation structure using fictional data. It is not a customer migration result.
- 01
Identity & workload mapping
Source-to-target users, groups, destinations, owners and dependency decisions.
- 02
Migration roadmap & wave plan
Readiness, remediation, tooling, pilot scope and sequenced workloads.
- 03
Cutover runbook
Communications, change windows, responsibilities, escalation and contingency decisions.
- 04
Validation & handover evidence
Reconciliation, exceptions, user acceptance, configuration notes and support ownership.
Specialist workloads and delivery boundaries
Exchange Online, Intune, endpoint management, complex Entra ID scenarios, third-party SaaS, telephony and compliance workloads may require specialist implementation or coordinated delivery. Tooling, licensing, application rebuilds and ongoing support are scoped explicitly. Confirm responsibilities and supported migration fidelity before implementation.
An appropriate first step
Bring both sides
of the tenant move into view.
Start with the source and target owners, your business transition and the decisions that need evidence.
Explore the assessment approachPeople
Source and target administrators, the migration sponsor and business process owners.
Context
Tenant overview, users, workload scale, known dependencies, deadlines and constraints.
Agreement
Assessment scope, access, deliverables, responsibilities and commercial terms before paid work.
Review the thinking
Technical guidance
for the next decision.
Use the guides and illustrative samples to discuss the approach and define the evidence your own migration needs.
Implementation guide
Tenant-to-tenant migration
Explore the planning considerations across tenants and connected workloads.
Explore resource Technical guideMigration validation
Review reconciliation, access checks, exceptions and acceptance evidence.
Explore resource Related serviceLegacy modernization
Assess forms, workflows and customizations that need remediation.
Explore resourceBefore you begin
Questions about
your tenant transition?
Clarify the scope, platform constraints and business expectations before setting a migration date.
Discuss your tenant migration (opens scheduling in a new tab)What does a tenant-to-tenant migration involve?
The agreed scope may include identity mapping, SharePoint and OneDrive content, Teams and group relationships, permissions, domains and application dependencies. Discovery establishes which workloads need migration, reconfiguration, remediation or specialist delivery.
How do permissions and guest access carry across?
Users, groups, ownership and external collaboration need source-to-target mapping and validation. Copying content alone does not guarantee equivalent permissions, guest access or sharing behavior.
Can Teams and Microsoft 365 groups be included?
They can be assessed within the migration scope, including channels, memberships, files, connected sites, tabs, apps and integrations. Supported fidelity depends on tools, tenant configuration and workload requirements; limitations need an agreed handling approach.
Do Power Apps, flows and SPFx move with the content?
Do not assume they do. Apps, flows, connections, environment variables, API permissions, tenant-specific configuration and deployment dependencies need separate assessment, migration or remediation planning.
How are domains, UPNs and URLs handled?
Review identity and domain changes alongside SharePoint and OneDrive URLs, hard-coded links, bookmarks, apps, flows and integrations. Define the responsibilities, timing and validation for any agreed changes in the cutover runbook.
Can you guarantee zero downtime?
No blanket zero-downtime promise is made. Business interruption, change windows, supported delta moves, validation and contingency options must be assessed against the actual workload and technical approach.
What is included in delivery, and what needs separate scope?
Scope, tooling, responsibilities and acceptance criteria are agreed before implementation. Exchange Online, Intune, endpoint management, complex identity scenarios, telephony, compliance and third-party SaaS may require specialist delivery or coordinated work packages.
How long will the migration take?
Duration depends on users, data volume, workload scope, dependencies, access, remediation, tooling, migration windows and validation depth. A representative pilot helps inform the wave plan and cutover decisions.
Plan the transition together
A new tenant.
A considered next step.
Discuss the business change, the workloads and what a useful first engagement would look like.
Discuss your tenant migration (opens scheduling in a new tab)Review the workload scope
Assessment, implementation and support are agreed as scoped engagements.