Do you want MSAdvance to handle your entire Microsoft 365 tenant-to-tenant migration?
MSAdvance provides end-to-end support for Microsoft 365 tenant-to-tenant migrations, with a focus on business continuity, controls to preserve the information within scope, user adoption and the organisation’s operational requirements.
We design the Microsoft 365 tenant-to-tenant migration strategy, coordinate with the internal IT team and protect the end-user experience, taking care of both the technical side and the communication and change management.
- Architecture and governance design for the new Microsoft 365 organisation.
- Coexistence plan (identity, email, calendars, files, Teams) tailored to the business requirements.
- Adoption support and assistance during go-live and stabilisation.
A Microsoft 365 tenant-to-tenant migration (also called an Office 365 tenant-to-tenant migration) is a project to transfer the data and services within scope from one Microsoft 365 tenant to another, prepare the target identities, recreate the necessary settings and re-enrol devices where required. Validation checks help preserve information and reduce disruption to day-to-day operations. It is commonly needed for mergers and acquisitions (M&A), divestitures or the consolidation of several tenants into one. A domain or partner change may be handled within the existing tenant and should be assessed before committing to a migration. The method is selected for each workload and its requirements: native Microsoft capabilities, specialist tools or a combination. CTUDM is the licensing add-on that enables supported native user-data migration capabilities. Microsoft’s migration orchestrator covers Exchange Online, OneDrive, Teams chats and Teams meetings, subject to specific limits and identity preparation requirements.
Quick summary: Microsoft 365 tenant-to-tenant migration in 7 key points
- When it is required: mergers and acquisitions, carve-out or spin-off and the consolidation of several Office 365/Microsoft 365 tenants. Rebranding, a domain change or a partner change only justifies a new tenant when there are additional separation, architecture or governance requirements.
- Workloads and configuration: Exchange Online email and calendars, OneDrive, SharePoint and Microsoft Teams; the scope may also include Intune-managed devices, Power Apps, Power Automate, Dataverse and Power BI. Target identities must be prepared, security and compliance policies recreated, and devices joined or re-enrolled using the appropriate procedure.
- Microsoft’s migration capabilities: CTUDM (Cross-Tenant User Data Migration) and its orchestrator for supported user workloads: mailboxes, OneDrive, Teams chats and meetings. Entra ID provides coexistence capabilities, while SharePoint follows a separate procedure using Cross-Tenant Shared Data Migration. Each option has its own prerequisites, licensing requirements and exclusions.
- Project pillars: a thorough assessment of the current environment, a migration method selected for each workload, well-designed coexistence, security and compliance from day one, and a rehearsed domain move when it is included in the project.
- Typical risks: late procurement of migration licences, incompatible provisioning in the target tenant, an unprepared domain move, underestimated Power Platform and Power BI dependencies, untested links or permissions, missing retention and labelling policies, and insufficient user communication.
- Effort and roles involved: IT, security, business (process owners), legal/compliance in regulated sectors and, in many cases, a specialised partner that coordinates both the technical work and change management.
- When it makes sense to rely on a partner: when the organisation is going through M&A, when there are strong regulatory requirements, when there are multiple legacy tenants or when you want to minimise the risk of disruption and data loss.
When do you need a Microsoft 365 tenant-to-tenant migration?
Not every organisation needs a Microsoft 365 / Office 365 tenant-to-tenant migration. However, separation, integration or governance requirements can make this type of project necessary. Identifying the business scenario helps establish the effort, risks and available alternatives.
Typical scenarios
- Mergers and acquisitions (M&A): one company acquires another that already uses Microsoft 365. There are two tenants and the goal is to consolidate people, email, documents and security into a single environment.
- Carve-out or spin-off: part of the business is separated and needs its own tenant (new legal entity, new domain, new leadership team), moving only a subset of users and data.
- Rebranding or corporate domain change: the organisation changes its brand and email domain, requiring a review of domains, UPNs and identities. These changes can be made within the current tenant; a migration is considered when the organisation also needs a different Microsoft 365 tenant.
- Consolidation of legacy tenants: there are several Office 365/Microsoft 365 tenants inherited from previous acquisitions and the organisation wants to simplify management, licensing and governance.
- Partner or licensing model change: the organisation changes its CSP or partner and reviews its administration or procurement model. Changing the licensing provider can preserve the same tenant and its data; moving part of the organisation to another tenant requires a separate architecture or separation decision.
- Global reorganisation: multinational groups that want to move from a country-based model to a regional or corporate model, unifying tenants by region or line of business.
In all these cases, the practical question is not just “how to migrate”, but “what to migrate, what to leave in the source tenant, what to rebuild from scratch and in which order to do it” to minimise the impact on operations.
Alternatives to consider before changing tenants
Before authorising a migration, compare the intended outcome with changes that preserve the existing environment: adding a domain and updating UPNs and SMTP addresses, transferring subscriptions between partners, reviewing administrative access, or renaming the SharePoint domain where supported. These operations have their own prerequisites and will not resolve every divestiture, but they may avoid moving data when the objective is limited to procurement or branding.
A divestiture may require a separate tenant even if the organisation initially uses a temporary domain. Collaboration between companies, however, does not automatically require tenant consolidation. B2B collaboration, Teams external access, calendar relationships and a multitenant organisation can support continued collaboration without transferring all data. Record the decision before buying tools or scheduling cutover.
Introduction to Microsoft 365 tenant-to-tenant migration
This guide explains how to plan and carry out a Microsoft 365 tenant-to-tenant migration with controls to preserve the data within scope and document exceptions. It connects each phase: assessment, coexistence, applicable licensing, CTUDM where the native capabilities require it, Exchange, OneDrive/SharePoint, Teams, Intune and DNS. Clear explanations, practical examples and official references help make go-live predictable, support user adoption and manage risk throughout the project.
The need for a Microsoft 365 tenant-to-tenant migration, also known as an Office 365 tenant-to-tenant migration, typically arises during mergers and acquisitions, business divestitures, internal reorganisations, changes to the management model that require another tenant, or consolidation to simplify administration. The project extends beyond moving mailboxes and files: it must also support how teams work, collaborate and share information.
That is why, beyond the technical side, this guide focuses on the business perspective and the impact on people: what users will notice in their day-to-day work, how to reduce friction when adopting the new tenant and which decisions should be agreed with leadership before changing anything. The aim is for this guide to become a practical roadmap for IT, security and data governance teams planning a Microsoft 365 tenant change.
Throughout the article you will see concepts such as Cross-Tenant User Data Migration (CTUDM), Entra ID (formerly Azure AD), Exchange Online, OneDrive, SharePoint, Teams, Intune or Microsoft Purview. We explain when they come into play, why they matter and which best practices to follow in a modern Microsoft 365 / Office 365 tenant-to-tenant migration.
Last technical review: . This guide distinguishes native moves, copying with specialist tools and the recreation of configuration. It also covers Microsoft’s migration orchestrator and its documented limitations. Before a project is executed, confirm feature availability, service prerequisites and the licences held by the specific source and target tenants.
The objective of avoiding data loss is put into practice through a defined scope, an inventory, authorised preservation, testing and reconciliation of results. Not every Microsoft 365 component can be transferred in full by every method. Agree in advance which information will migrate, which will be archived or retained, which settings must be recreated and which exclusions the business accepts.
1. Project methodology and governance
In practice: the goal of the methodology is to make the Microsoft 365 tenant-to-tenant migration predictable, measurable and understandable for both IT and the business.
A solid methodology reduces friction, improves communication with business stakeholders and supports adoption. Working in waves allows you to learn with a pilot, scale with confidence and reserve a well-rehearsed final cutover. In a Microsoft 365 tenant-to-tenant migration, coordination issues often have more impact than purely technical errors.
MSAdvance delivers in waves: representative pilot → progressive waves → cutover and stabilisation. Each wave includes business validation (UAT), synchronisations where applicable, metrics and role-based communication.
A common approach is to combine agile practices with a milestone-based plan: kickoff workshops, architecture design, technical execution and adoption phase. For each phase, responsibilities, approvers and expectations are clearly defined, so that the migration is not perceived as a “pure IT project”.
| Activity | R | A | C | I |
|---|---|---|---|---|
| Architecture & plan | MSAdvance | IT | Security | Leadership |
| Identity, calendar and email coexistence | MSAdvance | IT | Business | Users |
| Exchange/OneDrive/SharePoint migration | MSAdvance | IT | Key areas | Leadership |
| Domain move | IT | IT | MSAdvance | Business |
| UAT & training | Business | IT | MSAdvance | Users |
Good project governance also includes a steering committee (weekly or fortnightly) with representatives from IT, business and security, where risks, dependencies and pending decisions are reviewed. This prevents key topics like legal hold, information classification or device management from being pushed “to the end”.
Choosing the migration sequence and decision points
Waves are useful when dependencies allow users and services to be separated. For a smaller organisation, or a domain that must be released in a single window, a coordinated cutover after the pilot may be more appropriate. Both approaches need entry and exit criteria covering target readiness, outstanding errors, supported synchronisation status, support availability and business approval.
In the RACI matrix, R identifies who performs the work, A who approves it and is accountable for the outcome, C who is consulted, and I who is kept informed. The matrix is illustrative: if MSAdvance carries out the domain move, that operational responsibility must be recorded explicitly, alongside the client’s approval and authorised access to the DNS provider.
Document the points of no return for each workload. Cancelling a batch before completion, moving a mailbox back through a reverse migration and restoring data from a backup are different procedures. The contingency plan identifies which option is available, how long it may take and how changes made by users will be preserved.
2. Assessment: inventory, dependencies and limits
In practice: the assessment answers “what is there”, “what can be moved” and “what blocks a smooth Office 365 tenant-to-tenant migration”.
The initial inventory determines how accurately the project can be planned. This is where you detect blockers (holds, special permissions) and size waves and timelines before any data is moved. A Microsoft 365 tenant-to-tenant migration without a rigorous assessment usually leads to last-minute surprises and conflicts between teams.
2.1 Identities and email
- Users, aliases, groups, shared mailboxes, permissions and delegations.
- Transport rules, connectors and accepted domains.
- Retention and Litigation Hold, active eDiscovery cases.
2.2 Collaboration and files
- OneDrive per user (volume, file types, external sharing).
- SharePoint: sites, owners, inheritance, integrations.
- Teams: teams, channels, apps, recordings, Stream (on SharePoint).
2.3 Devices and apps
- Intune: managed devices, profiles, compliance policies.
- Applications using Graph/EWS/SMTP OAuth.
- Power Platform: connectors, environments, critical flows.
It is also recommended to document regulatory requirements (financial sector, healthcare, public sector, etc.) and data location (datacentre regions) to confirm that the target tenant complies with the organisation’s data residency policies.
A good assessment outcome is a dependency map: which applications depend on email, which business processes use Power Automate flows, which areas share SharePoint sites and which users are particularly sensitive to change (leadership, customer service, 24/7 operations, etc.). This map will help prioritise waves and prepare a realistic communication plan.
2.4 Dependencies to include explicitly in the inventory
- Hybrid identity: the source of authority for each attribute, Microsoft Entra Connect or Cloud Sync, UPNs, dynamic groups, devices joined to Entra ID or the on-premises domain, and AD DS dependencies.
- Enterprise applications: SAML/OIDC single sign-on, SCIM provisioning, application registrations, service principals, delegated and application permissions, administrative consent, certificates, secrets and owners.
- Exchange: online archives, shared and resource mailboxes, user delegation dependencies, X500 addresses, applications that send email, rules, connectors, SMTP and client configuration.
- Protected information: active holds, eDiscovery cases, sensitivity labels, encryption, Customer Key and the people authorised to decide how these protections are handled.
- Power BI: workspaces, reports, semantic models, data sources, gateways, row-level security (RLS), credentials, scheduled refresh and assigned capacities.
- User experience: Outlook profiles, additional mailboxes, mobile devices, OneDrive synchronisation, shortcuts, bookmarks and processes that use existing URLs.
The inventory should distinguish supported configurations from retired components and items that require modernisation. For example, the legacy SharePoint Add-in model was retired in SharePoint Online on 2 April 2026. Affected solutions need to be assessed for alternatives such as SharePoint Framework and Entra ID authentication. This retirement does not mean that all SharePoint applications or APIs have been retired.
Produce a migration-readiness register for each workload: object, volume, owner, proposed method, licence, target, dependency, exclusion and acceptance evidence. Removing a legal hold is not a routine inventory task. Any change requires an authorised preservation procedure and validation by the relevant compliance owners.
3. Coexistence: identity, Free/Busy and email
In practice: well-designed coexistence allows the business to keep working while IT moves data between Microsoft 365 tenants.
Coexistence ensures the organisation can continue operating during the migration. With identity, calendars and email aligned, interruptions are reduced to a minimum. For end users, the ideal is that the tenant change feels like an adjustment rather than a full relocation.
3.1 Identity (Entra ID)
Configure the Cross-tenant access policies required for B2B collaboration. Where user provisioning and updates need to be automated, use Cross-tenant synchronization with mapped attributes. The default configuration provisions external B2B members, and other supported mappings are also available. These collaboration representations must be distinguished from the internal target identities prepared to receive migrated data.
A best practice is to define in advance how User Principal Names (UPN) and email aliases will look in the target tenant. This avoids unnecessary address changes for users and simplifies external communication with customers and suppliers.
3.2 Calendars (Free/Busy)
It is recommended to configure Organization Relationships in Exchange so that both tenants can see availability during coexistence.
# Run in the tenant that needs to publish its availability.
# First complete the federation configuration and endpoints required
# for the scenario, and verify the remote domains.
Connect-ExchangeOnline -UserPrincipalName "admin@source.onmicrosoft.com"
$relationship = Get-OrganizationRelationship -Identity "Rel-Target-Tenant" -ErrorAction Stop
$relationship | Format-List Name,DomainNames,TargetApplicationUri,TargetAutodiscoverEpr
Set-OrganizationRelationship -Identity $relationship.Identity `
-FreeBusyAccessEnabled $true -FreeBusyAccessLevel LimitedDetails
# Prepare and test the reverse relationship from the other tenant.
# Use test accounts to verify the agreed visibility in both directions.For the business, the key is being able to schedule meetings normally during the migration. Before each wave, it is worth testing that calendars between source and target tenants correctly display availability (Free/Busy), especially in critical areas like sales, support or leadership.
3.3 Email and routing
It is usually a good idea to keep MX pointing to the source tenant until cutover. If temporary rerouting is needed, you can use well-controlled connectors and rules and rehearse end-to-end mail delivery.
In complex scenarios (for example, multiple domains or subsidiaries), it is useful to document clearly which domains move, in which order and how email will behave in each phase. A simple routing flow diagram saves a lot of questions for first-line support.
3.4 What each coexistence mechanism provides
B2B synchronisation leaves authentication in the source tenant. It does not transfer passwords, MFA methods or control of an internal identity to the target tenant. Microsoft requires an Entra ID P1 licence in the source tenant for each user synchronised through cross-tenant synchronisation; synchronising groups as well has additional Governance or Entra Suite requirements. Review the licensing for each feature actually used.
Free/busy sharing provides calendar availability at the authorised level of detail. A complete address list needs a separate design for contacts or recipient representations and directory visibility; a calendar relationship does not create it. For Teams, review external access, guests, shared channels and the policies of both organisations against the required collaboration experience.
The PowerShell example updates a relationship that has already been prepared. It does not configure the entire free/busy scenario on its own. Organisation relationships used to authorise mailbox moves also require migration-specific properties. Keep these purposes distinct, review existing values and test coexistence before moving users.
If the source and target organisations must continue collaborating after separation, agree who maintains their directory representations, how joiners and leavers are handled and which B2B access must remain. Temporary coexistence and ongoing collaboration may have different owners, attributes and policies.
4. CTUDM, shared-data licensing and legal considerations
In practice: licensing depends on the method chosen for each workload. CTUDM enables supported native user-data migration capabilities and must be planned in advance. SharePoint and third-party tools follow separate licensing arrangements.
The native user-data migration capabilities require the Cross-Tenant User Data Migration (CTUDM) add-on, charged per user and migration. The orchestrator documentation includes Exchange Online, OneDrive, Teams chats and Teams meetings within its supported scope. The add-on can be assigned to the source or target user in accordance with the documented procedure; normal service licences are still required. Confirm procurement and assignment before running the move, alongside GDPR, audit and retention requirements.
From a legal perspective, migrating personal data between tenants usually implies reviewing data processing agreements, partner contracts and compliance documentation. It is important that the legal department understands what information moves, in what timeframe and with what security guarantees, especially in organisations subject to external audits.
Specialist third-party tools can be the primary approach when they better meet the scope, wave plan, existing-target requirements, or copying and reporting needs. Using them does not, by itself, require CTUDM: check the licences and APIs used by the specific product. PST exports and IMAP migrations remain useful in limited scenarios, but their restrictions on calendars, contacts, permissions, metadata and user experience must be assessed.
Costs and effort in a Microsoft 365 tenant-to-tenant migration
The cost of a Microsoft 365 tenant-to-tenant migration includes the licences for the chosen method and extends beyond a single add-on. Other factors include:
- Number of users and mailboxes to migrate.
- Data volume in Exchange Online, OneDrive and SharePoint.
- Complexity of Power Platform, integrations and third-party applications.
- Number of Intune-managed devices and legacy systems.
- Regulatory, audit and data retention requirements.
- Need for extended support, training and change management.
This is why many organisations choose a mixed approach: part of the effort is handled by the internal IT team and part is delegated to a specialised partner who has already delivered other Microsoft 365 cross-tenant migration projects.
Shared-data licensing and purchasing availability
Native migration of SharePoint sites is documented separately as Cross-Tenant Shared Data Migration. At the review date, Microsoft offers it to Enterprise Agreement customers, with licences per 100 GB of data moved and specific calculation rules. It should not be costed as though it were automatically included in every user’s CTUDM licence.
The current user-data orchestrator documentation covers EA, CSP, web direct, small-business and education customers. Confirm the purchasing channel, services and actual availability for the tenants involved. Availability of one capability should not be assumed to extend to another capability or a different sovereign cloud.
Preservation, holds and contractual requirements
A native move may remove content from the source once it completes. If the business needs evidence to remain there, design an authorised copy or archive arrangement before migration. Mailboxes on hold and certain OneDrive accounts with hold policies block native moves. Legal and compliance teams determine how obligations and evidence will be preserved; a hold must not be removed merely to get past a technical error.
Also review the data processing agreement, temporary administrative permissions, data location, any transfers performed by the chosen tool and the retention period for project records. Commercial terms should distinguish professional services, migration licences, user licences and any costs of temporary coexistence.
5. Migrating Exchange Online between Microsoft 365 tenants
In practice: in Exchange Online the objective is to keep email flowing and ensure users barely notice they have changed tenants.
A planned email migration reduces incidents and support requests. Well-defined batches and pre-cutover synchronisation help ensure that supported content is synchronised and exceptions are identified before the change. In an Exchange Online tenant-to-tenant migration, batch design can make the difference between a controlled cutover and prolonged disruption.
- Trust and consent: meet the prerequisites in the official guide.
- Target identity: prepare a target MailUser with the attributes required by Microsoft, including ExchangeGUID, ArchiveGUID where applicable and X500 addresses. A B2B collaboration account is not a substitute for this preparation.
- Migration batches: use
New-MigrationBatchwith CSV and enable synchronisation until cutover. - Post-cutover: validate rules, delegations, shared mailboxes and SMTP flows.
It is advisable to place critical users (leadership, 24/7 operations, customer-facing teams) in separate batches so you can provide closer support. It also helps to label each batch with a clear identifier (by department, country or business unit) to read reports and correlate incidents more easily.
# Run from the TARGET tenant, with the endpoint already authorised
# and the target MailUser objects prepared. The CSV uses target addresses.
Connect-ExchangeOnline -UserPrincipalName "admin@target.onmicrosoft.com"
$endpoint = "Source-Tenant-Endpoint"
$deliveryDomain = "target.onmicrosoft.com"
$csv = [System.IO.File]::ReadAllBytes("C:\ctm\target-users.csv")
Get-MigrationEndpoint -Identity $endpoint -ErrorAction Stop
New-MigrationBatch -Name "CTM-Wave-01" -SourceEndpoint $endpoint `
-CSVData $csv -TargetDeliveryDomain $deliveryDomain -AutoStart
Get-MigrationUser -BatchId "CTM-Wave-01" |
Get-MigrationUserStatistics -IncludeReport
# Complete only after checking synchronisation, exceptions and approval.EmailAddressalex.lee@target.onmicrosoft.com · jamie.morgan@target.onmicrosoft.comAllow an observation period to investigate delivery failures and confirm with business owners that distribution lists, resource mailboxes and shared mailboxes work as designed. In a native move, completion deletes the source mailbox and converts the recipient to a MailUser for routing. This observation period therefore does not mean that the original mailbox remains available for inspection. When a copying tool is used, source retention must be agreed and verified separately.
Two companies merge, and leadership wants everyone to use the same email domain from Monday. Without prepared batches and testing, missing delegations, rules that have not been recreated and incomplete distribution lists can disrupt users. A wave plan and prior UAT help limit the impact to the expected sign-in and client changes. The email and calendar content within scope is validated, and meeting links receive their own checks.
How to migrate Exchange Online between tenants (in practice)
Using Microsoft native tools (CTUDM)
- Prepare the relationship between tenants: prepare the migration application and permissions, consent in both tenants, the security group that defines the eligible mailboxes, and organisation relationships with the required mailbox-move properties. Configure B2B policies where coexistence needs them; they do not replace these migration prerequisites.
- Define endpoint and batches: from Exchange Online PowerShell, create the migration endpoint and batches using
New-MigrationEndpointandNew-MigrationBatch(as in the example above). - Sync before cutover: keep batches in incremental sync until the agreed change window.
- Cutover and validation: during cutover, complete the batches, review bounces, delegations, shared mailboxes and transport rules.
Using third-party tools (Quest, BitTitan, etc.)
Third-party solutions can be the primary migration method or be combined with native capabilities for different workloads. Do not assume that the same workload needs both engines or both sets of migration licences:
- Quest On Demand Migration (Exchange): connects both tenants, discovers mailboxes, maps identities, creates waves and provides dashboards with status per mailbox, errors and retries.
- BitTitan MigrationWiz (Mailbox Project): supports mailbox projects, source and target endpoint configuration, CSV user imports and a pre-stage using supported filters and content types, followed by a final update pass. The percentage completed beforehand depends on data volume, subsequent changes and the state of each mailbox.
- Other vendors: there are similar tools focused on specific scenarios (archive mailboxes, extended coexistence, audit-heavy requirements, etc.).
Official Microsoft documentation: Cross-tenant mailbox migration (Exchange Online).
Prerequisites that prevent migration failures and delivery errors
Coordinate Exchange Online licence assignment with preparation of the ExchangeGUID. Accidentally provisioning an empty target mailbox can prevent the native move. Also validate archives, quotas and the LegacyExchangeDN copied as an X500 address, so replies to older messages and autocomplete entries can resolve correctly. Assign SMTP addresses only when their domain belongs to the relevant tenant.
A mailbox on any type of hold blocks the native move. Supported user-visible content includes email, contacts, calendars, tasks and notes; moving it does not transfer every tenant setting or retain a source mailbox for eDiscovery. Transport rules, connectors, groups, signatures and permissions that the selected method does not migrate must be included in the inventory and explicitly recreated.
Move mailbox owners and delegates together where their dependencies require it, because cross-tenant mailbox permissions do not behave like internal delegation. Validate shared and resource mailboxes, Outlook, mobile devices, archives and email sent by applications. Clients may need a new profile or reauthentication and may download OST/OAB data again; include this work in the support and network-capacity plan.
The example CSV is for a native move, and its addresses identify the target MailUser objects. For the orchestrator, follow its Identity Mapping and batch-creation steps; for a third-party product, use that vendor’s template and mappings. Exchange synchronisation does not mean that OneDrive or Teams migration has completed at the same time.
6. Migrating OneDrive between Microsoft 365 tenants
In practice: OneDrive migration must preserve usable access, versions and shared links, as well as transfer the files users rely on.
OneDrive typically contains day-to-day working files, personal drafts and documents that have not yet found their permanent home in SharePoint. Defining how to handle versions and sharing helps avoid unexpected problems “the day after” the migration.
Cross-tenant OneDrive migration moves user content to the target tenant. It is advisable to plan how to handle external links and to explain to users what will happen with existing links, especially those shared with customers and suppliers.
- Set up trust and permissions between tenants.
- Pre-create users/groups in the target tenant and map identities.
- Run per-user moves and validate access, versions and sharing.
From the user’s perspective, it is important to clarify that files do not “disappear” but move to another tenant. A short visual guide with screenshots showing how to find their new OneDrive, how to check the “Shared” section and how to re-share key documents usually prevents a lot of support tickets.
- Links shared with customers that stop working from one day to the next.
- Users who cannot find their “personal” folders in the new tenant.
- Important versions lost because the migration was oversimplified.
The mitigation is clear communication, prioritising users with critical dependencies and providing fast support throughout the first week after go-live.
How to migrate OneDrive between tenants (in practice)
Using Microsoft native tools (CTUDM)
- Prepare cross-tenant permissions: establish the specific SharePoint Online trust between the source and target instances using the documented cmdlets, and verify the results. B2B collaboration is a separate mechanism.
- Validate target OneDrive: confirm that users and groups exist and have appropriate licences, but prevent their target OneDrive sites from being provisioned before or during the native move. An existing site cannot be overwritten or merged by this procedure, so resolve that scenario before proceeding.
- Configure mappings: define the source and target for each user, normally through CSV files or scripts, and start the move using SharePoint Online PowerShell. Alternatively, use the orchestrator when that is the chosen procedure and its identity requirements have been met.
- Verify content and sharing: check versions, business-critical folders and internal sharing links. For external links, validate redirects, identities and permissions, and agree which files need to be shared again if the chosen method does not preserve access.
Using third-party tools (Quest, BitTitan, etc.)
In organisations with a lot of OneDrive content, specialised document migration tools are common:
- Quest On Demand Migration (OneDrive): discovers source OneDrives, maps target users and moves content while preserving permissions and sharing where the API allows it.
- BitTitan MigrationWiz (Document Project): creates projects by batches, defines endpoints, imports users and runs phased migrations, with per-user and per-file reports.
Native moves, redirects and limits
A native OneDrive move is a single-pass operation. It transfers the content to the target and leaves a redirect at the source location. Incremental and delta passes are not supported. Plan for a period in which content may be read-only, and tell users when they must stop making changes.
Existing links can continue to work through the redirect if the recipient retains access to the target and identities and permissions are mapped correctly. Redirects remain until they are explicitly removed or the source tenant is deprovisioned. Before closing that tenant, review links used by customers, suppliers, documents, applications and shortcuts.
The native documentation specifies limits of 5 TB and one million items per OneDrive; the item count can include versions and other list items. Also validate the 400-character path limit, hold and Customer Key restrictions, and the source read/write state. Check each user’s actual data and the current service conditions before scheduling the operation.
Copying tools have their own rules for target provisioning, version preservation, sharing and subsequent passes. Those rules must not be applied to a native move. After cutover, validate the sync client, known folders where applicable, shortcuts and the Shared view. Use representative checks alongside reconciliation of the complete migration reports.
8. Migrating Microsoft Teams between Microsoft 365 tenants
In practice: in Teams, the important thing is to preserve key workspaces (teams and channels) and manage expectations about which conversations will be retained.
Teams brings together files, chats, meetings and apps. Moving files, recreating the required workspaces and providing role-specific training help maintain continuity. Decisions about which elements are transferred and which are rebuilt directly affect the consistency and usability of the new environment.
- Identify teams by process (sales, finance, projects) and criticality.
- Recreate governance (naming, expiration, guests) in the target tenant.
- Plan for recordings (Stream on SharePoint) and integrated tabs/apps.
Explain that the scope differs between chats, meetings and channel conversations. The native orchestrator supports chats and meetings in documented scenarios; teams, channels, sites and certain content or meeting types need another procedure. Where required, retain source information for an agreed period or export specific evidence to meet legal or audit requirements.
How to migrate Microsoft Teams between tenants (in practice)
Using Microsoft native tools
Microsoft provides a user-data migration orchestrator that covers Teams chats and meetings, alongside Exchange Online and OneDrive. It does not transfer every Teams component: teams, channels, sites and applications need complementary procedures. The strategy distinguishes:
- Files and tabs: migrate the files associated with Teams using SharePoint/OneDrive migration (documents are stored in SharePoint sites).
- Teams and channels: recreate teams and channels in the target tenant, manually or via PowerShell/Graph.
- Historical messages: Microsoft Graph APIs can import supported content into channels and chats, subject to migration permissions, mappings and specific restrictions. Message import is an application-level operation, rather than a guarantee that every Teams object will be migrated in full.
Connect-MicrosoftTeams
# Choose a unique alias and first check whether the team already exists.
$newTeam = New-Team -DisplayName "Sales EU" -MailNickname "sales-eu"
# New-Team creates the initial channel. Create an additional channel.
$channelName = "Planning"
if (-not (Get-TeamChannel -GroupId $newTeam.GroupId |
Where-Object DisplayName -eq $channelName)) {
New-TeamChannel -GroupId $newTeam.GroupId -DisplayName $channelName
}Using third-party tools (Quest, BitTitan, etc.)
To simplify the work, many organisations use specialised Teams migration solutions:
- Quest On Demand Migration (Teams): discovers teams, channels and members, maps them to target groups and migrates files, tabs and parts of the history according to API capabilities.
- BitTitan MigrationWiz (Teams): creates Teams projects, maps source/target teams, migrates files, tabs, members and, in some cases, channel conversations.
Official Microsoft documentation (Teams migration APIs): Import third-party platform messages to Teams.
Chats and meetings with Microsoft’s migration orchestrator
The procedure requires users to be prepared and Identity Mapping to be completed, together with the necessary application setup and consent and the required Teams licences in both tenants. Meeting migration also requires mailboxes and chats to be selected and the mailbox move to complete successfully. Identity preparation remains necessary even when only some workloads are selected.
If Exchange is included, the mailbox can synchronise before the scheduled completion date. OneDrive, chats and meetings are processed in the orchestrator’s documented order after mailbox cutover. Do not communicate that all workloads will be ready at the same instant. Business stakeholders should understand the expected experience and which client and identity users must use at each stage.
Identify chats that are excluded or require special handling: self-chats, certain conversations created by external users or users whose account or licence no longer exists, reactions, app messages and other unsupported elements. New or duplicate threads may appear during the transition. Content may remain in the source, but new messages sent there after a thread is migrated are not automatically added to the target.
Supported meetings have their URLs and participants updated according to the mappings, with restrictions for recurrences, calendars, organisers and event types. Recordings, transcripts and recaps are not transferred as part of meeting migration; include them in the inventory and handle them through the relevant file workloads or preservation procedures. Also review special events, channel meetings, rooms and applications.
Agreed scope and validation with users
The project matrix lists teams; standard, private and shared channels; membership; files; tabs; messages; one-to-one and group chats; meetings; and applications. Third-party tools may cover different elements through separate modules and licences. A history retained as an archive or evidence and a conversation that remains usable in the client are different outcomes, which must be agreed before migration.
The pilot should include real conversations, attachments, search, calendars and document access. Test updated invitations with internal and external users, and explain any action they need to take. If temporary source access is retained, define its end date and confirm which functions stop working once the mailbox is moved.
References: migration orchestrator · user experience and limitations.
9. Power Platform and other workloads (Power Apps/Automate/BI)
In practice: the goal in Power Platform is to ensure automated processes do not break due to credential, connector or environment changes.
Many automations depend on credentials and connectors with permissions that will change tenant. Before cutover, it is critical to review owners and dependencies. A Microsoft 365 tenant-to-tenant migration that ignores Power Platform can break key processes with no warning for users.
- Inventory of critical apps/flows and business owners.
- Re-authentication of connections and credential updates in the target tenant.
- End-to-end testing with sample data and user validation.
It is also a good idea to define an environment strategy (development, test, production) in the new tenant if one does not exist. This way, any new automation created after the migration will follow a more controlled lifecycle aligned with data governance policies.
How to migrate Power Platform between tenants (in practice)
Using Microsoft native tools (ALM and solutions)
- Convert apps and flows into solutions: package Power Apps, Power Automate flows and related components into managed or unmanaged solutions.
- Export from the source environment: download the solution (ZIP) from the Power Platform admin centre or use pipelines/DevOps.
- Import into the target environment: upload the solution into the new tenant environment, resolve dependencies (connectors, roles, Dataverse tables, etc.) and apply updates.
- Update connections and credentials: reconfigure connectors (SharePoint, Exchange, SQL, etc.) with accounts and permissions from the new tenant.
Using third-party tools or advanced automation
In scenarios with many environments and solutions, you can complement this with:
- Power Platform pipelines / Azure DevOps / GitHub: to automate lifecycle management in supported scenarios. Assess Power Platform pipelines against their environment and tenant boundaries. For cross-tenant deployments, prepare a supported mechanism with each target’s own connections, permissions and authentication, for example using Azure DevOps or GitHub with Power Platform CLI.
- Scripts with PowerShell and Power Platform CLI: to standardise recurring tasks such as exporting solutions, applying environment variables or enabling/disabling flows.
Official Microsoft documentation: Migrate Power Platform environments between tenants · Microsoft Learn: Power Platform.
9.1 Moving Dataverse environments and deploying solutions
Alongside solution export and import, Microsoft supports cross-tenant migration of production and sandbox environments with Dataverse that meet its prerequisites. The procedure moves the Dataverse organisation and requires preparation and validation of users, apps and components. It must not be treated as an automatic transfer of every Power Platform resource. Default, developer, trial and Teams environments are outside the documented move scope.
First test a copy of production in a sandbox. Review the specific steps for Power Apps, Power Automate, Power Pages and Copilot Studio agents where present, together with integration and component restrictions. After the move, validate URLs, owners, connections, roles, tables, flows and dependencies. Different applications in the same project may need different approaches.
An exported solution contains supported components and definitions, but it does not replace a plan for business data, connections and credentials. Document the package contents, prepare connection references and environment variables, and decide how Dataverse data or external-source data will move. Do not delete a solution containing tables without assessing the impact on its data and preserving the necessary evidence.
9.2 Migrating Power BI workspaces, reports and semantic models
Power BI needs its own plan within the project. Inventory shared and personal workspaces, reports, semantic models, published apps, dashboards, dataflows, subscriptions and any Fabric content. For each item, determine whether it can be downloaded and republished, deployed through a supported API or needs to be rebuilt. Power Platform solution ZIP files do not transfer these Power BI objects.
- Artefacts and dependencies: locate source files, distinguish reports from their semantic models, and document shared models, live connections, DirectQuery, composite models and dependencies between workspaces.
- Export and publication: review PBIX download restrictions, size limits, incremental refresh and service configuration. The ability to download a report does not guarantee that all its data and dependencies can be transferred by the same method.
- Data sources and gateways: prepare the necessary gateways or clusters, and reconfigure data sources, credentials, cloud connections and permissions for the accounts that will run refreshes.
- Security: recreate workspace roles, app audiences and RLS assignments. Target users and groups have different identifiers and must be mapped and tested with actual user accounts.
- Operations: review scheduled refresh, parameters, alerts, subscriptions, published links and integrations with Teams, SharePoint and external applications.
- Licensing and capacity: confirm the requirements for Power BI Pro, Premium Per User or Fabric/Premium capacity based on content creation, publication and consumption. Microsoft 365 Business Premium does not include Power BI Pro. Free access to content depends on the capacity and the conditions of the specific scenario.
Compare pilot results with the source: a complete refresh, key business metrics, the reader experience and role-based data restrictions. If the scope covers only supported reports and models in shared workspaces, explicitly define how dashboards, dataflows, personal content, Fabric items and other excluded objects will be handled.
Official references: report downloads and restrictions · Power BI licensing.
10. Migrating devices and Intune between Microsoft 365 tenants
In practice: with Intune, the key is that devices continue to comply with policies and users can work without unexpected blocks.
Define the procedure for each platform: leaving the previous management environment, joining or registering with the target tenant, and re-enrolling in Intune. This may involve reprovisioning where appropriate or a supported transition process. The aim is to maintain access and security policies through a planned, tested user experience, particularly for field teams and remote workers.
- Export configuration and recreate equivalent policies in the target tenant.
- Evaluate Windows Autopilot (import hardware hashes, profiles in the new tenant).
- Plan the user experience (un-enrolment and join to the new tenant).
It is recommended to distinguish between corporate devices and BYOD (user-owned devices). For BYOD devices, clear communication is essential: what will be done, how their personal data will be affected and which steps they must follow to re-register the device if necessary.
How to transition devices and Intune management between tenants
Using Microsoft native tools
There is no fully automated “Intune tenant-to-tenant migration”. In practice, the strategy is to recreate configuration in the new tenant and re-enrol devices:
- Export configuration: document or export compliance policies, profiles, apps and settings from the source tenant so you can recreate them in the target tenant.
- Prepare the new tenant: create equivalent groups, policies and profiles, configure Intune, Defender and, if applicable, co-management with Configuration Manager.
- Use Windows Autopilot where possible: first remove the previous Autopilot registration where required, then register the devices and assign profiles in the target tenant, and plan supported reprovisioning. Windows Autopilot Reset preserves the existing Entra ID join and MDM enrolment, so it does not change the device’s tenant on its own.
Install-Script -Name Get-WindowsAutopilotInfo -Force Get-WindowsAutopilotInfo -OutputFile .\AutopilotDevices.csv- Re-enrol existing devices: for devices that will not be fully reprovisioned, coordinate and test a supported process for leaving, joining and re-enrolling on each operating system. On Windows, verify local administrator access, the user’s profile and data, recovery keys and access to the new environment. Company Portal and Access work or school are parts of the process where appropriate; they do not automatically transfer the existing user profile.
Using third-party tools
Some identity- or device-specific solutions and modules can automate parts of discovery, transition, profile handling or reporting. Verify these functions against the exact product, operating system and join type. They must not be attributed generically to a vendor’s Microsoft 365 data migration module. Confirm that enrolment and final management actually belong to the agreed tenant.
Official Microsoft documentation: What is Microsoft Intune · Windows Autopilot.
Differences by operating system and management model
On Windows, distinguish Entra-joined devices, devices joined to on-premises Active Directory, hybrid-joined devices and devices registered for BYOD. Verify which identity can sign in after the change, how local data will be preserved or transferred, and the effects on Windows Hello, certificates, apps, BitLocker and compliance. Define how the device will be recovered if enrolment fails.
On iOS, iPadOS and macOS, review Apple Business Manager or Apple School Manager where used, MDM server assignment, automated device enrolment, APNs certificates, apps and tokens. On Android, review Android Enterprise, work profiles or corporate-owned devices, enterprise accounts and provisioning methods. The impact on apps and data depends on the enrolment mode; a wipe is not a universal requirement for every device.
Prepare Intune configuration in the target first and test it with representative devices. Coordinate the enforcement of compliance-based access so a device in transition is not blocked before its new management is ready. Validate applications, certificates and profiles for the relevant roles and users.
If the organisation retains an external MDM service managed by another provider, agree with that administrator which profiles, accounts, apps and policies need updating. A Microsoft 365 migration does not, by itself, require device management to move to Intune. The scope must identify who retains management responsibility and what access to the new tenant is authorised.
Specific reference: what Windows Autopilot Reset preserves.
11. Domain move: verification, TTL and DNS
In practice: the domain move is one of the most visible stages of a tenant-to-tenant migration. Proper preparation reduces the impact on email and authentication; an unprepared change can increase disruption significantly.
The domain move is the visible cutover. Rehearsing the procedure, lowering TTL early and preparing DNS records help manage routing and potential delivery queues. These preparations have a substantial effect on the user’s experience and the overall success of the project.
11.1 Preparation
- Reduce TTL for MX records 48–72 hours before cutover.
- Remove the domain from UPN, proxyAddresses, groups, shared mailboxes and applications in the source tenant.
- Prepare the target domain setup and verification records, and test services using temporary domains owned by the target tenant. Complete verification of the custom domain only after it has been released from the source.
11.2 Cutover and enablement
- Remove the domain from the source tenant (with no active references).
- Add and verify the domain in the target, assign UPNs and SMTP addresses according to the plan, and validate or update MX/SPF/DKIM/DMARC records using the service’s actual values.
- Validate delivery and SPF/DKIM/DMARC alignment. If DMARC is being introduced for the first time, agree a gradual rollout. Preserve an existing enforcement policy unless a justified change has been authorised.
# Structure examples: retrieve the actual values from the target tenant.
MX @ 0 → <MX-value-specified-for-the-domain>
# SPF: this example assumes Microsoft 365 is the only authorised sender.
# Include other legitimate senders in the single existing SPF record.
TXT @ "v=spf1 include:spf.protection.outlook.com -all"
# Publish BOTH selectors using their actual values; do not infer them.
CNAME selector1._domainkey → <Selector1CNAME-from-the-target-tenant>
CNAME selector2._domainkey → <Selector2CNAME-from-the-target-tenant>
# DMARC example: retain or agree the policy and use a valid reporting mailbox.
TXT _dmarc "v=DMARC1; p=quarantine; rua=mailto:dmarc@contoso.com"Measure the domain move using the observed time to release and verify the domain, stabilise email and authentication, and resolve delivery failures and incidents. Allow time for service dependencies and DNS caching instead of guaranteeing completion within a few minutes. The contingency plan defines which changes can be reversed and which require another migration or a specific recovery procedure.
Guides: Remove a domain · Add a domain · DNS records for Microsoft 365
- “Will important emails be lost?”
- “Will we be able to keep serving customers while the change happens?”
- “Will we have to notify all our contacts of a new email domain?”
The answer is to rehearse the change, lower TTL in advance, validate deliveries in the target tenant and have a specific communication plan for customer service, sales and support.
Domain release and verification sequence
A custom domain cannot be verified in two Microsoft 365 tenants simultaneously. Before cutover, prepare identities and tests using temporary domains. During the authorised window, remove references to the domain in the source, release it, and complete verification and assignment in the target. Correct references sourced from on-premises Active Directory at their source of authority so synchronisation does not recreate them.
Lowering TTL 48–72 hours in advance is an operational guideline: check the previous TTL and allow time for it to expire. This helps with DNS caches, but does not accelerate Microsoft’s internal domain release or eliminate delays at external providers. If the same domain is retained, the MX value may be unchanged; validate the value specified by Microsoft rather than changing it as a matter of routine.
Current DKIM values and legitimate senders
Microsoft introduced an updated DKIM target format for new domains in May 2025; existing domains may still use the earlier format. Retrieve both CNAME values from the portal or by running Get-DkimSigningConfig -Identity contoso.com | Format-List Selector1CNAME,Selector2CNAME after preparing the domain’s configuration. Publish both actual values, enable signing and verify the result. The DNS example illustrates the record structure and does not provide ready-to-use values for another tenant.
Review CRM systems, marketing tools, applications, printers and other senders, together with connectors and external gateways. SPF must continue to authorise legitimate senders, while DMARC must preserve the agreed alignment. Tests cover incoming and outgoing mail, replies to older messages, and delivery between migrated and non-migrated users.
The continuity plan addresses queues, retries and possible rejections according to the mail systems and routing design. Changing the MX record back does not, by itself, return domain ownership or mailboxes to the source tenant. Assign DNS responsibilities, confirm registrar access and define decision criteria and communication for customer-facing teams.
Reference for current values: configure DKIM in Microsoft 365.
Do you want to validate whether your current Microsoft 365 tenant-to-tenant migration plan covers all these points?
MSAdvance can run a short assessment of the current environment, review each workload’s method and licensing, CTUDM where applicable, coexistence and the domain move, and propose a wave plan aligned with business and security.
12. Security and compliance: MFA, Conditional Access, Purview
In practice: migration is a great opportunity to raise the security baseline of the target tenant and close inherited gaps.
Harden the target tenant from day one and maintain that protection throughout the transition. Temporary shortcuts can leave security gaps that remain after the migration is complete. A Microsoft 365 tenant-to-tenant migration provides an opportunity to improve the security baseline while preserving the controls required for day-to-day operations.
Core security controls
- MFA and Conditional Access with appropriate scope and licensing: P1 for supported general features, and P2 for policies based on user risk or sign-in risk.
- Defender for Office 365: Safe Links/Attachments and anti-phishing.
- Block legacy authentication and review POP/IMAP usage. These protocols can use OAuth; disabling the protocols entirely depends on authorised applications and business requirements.
Information governance (Microsoft Purview)
- Information Protection (labels and encryption).
- DLP in email and files based on PII/finance/regulatory data.
- eDiscovery and retention in the target tenant.
The technical work should be accompanied by training on security best practices: how to spot suspicious emails, what to do in case of a suspected phishing attack, how to share documents securely, etc. A few well-designed sessions greatly reduce human risk after the tenant change.
Identity, MFA and gradual enforcement of controls
Users’ authentication methods and MFA configuration do not transfer automatically to the new tenant. Prepare registration, initial access and account recovery in the target, with specific instructions for Authenticator and devices. Recreate Conditional Access policies using target groups, apps, locations and devices, and test them in report-only mode before enforcement.
Define emergency access accounts, justified and monitored exclusions, and least-privilege administrative access. B2B trust in MFA or compliance signals can support coexistence, but it does not transfer policies or authentication methods into the new environment. Every user who benefits from a feature needs the appropriate licence.
Retention, encryption and compliance evidence
Recreate the required Purview policies and test their effective application to email and files. Do not assume that source labels and their protections are valid in the target without checking configuration, rights and keys. Identify encrypted documents and data subject to preservation obligations, and establish how access and protection will be maintained throughout the transition.
Handling holds, protected information or labelling changes requires authorised decisions and evidence. Retain inventory records, exceptions and validation results. At the end of the project, remove consent grants, technical accounts and temporary secrets that are no longer needed, review partner access and confirm that the target’s protection mechanisms remain active.
13. Business Basic, Standard and Premium licences (and Enterprise)
In practice: migration is an opportunity to align Microsoft 365 licences with the organisation’s current requirements.
Where the selected native capabilities require CTUDM, the add-on sits alongside normal service licensing. Decide target licences before migration, balancing cost, security and productivity by user profile, and assign them in the technical sequence required by the chosen method. A tenant-to-tenant migration is also an opportunity to rationalise licences and align them with current business needs.
| Plan | Productivity and services | Security and administration | Selection criteria |
|---|---|---|---|
| Microsoft 365 Business Basic | Exchange Online, OneDrive and SharePoint, with web and mobile apps. Teams availability depends on the purchased variant. | Baseline protection and controls for included services; assess add-ons for advanced features. | Users who work in web apps and need email and collaboration services. |
| Microsoft 365 Business Standard | Business Basic services and Microsoft 365 desktop apps. | Desktop productivity does not, by itself, provide all of Premium’s identity and device-management capabilities. | Users who need applications installed on their computers. |
| Microsoft 365 Business Premium | Standard productivity features plus security and management capabilities for small and medium-sized businesses. | Entra ID P1, Intune Plan 1, Defender for Business and Defender for Office 365 Plan 1. | Organisations within the Business-plan limit that need protection for email, identities and devices. |
| Office 365 E1 | Collaboration services and web apps according to the SKU; without E3’s full desktop app suite. | Assess the identity, device-management and advanced-protection add-ons required. | Enterprise environments with users who work mainly in the browser. |
| Office 365 E3 | Desktop apps and Enterprise email and collaboration services, with service-specific compliance features. | Defender for Office 365 Plan 1 is included from 1 July 2026 according to Microsoft’s current description. Verify service assignment in the subscription. | Enterprise productivity with the email and compliance requirements addressed by E3. |
| Microsoft 365 E3 | Office 365 E3 plus Windows Enterprise, identity and device-management components. | Includes Entra ID P1 and Intune Plan 1; Defender for Office 365 Plan 1 is documented as included from 1 July 2026. | Businesses that need an Enterprise foundation for productivity, identities and devices. |
| Office 365 E5 | Office 365 Enterprise productivity with additional analytics and compliance capabilities, including Power BI Pro. | Includes Defender for Office 365 Plan 2; assess identity and device-management features separately. | Office 365 requirements with enhanced email protection, analytics and compliance. |
| Microsoft 365 E5 | Office 365 E5 plus Windows, identity, device and Enterprise security components. | Entra ID P2 and advanced Defender and Purview capabilities according to the plan’s services. | Organisations that need advanced controls and have the operational capacity to manage them. |
The whole organisation does not need to use the same plan. Mixing licences according to actual needs can optimise costs, provided every user benefiting from Conditional Access, Defender, Intune, Purview or another feature has the required rights. A feature being technically available at tenant level does not authorise its use for unlicensed users.
We recommend reviewing the official plan comparison tables regularly for details and changes.
Business-plan limits, Teams variants and Power BI
Microsoft’s plan documentation specifies a limit of 300 provisioned licences across the base per-user plans in the Business family within a tenant. Check the total and applicable terms before combining Basic, Standard and Premium. Larger organisations should assess Enterprise plans while continuing to select licences by user needs and usage rights.
Commercial variants exist with and without Teams. Its inclusion cannot be inferred from the Basic, Standard, Premium or E3 name alone: check the SKU, region, channel and assigned services. Additional telephony, event, security or compliance requirements may need further add-ons.
Power BI Pro is not included in Business Premium and must not be assumed to be included in E3. Calculate licensing and capacity requirements for content creation, publication and consumption, including any conditions for free access to content in supported capacities. Similarly, the included Power Apps and Power Automate rights do not automatically cover every premium connector, Dataverse scenario or automation in the project.
For email security, distinguish Defender for Office 365 Plan 1 and Plan 2. For devices, distinguish Defender for Business and the Defender for Endpoint variants. These products carry different rights. Check the final configuration against official service descriptions and enabled service plans, particularly when plan contents change or subscriptions renew.
References: Defender for Office 365 and the E3 update · Conditional Access licensing.
14. Performance, concurrency and scalability
In practice: performance determines whether the migration progresses at the expected pace without overloading either the platform or the support team.
Respect service limits, plan suitable off-peak windows and monitor batch health to reduce bottlenecks and cutover surprises. Performance depends on the migration engine, the number and types of items, service limits and load, and concurrency. Local bandwidth and latency are particularly relevant where intermediary agents are used or clients download data again; their effect is different for a native move within Microsoft 365.
- Mailbox concurrency: set batch sizes and wave proportions, then refine them after the pilot. A figure such as 10–20% of the workforce per window is only an initial planning example.
- Throttling and windows: align execution with service limits and work in off-peak hours to reduce impact.
- Retries and errors: review
Get-MigrationUserStatisticsand plan granular re-runs.
It is useful to agree early what an acceptable migration time is and which scenarios would justify moving users to another window. This helps to make quick decisions if any performance degradation is detected during the process.
Planning by workload and support capacity
Microsoft’s orchestrator currently limits each batch to 100 users, while allowing multiple batches to be submitted. The documentation also specifies a shared maximum of 4,000 queued or in-progress OneDrive and SharePoint moves. Check current limits for the exact service before scheduling larger volumes.
Initial Exchange synchronisation, mailbox cutover and the start of OneDrive, chat and meeting migration can occur at different times. Include that sequence in the schedule, with time for validation, data-consistency issues and user support. Microsoft does not provide a completion-time SLA for these migrations.
Measure pilot performance using representative data and plan with forecast ranges. Distinguish transfer time from validation, subsequent Outlook and OneDrive downloads, and actions users must perform. Increasing concurrency without checking throttling, dependencies and support capacity can make the outcome worse.
15. Migration methods and tools (native vs third-party)
In practice: there is no single perfect tool; you choose a combination based on scope, risk and timelines.
Select tools according to scope and risk as well as cost. Compare native capabilities, third-party products and automation for each workload without assuming one method is preferable for every project. Organisations differ in their requirements for flexibility, vendor support and the time available to develop and maintain automation.
| Method | Advantages | Limitations | When to use |
|---|---|---|---|
| Native user-data capabilities and orchestrator, with CTUDM | Integrated, Microsoft-supported | Workload-specific scope; requires the add-on and compatible identity and target preparation | When the native scope, target requirements and move model fit the project |
| SharePoint cross-tenant | Site moves through a dedicated procedure | Shared-data licensing, EA availability and specific prerequisites | When it fits within the feature constraints |
| Third-party tools | Flexibility, reporting, advanced mappings | Additional cost/licensing | Complex environments or special requirements |
| Custom scripts/Graph | Bespoke automation | Requires expertise and maintenance | Specific flows or integrations |
A project may use one main engine or combine methods across workloads when there is an operational reason. For example, it may require copying with pre-staging and deltas into an existing target, or a native move of supported content with automation for configuration. Avoid using two engines on the same object without an explicit design and support arrangement.
Questions for selecting the method and specific product
- Do you need to copy while retaining the source, move content, or merge data into an existing target?
- Which workloads support pre-staging and deltas, and which only start moving when cutover begins?
- How are versions, metadata, permissions, links and protected data handled?
- Which chats, meetings, teams and channels are covered, and what will users experience afterwards?
- Which licences does the engine require, and which modules are included in the proposal?
- How will evidence be retained, results reconciled, and recovery or reverse migration carried out?
For Quest On Demand Migration, identify the specific module or workload and its limits; verify identity and device functions separately. For BitTitan MigrationWiz, distinguish mailbox, document and Teams project types and licensing. ShareGate is another specialist option for SharePoint and Teams projects, with scope that must also be checked for each content type. A product brand alone does not establish which elements will be migrated.
Base the final decision on representative testing and the vendor documentation for the version and APIs used. Assess reporting, retries and subsequent passes together with content fidelity, business continuity and the total project cost.
16. Operational checklists (pre, during, post)
In practice: checklists turn the migration into a repeatable process and make it easier for new team members to onboard without losing context.
Clear checklists reduce error margins and make the process repeatable across waves and regions. They also serve as a guide for new team members or partners joining the project.
16.1 Before migration
- Procure and verify service and migration-engine licences, including CTUDM and shared-data licensing where applicable.
- Cross-tenant access and synchronisation (if applicable) configured.
- Organisation relationships (Free/Busy) created.
- Prepare users, groups and licences in the correct sequence; validate MailUser objects and mappings, and prevent target OneDrive creation for native moves.
- Communication and support plan per wave.
- Verify that authorised backups or exports actually exist and have a recovery procedure; document contingency and reversal options for each workload.
- Formal business approval for cutover schedule.
16.2 During migration
- Monitor batches; handle errors and retries.
- Resolve conflicts (delegations, rules, aliases).
- Run incremental synchronisation until cutover only for workloads and engines that support it; respect the windows required for single-pass moves.
- Provide periodic updates to business on the progress of each wave.
16.3 After migration
- Validate MX/SPF/DKIM/DMARC values and update records as needed for the intended routing and authorised senders.
- Review permissions in SharePoint/OneDrive; recertify access.
- Close temporary exceptions, block legacy authentication and disable POP/IMAP only where this has been approved after dependency checks.
- Collect user feedback and update documentation and FAQs.
16.4 Essential project-closure checks
- Confirm the migrated content, errors and accepted exclusions for each workload, with reports and identified business owners.
- Test Outlook, application-generated email, mobile clients, file synchronisation, meetings, flows and Power BI refresh.
- Verify MFA registration, device compliance, Conditional Access and effective application of protection and retention policies.
- Review links that depend on redirects and services that still need source accounts or objects.
- Remove migration permissions, applications, secrets and temporary access once no longer needed, while retaining project records.
- Approve acceptance and the end of stabilisation support before removing licences or deprovisioning the previous environment.
Microsoft 365 does not provide a universal tenant snapshot that this checklist can assume exists. Each backup or preservation mechanism must have a verifiable scope, location, permissions and restore procedure. Once content has been moved out of the source, recovery must not be assumed to be available from that now-empty source.
17. KPIs, UAT and business acceptance
In practice: defining KPIs and UAT from the beginning helps the business see the migration as a controlled project, not as a risk.
What is not measured cannot be improved. Defining KPIs before the first wave and aligning with business stakeholders on what “success” means at each milestone helps position the migration as a controlled, results-oriented project, not just a set of technical tasks.
| Area | Test | Success criteria |
|---|---|---|
| Delivery after cutover | Agreed tests without delivery failures caused by the change; authentication and alignment verified | |
| Calendars | Free/Busy during coexistence | Availability visible |
| OneDrive | Access and links | No relevant broken links |
| SharePoint | Site permissions | Correct access |
| Security | MFA/CA per role | Coverage and exceptions approved against the design and licensing |
| Support | Post-go-live incident volume | Below agreed threshold |
User acceptance testing (UAT) should focus on real scenarios: how a customer request is handled, how an incident is managed, how an international project is coordinated, etc. The closer tests are to everyday work, the more valuable the validation will be.
The percentages and times above are examples for agreeing acceptance criteria. They are not an SLA or a blanket MSAdvance guarantee for every project. Define the migration window, support coverage, incident severity and what counts as resolution or recovery. Reports must identify incidents that depend on Microsoft or another provider.
Content reconciliation and acceptance of exceptions
Compare counts and volumes using the migration engine’s criteria and the expected differences for each workload. Investigate skipped, unsupported or failed items and document their treatment. User sampling validates the experience, while complete reports support assessment of the full data set within scope.
The acceptance record covers mailboxes and delegation, file access, critical links, meetings, Power Platform processes, Power BI refresh and RLS, and device compliance. Each exception has an owner, an impact assessment and a decision to correct it, preserve it through an alternative method or explicitly accept it. Update training and final instructions using the pilot findings.
18. Common risks and mitigations
In practice: anticipating risks lets you decide what you absolutely want to avoid and what you can accept with a contingency plan.
Anticipating risks gives you room to manoeuvre. Defining preventive measures and simple, rehearsed contingency plans helps your migration be perceived as a robust process, even when unexpected issues arise.
| Risk | Indicative likelihood | Impact | Mitigation |
|---|---|---|---|
| Late procurement of licences for the chosen method | Medium | High | Confirm purchase, availability and assignment before scheduling cutover |
| Improvised domain move | Medium | High | Rehearsal and low TTL 48–72h |
| Permissions and labels not recreated | High | High | Purview/DLP plan in target tenant |
| Broken external links | Medium | Medium | Communication + recertification |
| Throttling and window issues | Medium | Medium | Waves and off-peak timing |
| Insufficient user communication | High | Medium | Wave-based, multi-channel comms plan |
| Underestimating Power Platform | Medium | High | Inventory of critical flows and apps before migration |
The likelihood and impact ratings in the table are illustrative. Reassess them using the inventory, pilot and business criticality, and assign an owner and due date to each action. The risk register should also include:
- Incompatible target provisioning: a mailbox, OneDrive or site created before a native move. Mitigation: prepare identities and restrict provisioning using the correct procedure.
- Retention or encryption: content blocked for the migration engine or inaccessible in the target. Mitigation: inventory protections and agree an authorised preservation and access-rights plan.
- Hybrid identity: attributes that reappear or changes not made at their source of authority. Mitigation: coordinate Entra ID, Exchange and on-premises Active Directory.
- Devices and profiles: interrupted local access, compliance or applications. Mitigation: pilot each platform, prepare recovery access and define the re-enrolment procedure.
- Chats and meetings: duplicate threads, old URLs, excluded event types or unsupported content. Mitigation: a scope matrix, Identity Mapping and testing with internal and external users.
- Power BI and automation: stale data, incorrect RLS or connections using old credentials. Mitigation: process testing, identified owners and security validation.
- Premature source decommissioning: loss of access to redirects, evidence or out-of-scope content. Mitigation: formal approval of closure and preservation arrangements before deprovisioning.
19. Useful scripts and snippets (PowerShell/JSON) for tenant-to-tenant migrations
In practice: scripts don’t replace design, but they save many hours on repetitive tasks.
These examples help standardise recurring tasks and monitor progress during tenant-to-tenant migrations. They do not replace planning, but they do reduce the time required for repetitive actions.
Connect-ExchangeOnline -UserPrincipalName "admin@target.onmicrosoft.com"
$batch = "CTM-Wave-01"
Get-MigrationBatch -Identity $batch | Format-List Identity,Status,TotalCount
Get-MigrationUser -BatchId $batch |
Get-MigrationUserStatistics -IncludeReport |
Format-List Identity,Status,*Item*,*Error*,Report# Approved CSV with an EmailAddress header and target-tenant mailboxes.
$mailboxes = Import-Csv "C:\ctm\approved-mailbox-protocols.csv"
$mailboxes | ForEach-Object {
Get-CASMailbox -Identity $_.EmailAddress -ErrorAction Stop |
Select-Object Identity,ImapEnabled,PopEnabled
Set-CASMailbox -Identity $_.EmailAddress `
-ImapEnabled:$false -PopEnabled:$false -WhatIf
}
# Remove -WhatIf only after reviewing the scope and approving execution.{
"displayName": "MFA for modern apps - report-only pilot",
"state": "enabledForReportingButNotEnforced",
"conditions": {
"users": {
"includeUsers": ["All"],
"excludeUsers": [
"11111111-1111-1111-1111-111111111111",
"22222222-2222-2222-2222-222222222222"
]
},
"applications": { "includeApplications": ["All"] },
"clientAppTypes": ["browser", "mobileAppsAndDesktopClients"]
},
"grantControls": { "operator": "OR", "builtInControls": ["mfa"] }
}EmailAddress
alex.lee@target.onmicrosoft.com
jamie.morgan@target.onmicrosoft.comHow to use these examples
Tenant names, paths, batches, users and GUIDs are illustrative. Replace them with the values recorded for the project and verify the connection context before execution. Reports can contain personal information and must be stored in a restricted-access location. Check available properties against the module version and migration type in use.
The POP/IMAP example uses -WhatIf to simulate the change and is restricted to an approved CSV. Review clients and applications that use these protocols and OAuth before disabling them. Removing legacy authentication and disabling a protocol entirely are separate controls that require their own design decisions.
The MFA JSON includes application scope, report-only state and two sample GUIDs. Replace them with the actual object IDs of the authorised emergency access accounts. Before creating the policy, verify P1 licensing, administrative permissions and exclusions. Review the result in logs and Conditional Access evaluation tools. Enforcing the policy requires a subsequent decision and access testing.
This example covers modern clients; it does not, on its own, block legacy authentication or configure P2 risk-based access. The mailbox CSV identifies target recipients for the native move. Third-party tools and the orchestrator may require different fields and mappings. The code illustrates individual steps within a wider procedure and does not replace its prerequisites.
20. Frequently asked questions (extended FAQ) about Microsoft 365 tenant-to-tenant migration
What is a Microsoft 365 tenant-to-tenant migration and when is it needed?
It is a project to transfer the agreed data and services between Microsoft 365 organisations and prepare the necessary target identities, settings and devices. Common scenarios include mergers, acquisitions, carve-outs and consolidation. The scope must distinguish content that is moved or copied from configuration that is recreated and information that is retained or excluded. Assess domain and partner changes separately, because these may preserve the existing tenant.
How do I migrate Microsoft 365 between tenants step by step?
The process includes assessment, target architecture, method and licence selection for each workload, identity preparation, required coexistence, a pilot, execution and validation. Exchange can synchronise before cutover; OneDrive, SharePoint and Teams follow the selected engine’s requirements. If the domain is moving, release it in the source and verify it in the target during the agreed window. Prepare security from the start and validate it during stabilisation.
How long does a Microsoft 365 tenant-to-tenant migration take?
Duration depends on user numbers, data volume and item counts, identity complexity, Power Platform, Power BI, devices and available business windows. A pilot helps estimate ranges and support capacity. Choose waves or a coordinated cutover according to dependencies. With the orchestrator, mailbox completion does not mean that OneDrive, chats and meetings finish at the same time; communicate the schedule for each workload.
How much does a Microsoft 365 tenant-to-tenant migration cost?
The cost combines assessment and delivery services, normal target service licences, migration-engine licences, and work on coexistence, devices, integrations and support. Include CTUDM when the selected native capabilities require it; native SharePoint and third-party tools have their own conditions. The proposal should define volumes, workloads, exclusions, windows and validation so alternatives can be compared on the same scope.
Which tool should I use to migrate Microsoft 365 between tenants?
Compare native capabilities, Microsoft’s orchestrator, solutions such as Quest On Demand Migration, BitTitan MigrationWiz or ShareGate for their supported workloads, and task-specific automation. The choice depends on moving or copying, existing targets, deltas, permissions, links, chats, meetings, preservation and licensing. The orchestrator supports mailboxes, OneDrive, chats and meetings with restrictions; teams, channels and sites need complementary procedures. Validate the choice with a pilot.
Can I migrate only some users to another Office 365 tenant?
Yes. A subset of users can move as part of a divestiture or phased migration. Design routing, permissions between migrated and non-migrated users, calendar and directory visibility, and Teams collaboration. Shared groups, sites, applications and automation need agreed owners and treatment. Retaining the domain in the source during part of the project affects target addresses and access arrangements.
Can I run incremental synchronisations before cutover?
Exchange Online supports pre-cutover synchronisation through its migration batches when that procedure is used. Native OneDrive and SharePoint moves are single-pass operations and do not support deltas. Third-party tools may offer subsequent passes depending on the workload, API and configuration. Scheduling a completion date in the orchestrator does not mean every workload starts copying immediately; follow the documented processing order.
Do security and retention policies migrate automatically?
Security settings, MFA, Conditional Access, labelling, DLP, retention and eDiscovery need specific preparation and validation in the target. Identities and groups change, and protections tied to the source may affect documents. Holds can block native moves. Any change to preservation or encryption must maintain applicable obligations and be approved by the authorised owners.
How can I minimise email downtime in a tenant-to-tenant migration?
Prepare recipients, complete supported synchronisation, rehearse cutover and configure the required routing. Lower TTL sufficiently in advance and validate legitimate senders, SPF, both DKIM selectors and DMARC. Test the target using temporary domains before releasing the domain, then validate final addresses and delivery afterwards. The plan includes clients, queues, incidents and contingency; the interruption cannot be assumed to be identical in every scenario.
What happens to Intune and devices when changing tenant?
Prepare the target configuration and define, for each operating system and ownership model, how devices will leave the previous environment and be joined or enrolled again. Review profiles, local data, certificates, apps and compliance. Autopilot Reset preserves the current join and management state and does not change tenants on its own. If an external MDM remains, coordinate account, app and access changes with its administrator.
What happens to Teams chats in a tenant-to-tenant migration?
Microsoft’s native orchestrator supports chats and meetings within its documented scope, using Identity Mapping and the required licences and preparation. Some content and conversation types are excluded, duplicate threads may appear, and new messages sent in the source after a thread is migrated are not automatically replicated. Third-party tools have their own scope. Teams, channels, recordings and transcripts need separate handling according to the project.
Does changing partner or domain require a new tenant?
Not by itself. A CSP change can follow the applicable commercial process while preserving the tenant, identities and data. A new domain can be added to the current tenant and used for UPNs and email after verification. Migration becomes necessary when an additional separation, consolidation, architecture or governance requirement calls for another Microsoft 365 organisation.
Should the target OneDrive exist before a native migration?
No. Prepare users, groups, licences and mappings, but prevent target OneDrive site creation before and during the native move. This procedure cannot overwrite or merge an existing site. If target content already exists, assess and authorise a supported approach before continuing. Copying tools may have different requirements and must be used according to their own documentation.
Can the same domain be verified in both tenants during cutover?
The same custom domain cannot be verified in both tenants simultaneously. Prepare the target using temporary domains and remove source references during the agreed window. Then verify the domain in the target and apply the required addresses and settings. Lowering TTL helps with DNS caching, but does not remove the service’s internal release and verification dependencies.
Does Power BI move with Power Platform flows and apps?
Power BI needs its own inventory and procedure for workspaces, reports, models and dependencies. Power Platform solutions do not automatically transfer those objects. Review supported export and publication, data sources, gateways, credentials, RLS, permissions, refresh, links, apps and licensing. The pilot must verify business results and each role’s access before source content is retired.
21. Official resources and external links for Microsoft 365 tenant-to-tenant migration
- Cross-tenant mailbox migration
- Cross-tenant OneDrive migration
- Cross-tenant SharePoint migration
- Entra ID — Cross-tenant access
- Entra ID — Cross-tenant synchronization
- Remove a domain from a tenant · Add a domain · Create DNS records
- Defender for Office 365
- Microsoft Information Protection (Purview)
- Microsoft Intune
- FastTrack — Cross-tenant migration
- Microsoft 365 plan comparison
You can also explore related MSAdvance services: Microsoft 365 migration, Azure architecture, modern workplace and the full catalogue at services.
References for current capabilities and limits
- Microsoft 365 migration orchestrator: scope and licensing.
- Orchestrator: planning and prerequisites.
- Orchestrator: user experience and unsupported items.
- Orchestrator: batches, performance, cancellation and reverse migration.
- DKIM: current Microsoft 365 selectors and values.
- Windows Autopilot Reset: identity and management settings that remain.
- Moving Power Platform environments between tenants.
- Power BI: report and model downloads and restrictions.
- Power BI: rights by licence type.
- Defender for Office 365: plans and current E3 inclusion.
- Retirement of the SharePoint Add-in model in SharePoint Online.
- Microsoft Graph: Conditional Access policy structure.
Use FastTrack references to check available resources, prerequisites and services. They do not imply that delivery of every workload in this article is included. Also consult the vendor guides for the purchased edition, module and version, and retain the scope decisions made for the project.
Related MSAdvance articles provide more detail on migration with Quest On Demand, cross-tenant synchronisation and migration, SharePoint tenant-to-tenant migration and Microsoft Teams tenant-to-tenant migration.
22. Conclusion and next steps in a Microsoft 365 tenant-to-tenant migration
A Microsoft 365 tenant-to-tenant migration that preserves the data within scope depends on a thorough assessment, prepared target architecture, a suitable method for each workload, well-designed coexistence and validation. Procure licences in time and rehearse domain cutover when it is part of the project. Representative pilots, measurable milestones and security from the start help reduce incidents and support user adoption.
As next steps, it is usually useful to:
- Turn this guide into your own checklist, adapted to your business terminology and requirements.
- Define a scoped but representative pilot (one or two key departments).
- Establish a communication and training plan to accompany each wave.
Why rely on a specialised partner for tenant-to-tenant migrations
A specialised Office 365 tenant-to-tenant migration partner brings prior M&A experience, up-to-date knowledge of Microsoft native capabilities and the ability to coordinate IT, security, legal and business teams. This translates into less risk, less improvisation and more internal focus on day-to-day operations.
- Experience in complex scenarios (international mergers, regulated environments, multiple legacy tenants).
- Templates, scripts and checklists already proven in other projects.
- An integrated approach to security, compliance and change management.
Do you want MSAdvance to take care of the entire process?
MSAdvance can support the project end to end: assessment, architecture, coexistence, Exchange/OneDrive/SharePoint and Teams migration within the agreed scope, a domain move where required, security and user adoption. Device, Power Platform and Power BI work is defined and scoped with its dependencies, owners and acceptance criteria.
Contact MSAdvance Discover our migration service
· We also provide support with Modern Workplace and Azure Architecture · All services
The final design should answer practical questions: what the business needs to retain, what each migration engine supports, how users will continue working and what evidence will demonstrate completion. If an item cannot be transferred with sufficient fidelity, agree how it will be rebuilt, archived or otherwise preserved before cutover.
To start the project, bring together the user and workload inventory, the domains involved, data volumes, the target date and critical dependencies. This information supports a realistic proposal covering scope, methods, schedule and support, with information protection and business continuity reflected in the acceptance criteria.






