# Post-Merger IT Integration: Consolidate, Coexist or Migrate in Stages?

> Separate consolidation or coexistence from the migration route. Compare one process, resolve dependencies and plan owner-reviewed integration steps.

Source: https://grandrounds.tech/insights/post-merger-it-integration · Published 2026-11-09 · CTO Grand Rounds

In post-merger IT integration, two choices get mixed up. **Consolidate or coexist** is the end state: one system, or two systems with agreed handoffs. **Migrating in stages** is the route to an end state. Compare options for one business process, using the same output, period and continuity needs, and include retaining the present arrangement. Only then fix the sequence.

A common platform can cut duplicated administration and interfaces. Mixed operation during a staged move can add routing, reconciliation and double support. Which effect dominates depends on the process, so compare at the process boundary.

**What you leave with:** one dependency, cost and continuity record per option, an owner for each open question, and a proposed first change with review criteria.

*Figure: Two separate choices: end state as one system or two systems with handoffs; transition route as one move or bounded stages.*

## Consolidate, coexist or migrate in stages: what are you choosing?

Separate the desired end state from its transition route. Consolidation reduces systems; coexistence retains owned handoffs; staging is a way to reach either. Include the present arrangement in the comparison.

## When the end states and routes tend to fit

- **Consolidate** when the process is the same in both businesses, one owner can run the result, retiring the old service is in scope, and contracts and run costs over the same horizon do not favor keeping both.
- **Coexist** when definitions, contracts or controls differ, or separation may be needed later. For Microsoft Entra tenants, Microsoft's guidance below gives future separation as a reason to keep tenants apart. Set a review condition instead of a retirement date.
- **Stage the move** when the process can be split into bounded populations or steps that each have an owner and a way to review the effect. Check shared dependencies at each step.

These are editorial rules of thumb, not a validated test. Record the evidence that supports or contradicts them in the matrix.

## Use a dependency, cost and continuity matrix

Hold the output, process, period and continuity needs constant across options, including retained services and when each option would retire or change a dependency. Ask the relevant owner for the definitions, access, vendor terms, service agreements and operating capacity that constrain it.

| Record field | Information to agree |
| --- | --- |
| Candidate/end state/route | Same process, output, period and continuity boundary |
| Dependencies | Systems, definitions, identifiers, contracts and permitted access |
| Cost assumptions | Change effort, mixed operation, support, licenses, exit and unknowns |
| Continuity/fallback | Affected users, operational support, interruption and restoration evidence |
| Decision | Required approvals, owner of each unknown, first step and review point |

Record setup/change work, mixed operation, reconciliation, support, contract/exit constraints and uncertain costs. Finance approves economic assumptions; operations accepts continuity; qualified owners keep their reserved decisions.

## Invented example: identity and email across two tenants

**Invented, unperformed editorial example.**

Two businesses share a brand after an acquisition but run separate identity and email setups. The process boundary is "staff sign in and receive group mail on the shared domain". Microsoft's cloud adoption guidance notes that a custom domain name can be associated with only one Entra tenant at a time, that consolidation is typically preferred in acquisitions, and that leaving tenants separate for an extended period is also common because consolidation is complex.

| Option | Dependencies and continuity | Cost and ownership questions |
| --- | --- | --- |
| Retain present arrangement | Two sign-in routes and two mail domains stay; the shared-domain requirement is not met | Record support effort, license duplication and user friction; name the owner of the review date |
| Coexist with agreed handoffs | Directory visibility or sharing rules between setups do not by themselves meet the shared-domain requirement; record that gap | Estimate setup and support; name who owns exceptions, access and any changed requirement |
| Coexist, built in stages | Set up one handoff at a time between the two setups, retaining the shared-domain gap until its owner resolves it | Name who owns each exception and the review date |
| Consolidate in stages | Move one population, check sign-in and mail flow, then decide on the next. A custom domain can sit in only one tenant at a time; decide how the second population's mail is handled during the move | Include retirement of the old service, license terms and the receiving support owner |
| Consolidate in one move | Cut-over of all users and the domain | Test whether a fallback is feasible; after mail and access have changed, a technical rollback may not restore the prior state |

For this boundary, a required shared custom domain points toward consolidation of that identity/mail arrangement; population-based stages are a route to evaluate, not an automatically safer choice. The domain constraint alone does not decide which other systems to merge. If the shared-domain requirement is removed, or a later separation is plausible, coexistence stays in the comparison. The owners use this record for the decision.

Source: Microsoft, [Scenarios for multiple Microsoft Entra tenants](https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/design-area/multi-tenant/scenarios) (Cloud Adoption Framework, updated 19 December 2025). The option table is editorial, not Microsoft's implementation recommendation.

## Post-merger IT integration steps for one process

1. **Resolve the choice-changing unknown.** Name the evidence, its owner and when the sponsor reconsiders options.
2. **Define the bounded change.** State users or records affected, the delivery team, permitted access and what stays unchanged.
3. **Agree checks before execution.** Name reconciliation, operational checks, exceptions and receiving reviewers; those owners set samples and tolerances.
4. **Review evidence and decide.** Record observations separately from acceptance. A demonstration does not authorize a wider rollout.
5. **Decide what can retire.** Confirm downstream users, retention, contracts, support ownership and authorized exit steps before removing the old arrangement.

This is an editorial sequence of decisions, not a validated method or calendar. Durations depend on the process.

*Figure: Four steps: resolve the choice-changing unknown, define bounded work and checks, record observations separately from acceptance, and have receiving owners review evidence. The next wave is separately authorized.*

**Your next action:** bring the option records to the sponsor, CIO, finance and receiving business owners. If there is no shared inventory yet, start with [who owns the combined technology decisions](https://grandrounds.tech/insights/post-acquisition-tech-decisions). If the gap is authority rather than analysis, read [who should hold the integration mandate](https://grandrounds.tech/insights/interim-cto-post-acquisition).

If you want a senior outside view of that bounded technical choice, [talk with the Grand Rounds curator](https://grandrounds.tech/talk-with-the-curator). The curator guides the conversation from the first introduction through setting up work with a CTO and follow-up support. Describe the decision and your role using a permitted nonconfidential summary.

## Boundaries

This page frames a technical decision for one process. Finance owns economic assumptions and deal valuation; legal, procurement and security own their approvals. Delivery is by your team or a provider you select. A Grand Rounds CTO's stated experience can inform the discussion. If your CIO and vendor already have the evidence, authority and a workable plan, another leadership appointment may add little.

Grand Rounds is an initiative of Dinarys, and a conversation may lead to cooperation with Dinarys.

## Questions and answers

### Is staged migration an alternative to consolidating?

Consolidating or coexisting describes where you end up; staging describes how you get there. You can consolidate in stages, or use staged changes to set up a lasting coexistence.

### Can keeping two systems be the right answer?

Yes. Microsoft's guidance for Entra tenants says that after an acquisition tenants are sometimes left separate for an extended or indefinite period because consolidating is complex. Set an owner for the interface, the exceptions and the running cost, and a review condition.

### Does a phased plan reduce risk by default?

Smaller steps limit exposure, but mixed operation adds routing, reconciliation and duplicate support, and a step can still break a shared dependency.

### What should we compare first?

One output for one process, over the same period and with the same continuity needs, including the current vendor's supported options and the current arrangement. Keep an unpriced item’s cost explicitly unknown.

### Who decides?

Decision rights are covered in [who owns the combined technology decisions](https://grandrounds.tech/insights/post-acquisition-tech-decisions). In short: the sponsor resolves priority conflicts within their authority, business owners judge whether the process works, and legal, procurement and security approve their own areas.
