Home » Resource Library » M&A IT Integration and Carve-Out Readiness Checklist

Free technical checklist

M&A IT Integration and Carve-Out Readiness Checklist

What to establish before signing, what has to work on Day 1, and the carve-out traps that surface late.

  • 72 verifiable checks
  • 16 cited sources
  • 80 KB PDF
Get the document Read a section first

What this is

IT is rarely the reason a deal is done and frequently the reason it is painful. Tenant to tenant migration has ordering constraints that are not obvious, licenses do not move between tenants, and a carve-out has to separate things that were never built to be separable. This checklist covers thirteen areas from pre-close discovery to post-close operations, with the Microsoft sequencing constraints stated explicitly rather than discovered during a cutover weekend.

Who it is for: Corporate development, integration leads, CIOs and IT directors working a merger, an acquisition, a divestiture or a carve-out where Microsoft 365 and Azure estates have to combine or separate.

What is inside

  • Thirteen areas from pre-close discovery through post-close operations
  • The Microsoft tenant to tenant sequencing constraints, cited to Microsoft Learn
  • A Day 1 continuity list separating what must work from what can wait
  • Carve-out specific traps that do not appear in a merger checklist
  • Transitional service agreement questions IT should answer before the TSA is signed
  • Space to record owner, status and date against each item

Contents

  1. Domain 1. Pre-close discovery 6 items
  2. Domain 2. Identity and directory 6 items
  3. Domain 3. Microsoft 365 tenant strategy 6 items
  4. Domain 4. Endpoints and devices 5 items
  5. Domain 5. Networking and connectivity 5 items
  6. Domain 6. Applications and licensing 6 items
  7. Domain 7. Data migration 6 items
  8. Domain 8. Security posture 5 items
  9. Domain 9. Day 1 continuity 6 items
  10. Domain 10. Transitional service agreements 5 items
  11. Domain 11. Carve-out specific risks 6 items
  12. Domain 12. Governance and decision rights 5 items
  13. Domain 13. Post-close operations 5 items

Read a section before you decide

This is the whole of "Domain 3. Microsoft 365 tenant strategy" as it appears in the document, not a sample rewritten for the web.

Domain 3. Microsoft 365 tenant strategy

How the two tenants relate, and in what order their contents move.

  1. The tenant end state is chosen deliberately: consolidate, coexist, or operate as a multitenant organization.

    Why it matters Consolidation is the most work and the cleanest outcome. Coexistence is faster and leaves permanent complexity. Choosing by default is choosing coexistence.

    How to verify A written decision with the reasoning, approved by someone who owns the consequences of the ongoing operating cost.

    Microsoft documented. Sources are cited in the document.

  2. Licenses are purchased in the target tenant. They are not transferred.

    Why it matters Microsoft states that licenses cannot be moved between tenants. Every migration plan that assumes otherwise has a hole in its budget.

    How to verify Confirm target tenant license procurement is in the plan and the budget, with the timing set against the migration schedule rather than close.

    Microsoft documented. Sources are cited in the document.

  3. Mailboxes migrate before or alongside Teams content, not after.

    Why it matters Microsoft documents that Teams chat and channel content depends on Exchange Online mailboxes, which sets the ordering. Moving Teams first produces content with nothing underneath it.

    How to verify Check the runbook sequence explicitly. This is one of the ordering errors that is only discovered at execution.

    Microsoft documented. Sources are cited in the document.

  4. OneDrive and SharePoint are migrated together.

    Why it matters Microsoft documents that they share a permissions model, so separating them in the schedule risks inconsistent permissions between content that references itself.

    How to verify Confirm the schedule keeps them in the same wave for a given population.

    Microsoft documented. Sources are cited in the document.

  5. Migration tooling is chosen and its limits understood before the plan is committed.

    Why it matters Native and third party tools differ in what fidelity they preserve. Discovering that a tool does not carry something you needed is a discovery best made before the schedule is published.

    How to verify Review the migration orchestrator and the alternatives against the specific fidelity requirements, particularly version history, permissions and metadata.

    Microsoft documented. Sources are cited in the document.

  6. A pilot wave of real users is run before the first large wave.

    Why it matters The problems in a migration are specific to the estate, and no amount of planning finds them as quickly as twenty real users with real content and real complaints.

    How to verify Confirm the pilot is a genuine cross section rather than the IT team, who have unrepresentative content and unrepresentative patience.

    Simplicity IT delivery practice, not a documented product behavior.

Download your free copy

Get the complete document below. No registration is needed.

Download M&A IT Integration and Carve-Out Checklist (PDF, 80 KB)

Discuss your results with Simplicity IT

Related work