Skip to content

Est. 2011·Microsoft Partner ID 7033487·Delivery under 3 min·Support 7 days a week

Your vault is empty.

Review

Merging Two Companies’ Software: Consolidating Licences After a Deal

13 min read Updated October 5, 2026 Buying & Decision Guides

Fix it now

Deal structure decides what you own before technology decides anything. Get that answered in writing, then inventory both estates twice – entitlement and deployment – because the gap between them is the same gap a reviewer would find. One tenant is the usual destination, and the domain move is a hard cutover because a domain name can only be verified in one directory.

  1. Establish what transferred. Where the legal entity survives, its agreements generally survive with it; in an asset purchase, licences held by that entity do not automatically travel. Confirm it with whoever handled the transaction before your inventory drives any purchasing.
  2. Collect entitlement from the right place on both sides. Volume licensing records moved to the Microsoft 365 admin center when the Volume Licensing Service Center was retired in April 2024 – Billing, then Your products, then the Volume licensing tab.
  3. Provision and licence accounts in the destination tenant before migrating anything into them. Microsoft’s own guidance is to make sure sufficient licences are available in the target tenant before migration.
  4. Sequence the workloads: migrate mailboxes before or alongside Teams, because Teams content depends on Exchange mailboxes, and migrate OneDrive and SharePoint together because they share a permissions model.
  5. Cancel nothing at the source until the data is verified. A lapsed subscription bought directly runs 30 days Expired then 90 days Disabled, and then the data is deleted and the directory removed.
  6. Recount CALs afterwards. More people reaching the surviving servers means more CALs, and the CAL version must match the newest server in the combined estate.

This is a licensing article, not legal advice. Volume licensing agreements are not uniform on assignment, so whoever handled the transaction should confirm what transferred before the inventory is used to make purchasing decisions.

If you know which entity holds what and which tenant survives, the rest is a project plan. Below is the inventory to build on both sides, the domain cutover in the documented order, and the contracts that rarely merge cleanly.

Why it happens

Two software estates do not merge by themselves, and the licensing questions arrive earlier than the technical ones. In a share purchase the acquired company continues to exist, so its agreements, subscriptions and OEM licences usually continue with it. In an asset purchase the legal entity is left behind, and licences held by that entity do not automatically come with the assets. Microsoft does not publish a single rule that covers every agreement, which is why this belongs to whoever handled the transaction rather than to IT.

Two categories behave differently enough to separate early. OEM licences are attached to hardware – the terms permit transferring the licence to another user only with the licensed device – so they travel with the machines if the machines transfer. Subscriptions are attached to a tenant and a billing relationship, so they follow whoever holds that relationship, which may not be whoever ends up using them.

On the technical side, one constraint shapes the whole plan: a domain name can only be verified in one Microsoft Entra directory, and if it is currently verified in another directory it cannot also be verified in the new one. That makes the domain move a hard cutover rather than a gradual one, and it means the overlap period has to be planned around mail routing instead. Microsoft’s own tenant-to-tenant guidance covers this coexistence explicitly, including mail routing between tenants, calendar free/busy sharing and Teams federation during the transition.

Nobody knows what transferred

You have this one if Two IT teams comparing inventories while the deal documents sit with the lawyers.

  1. Stop and get the structure confirmed in writing. Share purchase and asset purchase produce different answers for the same estate.
  2. Ask specifically about assignment provisions in each volume licensing agreement, because they vary and are not published as a general rule.
  3. Until that answer exists, treat both estates as separately licensed and do not consolidate purchases on an assumption.

Two tenants and one domain

You have this one if Both companies use the same trading domain, or the domain needs to move to the surviving tenant.

  1. Clear the domain from the source tenant first. Microsoft’s checklist is specific: it must not be the default domain, no users, shared mailboxes, resource mailboxes or contacts may use it, no Microsoft 365 groups, distribution lists or teams may use it, and it must not be used for admin sign-in.
  2. Understand how mail flow changes if the domain has MX records pointing to Microsoft 365, before you move it rather than afterwards.
  3. Plan the overlap on mail routing and free/busy sharing between the two tenants, because the domain itself cannot be shared.

The source tenant is cancelled too early

