Assess the inherited estate
Inventory tenants, domains, mail routes, security policies, shared mailboxes, delegated access, sending applications and archive dependencies. Identify the teams and suppliers who can authorise each change.
Email for mergers, acquisitions and divestments
Keep communication moving while organisations come together or separate.
We plan the domains, security, mailbox transitions and records that need to survive the change.
The business needs to communicate from day one.
An acquisition brings together people who may have different domains, security products, directories and support arrangements. A divestment has to separate them without carrying across access or records that belong elsewhere.
We establish what must be available at completion, what can remain separate during transition and what has to be preserved before any platform is retired.
Plan the transition around the deal.
Define day-one communication
Agree addresses, routing, coexistence and support responsibilities during the transition. Where a transitional service agreement applies, record the email dependencies and exit dates.
Consolidate or separate
Sequence identity preparation, domain changes, mailbox movement and security policy changes. Carve-outs include the access and data boundaries approved by the relevant owners.
Preserve the required records
Map holds, retention policies, archive access and search/export requirements before selecting a migration method. Your legal and records owners approve the preservation approach.
Deal with holds before scheduling the move.
Microsoft documents that its native cross-tenant mailbox migration blocks mailboxes on hold. That constraint has to be addressed in the design; removing a hold merely to unblock a move is not our default approach.
We agree a supported preservation and transition plan with your legal team, platform owners and, where necessary, the vendor. The order records how records remain accessible, how results will be checked and who can approve source-system retirement.
What your team receives.
Before implementation
An estate and dependency map, decisions register, proposed target design, transition sequence and scoped implementation quotation.
For each change
An approved change record, test and recovery criteria, named decision owners and communications for the affected teams.
At handover
Configuration and support records, migration exceptions, record-preservation checks and an agreed list of residual actions.
At retirement
A documented decision on remaining data, legal holds, forwarding, application dependencies, supplier services and access removal.
Start with Discovery & Design.
An M&A programme needs its own scope. The standard per-mailbox migration price does not cover an acquisition, carve-out or records-preservation programme.
Discovery is priced around the systems to assess. Implementation follows a separate quotation covering the agreed waves, coexistence, security and retention requirements. What discovery includes.
Technical and regulatory references
Checked 19 October 2026. The service scope above is our proposed delivery approach. These references explain the technical constraints and regulatory distinctions.
Plan your email transition.
Tell us about the environment and the outcome you need.