Microsoft 365 Tenant-to-Tenant Migration
M&A, divestiture, rebrand. Mailboxes + OneDrive + SharePoint + Teams + domains — all consolidated into one target tenant. 70% of our tenant moves are M&A. 2-4 hour cutover window. Fixed-fee SOW.
BitTitan · Quest · ShareGate · MS Solutions Partner
Every workload. Tenant to tenant.
What nobody tells you about T2T.
70% of tenant migrations we deliver are M&A scenarios. Two companies become one — two tenants must become one. Co-existence, permission mapping, calendar conflicts all hit on day one.
Microsoft does not allow private 1:1 Teams chats to migrate between tenants. Called out in the SOW. Group chats in channels move fine. Users briefed before cutover so nothing surprises them Monday.
Background sync runs for days. DNS cutover window is 2-4 hours off-hours. MX, SPF, DKIM flip. Final delta sync captures last writes. Rollback one-click if anything fails.
Source tenant licences do not carry across. Target tenant needs its own Microsoft 365 subscriptions. We help right-size and procure as Microsoft Solutions Partner — volume pricing on Business Premium, E3, E5.
Every workload. Every permission.
Cross-tenant trust + identity
Configure migration permissions, Entra ID cross-tenant access, synced identity model, and cutover strategy (new UPN, retained UPN, merged identity).
Mailbox migration
Exchange Online mailboxes, shared mailboxes, room/equipment mailboxes, distribution groups, transport rules. Delta sync up to MX cutover means no missed mail.
OneDrive + SharePoint
OneDrive files and folders with permissions. SharePoint sites and document libraries with navigation + metadata. Large libraries use ShareGate for throughput.
Microsoft Teams
Teams, channels, channel files, and Teams-attached SharePoint sites. Group chats in channels move. Private 1:1 chats cannot migrate — called out upfront.
Domain + DNS cutover
Source domain transferred to target tenant during 2-4 hour off-hours window. MX, SPF, DKIM, DMARC, Autodiscover. Rollback ready if anything fails.
BitTitan / Quest / ShareGate tooling
Tool selection matched to workloads, data volumes, and tenant configuration. Enterprise-grade tools for background sync, incremental, and automated batch cutover. BYOL or we procure.
Four phases. Dual-tenant playbook.
Discover
1-2 weeks · Audit both source and target tenants, mailbox/site inventory, permissions map, domain conflict check, fixed-price SOW.
Prep
1 week · Target tenant provisioned/hardened, cross-tenant trust configured, identity strategy signed off, runbook + rollback approved.
Migrate
1-6 weeks · Background sync of mailboxes, OneDrive, SharePoint, Teams. Pilot wave first. Incremental sync runs 24/7 until cutover.
Cutover
2-4 hrs off-hours · Domain transfer, MX flip, final delta sync, validation. 14-30 days hypercare covers permission issues, mailbox access, Outlook profiles.
The engineers on your project.
No outsourced ticket triage. The same three engineers handle M&A architecture decisions, cross-tenant discovery, domain release coordination, and the cutover window.
Sreenivasa Reddy
Founder & Principal Migration Engineer
MCSE Messaging · 25 yrs · 500+ migrations led
Owns the M&A architecture decisions: tenant consolidation strategy, domain ownership transfer sequencing, license SKU rationalization across the merged org. Direct contact for board/CFO conversations on M&A IT integration cost + timeline.
Roshan Pujari
Senior Migration Engineer · T2T Lead
Microsoft Certified · M365 Administrator
Runs the cross-tenant discovery: source + target tenant inventory, conflicting SKUs, OneDrive sharing-link dependency mapping, Teams/channel architecture. The person who sees the tenant overlap problems before they become cutover problems.
Bhargav
Senior Migration Engineer · Mail Flow + Domain Cutover
Microsoft Certified · Exchange + M365 Messaging
Cross-tenant mail flow during coexistence (no MX shared between tenants — per-domain handling needed). Domain release from source tenant + add to target tenant. Owns the post-cutover delta sync window.
Three engagements. Three different shapes.
Anonymized. Scope → challenge → fix → outcome. M&A consolidations, divestiture splits, and vendor-managed-tenant escapes — the full T2T spectrum.
Fintech / SaaS · 257 users · 4 countries · M&A consolidation · M365 Tenant A → Tenant B (post-acquisition)
Post-acquisition consolidation of 4 country tenants into one in a single week
Scope
Acquired company had separate Microsoft 365 tenants per country (Singapore, Malaysia, India, Dubai) inherited from the seller. Total ~257 users across all four. Target was the parent company's existing M365 tenant. Required: mailboxes, OneDrive content with sharing links, SharePoint sites, Teams + channels, Entra ID identities, three custom domains transferred.
Challenge
Four source tenants meant four sets of credentials, four sets of admin policies, four different license SKU mixes. Some users existed in multiple tenants (regional dual-employment scenarios). Teams 1:1 private chat history cannot be migrated by ANY tool — had to be communicated upfront. Sharing links in OneDrive needed re-rooting to the target tenant URLs. Three custom domains had to be released from source tenants and added to the target — each domain release has a 7-day cooldown unless escalated to Microsoft Support.
Fix
Used BitTitan MigrationWiz tenant-to-tenant tooling for the bulk move — mailboxes, OneDrive, SharePoint sites, Teams + channel files all in scope. Per-source-tenant license inventory built first to right-size the target. Domain release paths: parallel tickets opened with Microsoft Support to skip the 7-day cooldown for two of the three domains; third domain released on natural timeline. Conflicting users (in 2+ source tenants) handled with merge-and-deduplicate logic: kept the target-tenant identity, brought across mailbox content from the larger source, archived the smaller source mailbox. Teams private chat limitation announced to all users 2 weeks before cutover.
Outcome
257 users on the consolidated target tenant within 1 week. All 3 custom domains successfully transferred. Sharing links re-rooted to new tenant URLs. Conflicting users de-duplicated with no email or document loss. Customer's consolidated tenant now has unified governance + license rationalization.
SaaS / Software · ~140 users · Divestiture (one-tenant split into two) · M365 Tenant → split into Tenant A + Tenant B
Reverse T2T — splitting one tenant into two during a divestiture
Scope
Divestiture scenario: one Microsoft 365 tenant being split into two tenants as a business unit was being spun off. ~140 users total, ~85 staying with parent (Tenant A) and ~55 going to the new spun-off entity (Tenant B). Required: spin-off users' mailboxes, OneDrive content, Teams membership, identity, and one of the custom domains all moved to the new Tenant B.
Challenge
Reverse T2T is harder than forward — instead of consolidating you're partitioning. Shared OneDrive content with mixed-membership permissions had to be carefully evaluated: which copy goes to which tenant? Teams memberships had to be split cleanly. Domain assignment had to be coordinated with legal (the spun-off entity got a new domain, but kept some email aliases on the original domain for 6 months as part of the transition agreement). Compliance/eDiscovery holds on certain mailboxes had to follow the user to the new tenant.
Fix
Pre-cutover: per-user destination mapping ratified by HR + legal. New Tenant B provisioned with right-sized licensing for the 55 users. Mailboxes + OneDrive moved to Tenant B via tenant-to-tenant tooling (BitTitan/Quest/ShareGate per-asset class). Teams memberships rebuilt manually in Tenant B (no automated tool handles Teams membership splits). New domain added to Tenant B + old-domain email aliases kept active in Tenant A with forwarding rules to the new addresses for the 6-month transition period. eDiscovery holds re-applied in Tenant B on day 1 for the relevant users.
Outcome
Clean split of 140 users into two tenants over 3 weeks. Spun-off entity operational on day 1 of legal close. Email forwarding kept business continuity during the 6-month brand transition. Compliance holds preserved across the split with no continuity gaps.
Healthcare / HIPAA-regulated · ~85 users · Tenant consolidation after IT vendor change · M365 Tenant (vendor-managed) → Direct M365 Tenant
Migration off vendor-managed tenant to direct-customer tenant — HIPAA-compliant
Scope
~85-user healthcare network on a Microsoft 365 tenant that had been provisioned and managed by their previous IT vendor (CSP partner). Vendor relationship was ending. Customer needed everything moved to a direct-customer M365 tenant (own billing relationship with Microsoft, own admin, own BAA). PHI present in mailboxes, OneDrive, and Teams files.
Challenge
Vendor-managed tenant means the vendor has the tenant ownership and admin keys — full migration off requires their cooperation (good faith required, not always given). HIPAA controls on the source tenant (BAA, sensitivity labels, retention holds) all had to be replicated on the target tenant before migration. eDiscovery holds on certain physician mailboxes had to follow them across.
Fix
Coordinated with the outgoing vendor for a clean handoff (timed with their contract end). Provisioned new direct-customer M365 tenant with HIPAA-grade configuration: BAA signed Microsoft-direct, Microsoft Purview sensitivity labels for PHI auto-classification, Conditional Access for PHI-classified content, audit log retention extended. Migration ran with SHA-256 verification per item. eDiscovery holds re-applied on target tenant on day 1. Outgoing vendor's tenant deprovisioned 30 days post-cutover.
Outcome
85 users on customer-owned direct M365 tenant within 4 weeks. BAA in place on new tenant before any PHI moved. Compliance holds preserved across the transition. Customer now owns their own M365 relationship — can change MSPs without another tenant migration.
The T2T-specific realities.
T2T is not "just another migration." There is no hybrid coexistence between two M365 tenants, the platform has hard constraints (Teams chat history, domain cooldowns), and M&A timelines amplify every gotcha.
No hybrid coexistence between two M365 tenants
Unlike Exchange→M365 (where Hybrid Configuration Wizard lets you run both side-by-side), there is NO equivalent for two M365 tenants. You cannot share a single MX record between two tenants. Coexistence is per-domain or per-user with separate mail flow. Plan for cleaner cutover windows than you would for an on-prem migration — usually wave-based per-business-unit.
Teams 1:1 private chat history — non-migratable
No tool (BitTitan, Quest, ShareGate, native Microsoft) can migrate Teams 1:1 private chat history between tenants. This is a Microsoft Teams platform constraint, not a vendor limitation. Public/team channels DO migrate cleanly. Announce to users 2 weeks before cutover so nobody is surprised — most accept it once they understand it's a platform limit, not a screw-up.
Domain release + add — the 7-day cooldown
When a custom domain is removed from one M365 tenant, Microsoft enforces a default 7-day cooldown before that domain can be added to another tenant. For M&A timelines this is often unacceptable. We open a parallel ticket with Microsoft Support to request expedited release for business-critical scenarios — typically granted within 24-48 hours when there is a clear M&A justification.
OneDrive sharing links — re-rooting to new tenant URLs
OneDrive sharing links contain the source tenant URL. After T2T migration those links become broken. Standard tools can re-root links inside migrated documents (Word/Excel/PowerPoint with embedded sharing links) but external links (in emails, third-party systems, CRM records) need separate handling. We deliver a sharing-link inventory report so you know what to update post-cutover.
License SKU rationalization across merged tenants
Acquisitions often inherit a license mix you wouldn't buy from scratch. T2T is the natural moment to right-size: which users actually need E5 vs E3? F1/F3 for frontline staff who only use email + basic apps? Microsoft Purview tenant-wide vs per-seat? We do a license-rationalization assessment alongside the migration — typical savings 15-30% on annual M365 spend post-consolidation.
Conflicting users (existing in both source and target)
Common in M&A: a user has accounts in both tenants (board member, dual-role employee, contractor). On consolidation we de-duplicate per a documented policy: keep the target-tenant identity, merge mailbox content from the larger source mailbox, archive the smaller source mailbox to the user's new mailbox as a folder. Edge cases (different email aliases, conflicting display names) handled per-user during the discovery phase.
Frequently Asked Questions
What is a Microsoft 365 tenant to tenant migration?+
How do you migrate between Microsoft 365 tenants?+
How long does an Office 365 tenant migration take?+
What data can be migrated between Microsoft 365 tenants?+
Can users keep their email addresses after tenant migration?+
How much does a Microsoft 365 tenant to tenant migration cost?+
How do you handle the 7-day domain release cooldown when we have an aggressive M&A timeline?+
What happens to OneDrive sharing links after the migration?+
Can you migrate Teams 1:1 private chat history between tenants?+
We have a divestiture — splitting one M365 tenant into two. Do you do reverse T2T?+
We have users on compliance/legal hold in the source tenant — does that follow them to the target?+
Consolidate tenants clean.
M&A, divestiture, rebrand. Mailboxes + OneDrive + SharePoint + Teams + domains. 2-4 hour cutover. Fixed-fee SOW.
Microsoft Solutions Partner · BitTitan / Quest / ShareGate certified · Fixed-fee SOW · 30 days hypercare
Migrations Hub
All 12 migration practices — platforms, pricing, timelines.
Learn More →Microsoft 365 Migration
Email, OneDrive, Teams, SharePoint — all sources.
Learn More →Exchange → M365
On-prem Exchange 2010-SE to Exchange Online.
Learn More →Microsoft 365 Licensing
Business, Enterprise E3/E5 — volume pricing on the target tenant.
Learn More →Cloud Migration Strategies & Step-by-Step Guides
Google Workspace to Microsoft 365 Migration: The Complete 2026 Playbook (Gmail, Drive, and Shared Drives)
A step-by-step migration playbook for moving from Google Workspace to Microsoft 365 covering Gmail to Exchange Online, Drive to OneDrive/SharePoint, identity migration, DNS configuration, and post-migration security — with tool comparisons and timeline estimates.
50 Cloud Migration Statistics for 2026 — Success & Failure Rates
A comprehensive roundup of 50 cloud migration statistics for 2026 covering success rates, failure causes, migration costs, timelines, repatriation trends, and multi-cloud strategy data from Gartner, IDC, Flexera, and Forrester.
55 Cloud Computing Statistics for 2026: Spending, Migration & Adoption
55 cloud computing statistics for 2026 covering global spending ($679B), migration timelines, multi-cloud adoption, data center investment, and SMB cloud budgets with sourced data.
Case study: Hosting panel-based IMAP to Microsoft 365 Migration for government services in Virginia
Client overview A government services agency in Virginia, with over 1,000 employees, had been using a hosting panel-based IMAP system for their email and communication needs. As the agency grew, they faced challenges in managing email effectively, ensuring data security, and fostering collaboration across teams. Given the critical nature of their services, the agency needed a […]