Multi-Tenant M365 Migration for M&A

Multi-Tenant Microsoft 365 Migration: Tenant-to-Tenant Consolidation Guide

Multi-tenant Microsoft 365 consolidation is one of the most common M&A-driven engagements in 2026. When companies acquire each other, the acquired tenant must be consolidated into the acquiring tenant — covering identity, mailboxes, SharePoint, OneDrive, Teams, Power Platform, and integrated SaaS apps. The complexity is materially higher than greenfield M365 deployment because every existing relationship and integration must be preserved or migrated.

This guide walks through the complete tenant-to-tenant consolidation methodology as we deliver it for Fortune 500 healthcare, financial services, government, and manufacturing organizations. EPC Group has delivered 30+ tenant-to-tenant consolidations since the original Office 365 program.

TL;DR — Engagement Profile

Acquired Org Size	Timeline	EPC Group Fixed-Fee	Tools
100-500 users	8-14 weeks	$100,000-$220,000	ShareGate + Microsoft Native
500-2,000 users	14-20 weeks	$220,000-$450,000	ShareGate + AvePoint
2,000-5,000 users	18-26 weeks	$400,000-$800,000	AvePoint Migrator
5,000-10,000 users	22-32 weeks	$700,000-$1,300,000	AvePoint Enterprise

What's Migrating

A complete tenant-to-tenant consolidation spans:

• Identity — Microsoft Entra ID directory, group structure, SSO connections to SaaS apps
• Email — Exchange Online mailboxes, distribution lists, mail flow rules, calendar resources, public folders
• Files — SharePoint Online sites and OneDrive personal storage
• Collaboration — Microsoft Teams chats, channels, tabs, meeting recordings
• Apps — Power Apps, Power Automate flows, Dataverse environments
• Compliance — Audit log archive, sensitivity labels, retention policies
• Endpoint — Microsoft Intune device migration

Plus integrated SaaS apps (Salesforce SSO, Workday, ServiceNow, etc.) and Microsoft 365 Copilot license reassignment.

Phase 1: Discovery (3-4 weeks)

Source Tenant Inventory

• User accounts and licensing
• Mailbox sizes and complexity
• SharePoint site collection inventory
• Microsoft Teams inventory
• Power Platform environment audit
• SaaS app SSO connections

Target Tenant Readiness

• Capacity headroom for incoming users
• Microsoft Entra ID schema alignment
• Conditional Access policy compatibility
• Existing governance framework alignment
• Microsoft 365 Copilot readiness

Compliance Discovery

• HIPAA / FINRA / FedRAMP / CMMC requirements (which tenant must remain on which compliance posture)
• Data residency considerations
• Audit log archive plan
• Legal hold transfer for in-flight investigations

Phase 2: Architecture (2-4 weeks)

Identity Migration Design

• Source Microsoft Entra ID → target Microsoft Entra ID
• B2B guest pass-through for users not migrating
• SSO reconfiguration for SaaS apps (Salesforce, Workday, ServiceNow)
• Group structure consolidation
• Privileged access role mapping

Domain Strategy

• Source domain handling (consolidate, retain, or retire)
• Email domain cutover plan (DNS, SPF, DKIM, DMARC)
• Custom domain conflicts resolution

Content Migration Plan

• SharePoint site mapping (source → target target site collections)
• OneDrive per-user migration sequence
• Microsoft Teams chat history preservation strategy
• Power Platform environment migration

Phase 3: Pilot Migration (3-4 weeks)

Pilot Scope

• 50-100 users from acquired entity
• 5-10 SharePoint site collections (mix of executive, departmental, project)
• Power Platform environment migration validation
• SSO reconfiguration testing for connected SaaS apps

Pilot Validation

• Mailbox content fidelity (folder structure, calendar, mobile devices)
• SharePoint permission preservation
• OneDrive sync validation
• Teams chat history preservation
• Power Apps and Power Automate functionality
• SSO testing for SaaS apps

Phase 4: Wave Migrations (8-16 weeks)

Standard Wave Sequence

Wave 1: IT and Engineering — high tolerance for issues, validates tooling
Wave 2: Executive and Administrative — high-priority stakeholders, white-glove
Wave 3-N: Departmental — Sales, Marketing, Finance, HR, Operations

Per-Wave Execution