You have this one if An instinct to save a month’s billing while the migration is still being verified.

  1. Do not. A subscription bought directly runs 30 days Expired, then 90 days Disabled, and then the data is deleted and the Microsoft Entra ID directory is removed.
  2. Check which lifecycle applies: as of 9 February 2026 the Expired state no longer applies to licence-based subscriptions bought directly through a Microsoft Customer Agreement, so that cushion may not exist.
  3. Run both mail paths through a defined overlap and cancel only after a full clean week with named users confirming rather than a report confirming.

Overlapping antivirus and backup contracts

You have this one if Two products, two consoles, two renewal dates and two notice periods.

  1. Choose one product and plan the removal properly, including releasing seats in the console rather than only uninstalling the agent.
  2. Run both to the earlier of the two end dates rather than paying twice or breaching a notice clause, and check the notice period in each contract before deciding.
  3. Where the surviving product is Microsoft’s, check what the plans already include before renewing anything – Business Premium carries Defender for Business, Defender for Office 365 Plan 1, Entra ID P1 and full Intune capabilities.

Full reference

Two inventories, then one reconciliation

Estate item Collect from both sides The question it answers
Volume agreements Agreement numbers and exports from the Microsoft 365 admin center under Billing, Your products, Volume licensing Which agreement survives, and whether it can be assigned
Microsoft 365 Tenant names, purchased against assigned seats, plan mix, purchase channel and term Which tenant is the destination, and how many seats you really need
Domains Every verified custom domain in each tenant The order and timing of the cutover
Windows Edition and activation channel per device, read with slmgr /dli Whether volume Windows sits on qualifying base licences
Servers Physical cores, sockets, host and guest counts, editions Whether either side is under-licensed today
CALs Quantities, versions, user or device The post-merger recount against the newest server
Office Perpetual against subscription, and per device counts What can be retired and what must be preserved
Antivirus and backup Products, seat counts, end dates, notice periods Which contract to keep, and when you can leave the other
Line-of-business software Licence terms and the entity named on them Which vendors must consent to a transfer
Records Invoices, hardware purchase records, agreement paperwork Whether either estate can prove what it holds

Choosing the destination tenant

The destination is usually the tenant that is better configured, better licensed or simply larger, and the decision should be made on those grounds rather than on whose brand survives. A third, new tenant is occasionally proposed and almost always doubles the work, because everything migrates twice and nothing is already correct.

Accept in advance that the tenant’s underlying technical name may not match the trading name you keep. That initial domain is effectively permanent, it appears in very few places users ever see, and it is not worth a second migration on its own.

A cutover order that does not lose mail

  1. Agree a date and freeze non-essential changes on both sides, including new user creation.
  2. Provision and licence the accounts in the destination tenant before migrating anything into them – Microsoft’s guidance is explicit that sufficient licences must be available in the target tenant before migration.
  3. Migrate in dependency order: mailboxes before or alongside Teams, because Teams content depends on Exchange mailboxes; OneDrive and SharePoint together, because they share a permissions model.
  4. Run a delta pass, then verify with named users opening real content rather than with a completion report.
  5. Clear the domain from the source tenant against Microsoft’s checklist: not the default domain, no users, shared mailboxes, resource mailboxes or contacts using it, no groups, distribution lists or teams using it, and not used for admin sign-in.
  6. Add and verify the domain in the destination tenant, switch primary addresses, then change the public DNS records.
  7. Run both mail paths through a defined overlap period so anything misrouted is visible while it can still be fixed.
  8. Only after a full clean week, cancel the source subscriptions.

Do not cancel the source subscriptions to save a month’s billing while the migration is still being verified. A subscription bought directly runs 30 days Expired then 90 days Disabled, after which the data is deleted and the Microsoft Entra ID directory is removed – and as of 9 February 2026 the Expired state no longer applies to licence-based subscriptions bought directly through a Microsoft Customer Agreement, so the window may be shorter than you expect. The month you save is never worth the mailbox you lose.

What the merger does to the on-premises side

Two things change and both are easy to miss. More people and more devices reach whichever servers survive, so the CAL count goes up – and CALs are version-bound, meaning the newest server version in the combined estate sets the CAL version for everybody reaching it. A Windows Server 2025 CAL permits access to 2025 and prior versions; an older CAL does not reach a newer server. Merging two estates with different server generations is therefore a CAL purchase even when headcount is unchanged.

