LeadThem Consulting
Case study · Private equity

Multi-Portfolio Microsoft 365 Migration for a Private Equity Firm

Simultaneously migrating multiple portfolio companies across three continents, handling archive mailboxes, litigation holds, device migration, and Entra ID provisioning.

TL;DR. Private equity firm, 120+ users across three portfolio companies in NAM, EUR, and GBR. Mailboxes, archives, OneDrive, Teams, SharePoint, and workstations migrated simultaneously. Litigation holds preserved, archive size limits resolved, hybrid device ReACL via Ivanti Neurons.

What was the client environment?

A major private equity firm needed to consolidate the Microsoft 365 environments of multiple portfolio companies after a series of acquisitions. The portfolio companies, spanning operations in North America, Europe, and the United Kingdom, each had their own M365 tenants, Active Directory environments, and compliance requirements including litigation holds on archived mailboxes. All needed to be migrated to a unified target platform on overlapping timelines.

What made this migration challenging?

Private equity portfolio migrations are uniquely complex because each company has different IT maturity, compliance posture, and operational requirements, yet they all need to land on the same target platform:

How did LeadThem approach the migration?

Parallel portfolio execution

Phase 1: Discovery across all entities. Ran mailbox discovery for all portfolio companies including user, shared, and resource mailboxes. Pulled archive mailbox size data and litigation hold lists. Ran DirSync read/match workflows for on-premises users and computers. Updated CDS documentation for each entity.

Phase 2: Data sync and device preparation. Started mailbox and OneDrive initial syncs across all regions, completing GBR and EUR first, then NAM (the largest batch). Ran Teams chat discoveries and SharePoint site analysis. Prepped Entra ID provisioning packages, AD agent installation scripts, and DUA installation scripts for device migration. Configured device migration profiles for ReACL and Entra Join operations.

Phase 3: Production migration and troubleshooting. Executed production migrations per entity while troubleshooting archive mailbox size limit errors. Tested hybrid device ReACL on WhiteStar devices. Managed agent deployment via the client's Ivanti Neurons endpoint tool. Ran delta syncs on mailboxes, OneDrive, and Teams across all entities to minimize cutover window data.

What technical challenges did we solve?

What were the results?

All three portfolio companies were migrated to the unified M365 platform, with mailboxes, archive mailboxes, OneDrive data, Teams chats, SharePoint sites, and workstations all transitioned across three continents. Litigation holds were preserved throughout, archive mailbox size issues were resolved, and the private equity firm now has a single M365 platform for centralized IT management across its portfolio.

Which tools and technologies were used?

Why LeadThem Consulting

Private equity firms need a migration partner who can manage multiple portfolio companies simultaneously without sacrificing quality on any one engagement. LeadThem Consulting's consultant managed three parallel migrations across three continents, navigating archive size limits, litigation hold requirements, and device migration complexity while maintaining clear RAID tracking and proactive communication. When new portfolio companies were added mid-flight, we absorbed the scope increase and kept all workstreams on track.

How are litigation holds preserved during an M365 tenant migration?
Held mailboxes are identified upfront in discovery, the hold status is documented, and Quest ODM migrates the mailbox content with retention metadata intact. Post-migration validation confirms the hold is reapplied in the target tenant. Any loss of held content could expose the firm to legal liability, so chain-of-custody documentation is part of the standard deliverable.
What is hybrid device ReACL?
ReACL (re-access control list) is the process of updating local file and registry permissions on a workstation to reference the new user identity in the target domain or tenant. It is used during hybrid device migrations to preserve local user data and application settings when the workstation is rejoined to a new identity provider.
How does Quest ODM handle archive mailbox size limits?
Archive mailboxes in M365 can exceed default target tenant limits (typically 100GB). When migrations fail due to size limits, the remediation options are: increase the target tenant's archive mailbox quota, split the archive across multiple mailboxes, or perform selective archive migration based on retention policy. Each option has different implications for compliance and end-user experience.
How is M365 migration sequenced across multiple time zones?
Sync earlier time zones first (EUR/GBR) so they complete overnight relative to later zones (NAM). This staggers the network and ODM load across regions and minimizes the total elapsed time to reach a consistent sync state before cutover.

Consolidating M365 across portfolio companies?

LeadThem Consulting manages multi-entity PE migrations with the discipline to keep every workstream moving.

Schedule a portfolio migration assessment