• Mailbox migration via Microsoft Native or BitTitan
• OneDrive content migration via ShareGate or AvePoint
• SharePoint site migration with permission re-mapping (source group SIDs → target group SIDs)
• Microsoft Teams membership migration
• Power Platform environment cutover
• SaaS app SSO reconfiguration
• Conditional Access policy assignment

Per-Wave Validation

• Mailbox content fidelity
• OneDrive sync per user
• SharePoint permission spot-check
• Teams chat history validation
• SSO functionality verification
• Help desk ticket triage

Phase 5: Cutover and Decommissioning (2-4 weeks)

Cutover

• DNS cutover (MX records to target tenant Exchange Online)
• Mail flow validation
• Final delta migrations
• Source tenant set to read-only

Decommissioning

• 30-90 day source tenant preservation hold
• Audit log archive transfer
• Legal hold transfer for active investigations
• Source domain DNS retention or release
• Source tenant license cancellation

Frequently Asked Questions

How long does a tenant-to-tenant Microsoft 365 migration take?

EPC Group standard timelines: 8-14 weeks for 100-500 users, 14-20 weeks for 500-2,000, 18-26 weeks for 2,000-5,000, 22-32 weeks for 5,000-10,000+ users. Discovery 3-4 weeks, architecture 2-4 weeks, pilot 3-4 weeks, wave migrations 8-16 weeks, cutover 2-4 weeks.

What's the cost of tenant-to-tenant migration?

EPC Group fixed-fee tenant-to-tenant migration, tiered by acquisition size: 100-500 users, 2,000-5,000 users, and 5,000-10,000 user enterprise acquisitions. Plus migration tooling (vendor-quoted) and Microsoft 365 license reassignment.

Can Microsoft Teams chat history be preserved?

Yes — for tenant-to-tenant migrations using ShareGate or AvePoint, Microsoft Teams chat history is preserved. Microsoft Native tools have limited Teams chat preservation. Most enterprises use ShareGate or AvePoint specifically for Teams chat history preservation.

What about SaaS app SSO connections?

SSO connections to Salesforce, Workday, ServiceNow, etc. must be reconfigured during migration. EPC Group typical migration includes SSO migration scope (typically 15-50 SaaS apps) with parallel-run period for validation.

Can both tenants exist temporarily?

Yes — the standard pattern is parallel coexistence during the migration window (typically 8-16 weeks). Mail flow routes both tenants, users have access to both during the transition, and migration completes incrementally per wave. Beyond 6 months of parallel operation, governance debt accumulates rapidly.

What's the role of Microsoft Entra ID guest accounts?

For users not migrating from the acquired tenant (e.g., contractors, partners), Microsoft Entra ID B2B guest invitations preserve access to target tenant resources. Most tenant-to-tenant consolidations include 100-500 B2B guest invitations to maintain external collaboration relationships.

How does compliance posture transfer?

The acquiring tenant's compliance posture (HIPAA, FINRA, FedRAMP, CMMC) governs the merged tenant. Acquired tenant audit logs are archived for retention compliance. Legal holds active on the acquired tenant transfer to the target tenant via Microsoft Purview eDiscovery (Premium).

What about Microsoft 365 Copilot licenses?

Copilot licenses must be reassigned during migration. For organizations with significant Copilot deployment, EPC Group typical migration includes 30-day Copilot Readiness Assessment for the acquired user population (oversharing audit, sensitivity-label gap analysis) before Copilot license reassignment.

How EPC Group Delivers Tenant-to-Tenant Migrations

EPC Group has delivered 30+ tenant-to-tenant Microsoft 365 consolidations since the original Office 365 program. Every engagement includes:

• Microsoft Entra ID identity migration with group structure consolidation
• Mailbox, calendar, contacts migration
• SharePoint Online + OneDrive content migration with permission preservation
• Microsoft Teams chat history preservation (via ShareGate or AvePoint)
• Power Platform environment migration
• SaaS app SSO reconfiguration
• Microsoft 365 Copilot reassignment with readiness assessment
• Audit log archive transfer
• Written migration runbook and post-go-live managed services

For regulated industries, every migration includes BAA verification (HIPAA), regulatory-specific control mapping, audit-defensible documentation, and incident response runbook scoped to industry-specific breach notification requirements.

Next Steps

Schedule a 30-minute discovery call at /schedule or call (888) 381-9725. Senior architects (not sales reps) take discovery calls.

Related reading: Microsoft 365 Migration Checklist 2026, SharePoint Online Migration Guide 2026, and HIPAA-Compliant Microsoft 365.