Reassignment is the second. Under the Universal License Terms a licence may be reassigned to another device or user not less than 90 days since the last reassignment of that same licence, with published exceptions for permanent hardware failure or loss and for a user whose employment or contract has ended. That exception covers the redundancies a merger usually produces, but not a general reshuffle of licences between two populations.

Contracts that rarely merge cleanly

  • Antivirus and backup: choose one product, plan the removal, and run both to the earlier end date rather than paying twice or breaching notice.
  • Annual subscription commitments: these run to the end of their term. The cancellation window is seven calendar days from purchase and does not reopen until renewal, so plan the consolidation around the end dates rather than assuming surplus can be shed immediately.
  • Anything you intend to keep: co-terminate it onto one anniversary, remembering that an annual or three-year term cannot be co-terminated with a monthly one.
  • Line-of-business software: read the entity named on the licence and ask the vendor about assignment before assuming it comes with the assets.
  • Software Assurance on products where lapsing removes the right to run the software, such as Exchange Server SE and SharePoint Server Subscription Edition.

Which approach to take, by situation

  • Two small estates, one clearly better run: migrate into the better one and keep its agreements.
  • Similar size, both untidy: still choose one. Building a third tenant to be fair to both multiplies the work without improving the result.
  • Regulated or residency-sensitive data on one side: check the commitments on both tenants before choosing the destination, not afterwards.
  • Long notice periods on antivirus or backup: run both to the earlier end date rather than paying twice.
  • Still in diligence: build the two inventories now. They are the compliance evidence as well as the migration plan, and the buyer will ask for them regardless.

When a licence is the actual fix

Consolidation is usually where the money appears, because two estates almost always carry duplicate seats, overlapping security products and licences still assigned to people who left before completion. Standardising the combined company on Microsoft 365 Business Premium collapses several of those lines into one seat with one renewal date – device management, conditional access, endpoint protection and mail filtering included. Arco can price the combined headcount, check which of the two agreements can carry forward, and align the renewal dates as part of the move. The largest single saving is usually reclaiming duplicate and unassigned seats, and that costs nothing at all.

Questions people ask about this

Can we simply transfer the other company’s licences to ourselves?

It depends on the deal structure and on the assignment provisions in the agreements concerned, and Microsoft does not publish a single rule that covers them all. Where the legal entity survives, its licences generally survive with it. Where assets were purchased, the entity holding the licences was left behind. Confirm it with whoever handled the transaction before your inventory drives any purchase.

Can two tenants share the same domain during the migration?

No. Microsoft states that a domain name can only be verified in one directory, and if it is currently verified in another directory it cannot also be verified in the new one. That makes the domain move a hard cutover, and the overlap has to be planned around mail routing, free/busy sharing and Teams federation instead.

What has to be cleared before a domain can leave a tenant?

Microsoft’s checklist: it must not be the default domain; no users, shared mailboxes, resource mailboxes or contacts may use it; no Microsoft 365 groups, distribution lists or teams may use it; and it must not be used for sign-in by any admin account. You also need to understand how mail flow changes if the domain has MX records pointing to Microsoft 365.

When is it safe to cancel the source subscriptions?

After a full clean week of verified operation in the destination, not before. A subscription bought directly runs 30 days Expired then 90 days Disabled, and then the data is deleted and the Microsoft Entra ID directory is removed. As of 9 February 2026 the Expired state no longer applies to licence-based subscriptions bought directly through a Microsoft Customer Agreement, so check which lifecycle yours follows.

What happens to seats we no longer need?

It depends on the term. Monthly commitments can be reduced quickly. Annual commitments generally run to the end of their term, because the cancellation window is seven calendar days from purchase and does not reopen until the subscription renews. Plan the consolidation around those end dates rather than assuming the surplus can be shed immediately.

Do we have to recount CALs after a merger?

Yes, and it is easily missed. Merging directories means more users and devices reaching whichever servers survive, and CALs are version-bound: a Windows Server 2025 CAL permits access to 2025 and prior versions, while an older CAL does not reach a newer server. So the newest server in the combined estate sets the CAL version for everybody, even when total headcount has not changed.

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Review On-Prem Exchange SE or Microsoft 365: Choosing Where Your Email Lives Review Cyber Essentials and Insurers: The Licences Compliance Quietly Requires Review Where to Buy Licences: Reseller, Marketplace or Straight From Microsoft Review Moving From Perpetual to Subscription: What You Gain and What You Lose
← Back to Knowledge Base