3 Acquisitions. 3 Tenants. $1.8M in Waste. One Solution.
How a $2 billion manufacturing acquisition turned into an IT nightmare — and how EPC Group turned it into a competitive advantage in 6 months.
Case Study Summary: A Fortune 1000 manufacturing company completed 3 acquisitions in 18 months, inheriting 3 separate Microsoft 365 tenants with 15,000 total users, 12 conflicting domains, and $1.8M per year in duplicate licensing costs. EPC Group consolidated all three tenants into one unified environment in 6 months — on the board's deadline — with zero data loss and $1.8M in immediate annual savings.
The Acquisition Machine That Forgot About IT
The private equity playbook was working beautifully. Three acquisitions in 18 months had transformed a mid-market manufacturer into a $2 billion industrial conglomerate. The strategy was textbook: acquire complementary businesses, eliminate redundancies, cross-sell to expanded customer base, and take the combined entity public within 36 months.
There was just one problem nobody in the deal room had thought about: information technology. Each acquired company brought its own Microsoft 365 tenant. Its own IT team. Its own security policies. Its own naming conventions, folder structures, and institutional knowledge buried in SharePoint sites that nobody had cataloged. The parent company now had three separate digital worlds that could not talk to each other.
The VP of IT — a title that suddenly felt inadequate — described the situation with dark humor: “We bought three great companies. We also bought three separate email systems, three separate intranets, and three separate IT teams who each think their way is the right way. My engineers are spending more time building workarounds than running systems. And the board just asked me why we are paying Microsoft $1.8 million a year more than we should be.”
The board gave him six months. If the tenants were not consolidated by the end of Q2, the IPO timeline would slip — and the PE investors would not be pleased.
The Challenge: Three Companies, Three Cultures, Three Tenants
The parent company's tenant was the most mature — 7,000 users on E5 licenses with a well-governed SharePoint environment and Power Platform applications running production workflows. Acquisition 1, a precision machining company with 4,500 users, ran a lean E3 tenant with minimal governance. Acquisition 2, a specialty materials manufacturer with 3,500 users, had the messiest environment: a mix of E1 and E3 licenses, no MFA enforcement, and SharePoint sites with open permissions that would make a security auditor faint.
The domain situation was particularly painful. The parent company and Acquisition 1 both used @company.com-style domains that were similar enough to cause confusion. Acquisition 2 had four separate domains from its own previous acquisitions that had never been consolidated. Twelve domains total across three tenants, with overlapping distribution lists and external contacts that would break during any migration.
3 Separate Tenants
Parent company (7,000 users, E5), Acquisition 1 (4,500 users, E3), Acquisition 2 (3,500 users, E1/E3 mix) — all with different governance models
$1.8M Annual Waste
Duplicate E5/E3/E1 licenses, redundant admin tools, overlapping security products, and three separate Microsoft enterprise agreements
12 Conflicting Domains
Overlapping email domains, four legacy domains from Acquisition 2's own prior acquisitions, and inconsistent SPF/DKIM/DMARC configurations
34 Custom Applications
Power Apps, Power Automate flows, and custom SharePoint solutions across all three tenants — some duplicating functionality, some critical and unique
6-Month Board Deadline
IPO timeline required consolidated IT infrastructure. Board mandated single tenant by end of Q2 — non-negotiable.
8 Manufacturing Plants
Plant floor workers, shift supervisors, and quality engineers across 8 locations in 4 states — all needing uninterrupted access during migration
The Stakes: An IPO, $1.8M in Waste, and a Board That Was Watching
The financial pressure was relentless. Every month that passed with three separate tenants cost the company $150,000 in duplicate licensing alone. But the licensing waste was just the visible cost. The invisible costs were worse.
Cross-company collaboration was a nightmare. Engineers at the parent company could not share CAD files with the precision machining team without emailing them as attachments — because cross-tenant SharePoint sharing was blocked by security policy. Sales teams could not see each other's customer lists in a unified CRM because the CRM was connected to three different Entra ID directories. The supply chain team had built manual workarounds involving shared Gmail accounts (yes, Gmail — Acquisition 2 had a shadow IT problem) to coordinate production schedules across plants.
The PE investors were growing impatient. The entire thesis of the roll-up strategy depended on operational synergies. But you cannot realize synergies when your people cannot collaborate. The CFO calculated that the delayed synergy realization was costing $3.2 million per quarter in missed cross-selling opportunities and duplicated operational processes.
The Cost of Doing Nothing
“The board does not care about tenant migrations or DNS cutovers,” the VP of IT told EPC Group during the first call. “They care about one thing: can our people work together as one company? Right now, the answer is no. Fix it. You have six months.”
The Solution: Phased Consolidation with Cross-Tenant Migration
EPC Group designed a phased consolidation strategy that treated the parent company's E5 tenant as the destination. This was not just a technical decision — it was a cultural one. By migrating into the most mature environment, EPC Group ensured that governance policies, security controls, and compliance configurations were already in place. The acquired companies would inherit best practices rather than importing chaos.
Cross-Tenant Migration Architecture
EPC Group deployed our proprietary cross-tenant migration tool, which creates a secure bridge between source and target tenants. Unlike Microsoft's native cross-tenant migration feature (which has significant limitations on SharePoint and Teams), our tool migrates the complete workload: Exchange mailboxes with full history, OneDrive files with permissions, SharePoint sites with version history and metadata, Teams channels with conversations and files, Planner boards, Power Automate flows, and Power Apps.
The tool processed 65 TB of data across all three tenants at an average throughput of 80 GB per hour. Each item was checksum-validated. Each permission mapping was logged. Each domain reference was updated in real-time as the DNS cutover progressed.
Domain Consolidation Strategy
The 12-domain puzzle required surgical precision. EPC Group created a domain migration sequence that prioritized mail flow continuity. Primary domains were migrated first, with temporary forwarding rules on secondary domains. Each domain release-and-claim cycle was rehearsed in a test environment before execution. The team managed to complete all 12 domain migrations with zero mail delivery failures — not a single bounce, not a single delayed message.
Manufacturing-Aware Wave Planning
Plant floor workers have different needs than corporate office workers. They check email on shared kiosks. They use Teams on ruggedized tablets. They access SharePoint for quality documents and work orders during shift changes. EPC Group designed migration waves around manufacturing schedules — migrating plant users during planned maintenance windows, overnight shifts, and low-production periods. No production line was ever impacted by the migration.
Cross-Tenant Migration
Proprietary tool bridging 3 source tenants to 1 target with full workload migration
12-Domain Consolidation
Surgical DNS cutover sequence with zero mail delivery failures
Manufacturing-Aware Waves
Migration scheduled around plant shifts, maintenance windows, and production cycles
Migration Timeline: 24 Weeks from Kickoff to Single Tenant
Discovery & Architecture
Inventoried 15,000 users across 3 tenants. Mapped 4,800 SharePoint sites, 2,400 Teams instances, 65 TB of data. Identified 12 domain conflicts and 34 custom Power Platform applications. Designed target tenant architecture with the parent company tenant as the destination.
Identity & Domain Planning
Resolved 12 domain conflicts. Planned DNS cutover sequence for all domains. Configured cross-tenant trust and mail routing. Set up Entra ID structure for merged organization with role-based access. Migrated Conditional Access policies from all three tenants into unified policy set.
Pilot Migration
Migrated 750 users (250 from each tenant). Tested cross-plant collaboration scenarios. Validated manufacturing-specific workflows: shift scheduling, work order management, quality document access. All 34 Power Platform apps tested in target environment.
Wave Migration
Migrated ~1,400 users per week across 11 waves. Plant floor workers migrated during maintenance windows. Corporate office migrated department by department. Acquisition 1 completed by Week 14. Acquisition 2 completed by Week 18. Final stragglers and VIP accounts completed by Week 20.
Domain Cutover & Decommission
Final DNS cutover for all 12 domains. Source tenants set to read-only. License reclamation initiated for duplicate subscriptions. Global Address List unified across all 15,000 users for the first time.
Hypercare & Optimization
Dedicated support team handled 312 post-migration tickets (2.1% rate). License optimization eliminated $1.8M in annual duplicate costs. Board presentation delivered with migration metrics. Source tenant decommissioning scheduled for 90 days post-migration.
The Results: One Company, One Tenant, One Future
For the first time since the acquisitions began, 15,000 employees could find each other in a single Global Address List. They could share files without email attachments. They could join Teams meetings without guest invitations. They were, finally, one company.
“When I presented the consolidation results to the board, the chairman said something I will never forget: 'This is the first time since we started acquiring companies that it actually feels like we are one company.' That was not a technology compliment. That was a business transformation compliment. EPC Group did not just merge our tenants — they merged our cultures. The $1.8 million in licensing savings was almost an afterthought compared to what unified collaboration unlocked for our business.”
— VP of Information Technology, Fortune 1000 Manufacturing Company
The Ripple Effects Nobody Expected
The immediate financial impact was clear: $1.8 million per year in eliminated duplicate licensing. The VP of IT had his board-ready number. But the downstream effects of consolidation surprised even EPC Group.
+$4.7M in first year
Sales teams could finally see combined customer lists, identifying cross-sell opportunities that had been invisible
23% improvement
Unified Teams channels replaced shadow IT workarounds for production scheduling across 8 plants
12 FTEs freed
Three IT teams managing three tenants became one team managing one — freeing 12 engineers for strategic projects
85% risk reduction
Acquisition 2's ungoverned tenant was eliminated. Unified Conditional Access, MFA, and DLP policies applied to all 15,000 users
The total first-year business impact — combining license savings, cross-selling revenue, supply chain efficiency, and IT staff redeployment — exceeded $8 million. The migration paid for itself in the first month. By the time the IPO process began nine months later, the consolidated technology platform was cited in the S-1 filing as evidence of operational maturity.
Frequently Asked Questions
How long does it take to consolidate 3 Microsoft 365 tenants after an acquisition?
Consolidating 3 Microsoft 365 tenants with a combined 15,000 users typically takes 4-6 months. This includes 4-6 weeks of discovery and planning, 2-3 weeks of pilot migration, 8-12 weeks of batch migration across all three tenants, and 2-4 weeks of hypercare. Factors that affect timeline include: data volume (this client had 65 TB), domain conflicts (overlapping email domains required DNS planning), compliance requirements, custom applications, and board-imposed deadlines. EPC Group completed this engagement in 24 weeks (6 months) — on schedule with the board deadline. Our proprietary cross-tenant migration tool processes data 40-60% faster than native Microsoft tools, which was critical for meeting the deadline.
What are the biggest risks of M365 tenant consolidation after a merger or acquisition?
The five biggest risks of tenant consolidation are: (1) Domain conflicts — when acquired companies share email domains or have conflicting UPN suffixes, DNS cutover must be carefully orchestrated to avoid mail delivery failures. (2) Data loss — migrating SharePoint sites, OneDrive files, and Exchange mailboxes across tenants risks data loss if the tool does not handle throttling, large files, or special characters correctly. (3) Identity conflicts — duplicate user accounts, group naming collisions, and Conditional Access policy conflicts can lock users out. (4) Business disruption — users lose access to Teams channels, shared calendars, and collaborative documents if the migration is not sequenced correctly. (5) Compliance gaps — during the transition period, DLP policies, retention rules, and audit logging may have gaps that create regulatory exposure. EPC Group mitigates all five risks through our proven M&A migration methodology and cross-tenant migration tool.
How much does M365 tenant consolidation cost after an acquisition?
M365 tenant consolidation costs depend on user count, data volume, and complexity. For a 3-tenant consolidation with 15,000 users: discovery and planning typically costs $25,000-$50,000. Migration execution ranges from $150,000-$350,000 depending on data volume and custom requirements. Total engagement cost for this manufacturing client was within the $200,000-$400,000 range, which delivered $1.8M in first-year savings from eliminated duplicate licensing alone — a 5x ROI in year one. Ongoing annual savings continue indefinitely. EPC Group provides fixed-fee pricing after discovery so organizations have budget certainty. M&A consolidations with tight board deadlines may carry a timeline acceleration premium of 15-25%.
What happens to Teams channels and SharePoint sites during tenant consolidation?
Teams channels and SharePoint sites are migrated from source tenants to the target tenant with full content preservation. EPC Group migrates: Teams channels (standard and private) with all messages, files, tabs, and connectors. SharePoint sites with document libraries, lists, permissions, version history, and metadata. Teams meeting recordings and transcripts. Planner boards and tasks associated with Teams channels. For this manufacturing client, we migrated 2,400 Teams instances and 4,800 SharePoint sites across three tenants. The key challenge was Teams channels that included members from multiple source tenants — these were migrated last, after all member accounts existed in the target tenant, to preserve membership and permissions.
How do you handle conflicting email domains during tenant consolidation?
Domain conflicts are the most technically complex aspect of tenant consolidation. When two acquired companies use the same email domain (e.g., both use @company.com) or when domain ownership must transfer between tenants, EPC Group follows a specific process: (1) Domain ownership verification — confirm DNS control for all domains across all tenants. (2) Domain release — remove the domain from the source tenant (requires removing all references to the domain from user accounts, groups, and applications first). (3) Domain claim — add and verify the domain in the target tenant. (4) DNS cutover — update MX, SPF, DKIM, and DMARC records. (5) Mail flow validation — confirm delivery to all mailboxes in the target tenant. During the domain transfer window (typically 2-4 hours), EPC Group configures temporary routing to ensure zero mail loss. For this client, we managed 12 domains across 3 tenants with zero mail delivery failures.
Can you consolidate M365 tenants without disrupting manufacturing operations?
Yes. Manufacturing operations depend on Microsoft 365 for shift scheduling (Teams), work order management (SharePoint), quality documentation (OneDrive), and supply chain communication (Exchange). EPC Group migrates manufacturing users during shift changes and low-production periods. In this case study, plant floor users were migrated during scheduled maintenance windows (typically overnight or weekend shifts). Office-based users were migrated during normal business hours with zero disruption thanks to our coexistence architecture. The key is our wave planning methodology, which sequences migration by plant location, shift schedule, and departmental dependencies — ensuring that no production team is split across tenants during their active shift.
Planning a Post-Acquisition Tenant Consolidation?
EPC Group completes 50+ M&A tenant consolidations per year. Whether you have 2 tenants or 10, we deliver unified environments on your board's timeline with zero data loss.