How do you transfer Microsoft licenses to a new entity?

Microsoft licenses can be moved during a reorganization, but you must first separate a legal transfer of rights, an account details update, a subscription move between partners, and a data migration between tenants. Teams often combine these operations in one request, then wonder why the supplier asks for another document set, the administrator cannot move the domain, and finance receives two bills for the same month.

The main rule is simple: the party to the agreement owns or uses the license, not the familiar company name in the admin portal. If the same legal entity remains after a name change, the work normally concerns updating account details. If a new legal entity appears, you cannot assume that rights moved merely because the employees, computers, and domain stayed the same.

I start these projects with the agreement, purchase channel, and reorganization structure, not with buttons in Microsoft 365. The technical plan comes after the team identifies who was the customer before the event and who will be the customer afterward. Otherwise, the team may move the mail perfectly while leaving the new company entitled to use only trial or newly purchased licenses.

First establish who remains party to the agreement

If the business registration number and legal entity remain the same while the name, address, or bank details change, licenses normally are not being transferred to a new owner because the customer remains the same. Update the legal profile, billing details, and seller records, and check whether the change will trigger account reverification. Editing the tenant display name does not replace this work.

An absorption, merger, spin-off, business unit sale, or asset transfer has a different result. The documents identify a successor or a separate buyer, and its right to use the software must rest on the terms of the specific agreement. A reorganization decision under Kazakhstan law explains what happened to the companies, but it does not rewrite the Microsoft agreement contrary to its restrictions.

Record four identifiers before contacting any supplier: the full name of the agreement party, its business registration number, the agreement or account number, and the Microsoft Entra tenant ID. They answer different questions. The business number identifies the legal entity, the agreement number ties purchases to terms, and the tenant ID identifies the technical environment. A match on one identifier does not prove that the others match.

Do not confuse a company in the corporate group with an Affiliate under a Microsoft agreement. Microsoft volume licensing guidance connects Affiliate status to ownership or control of more than 50 percent, but you must apply the definition in your active agreement. A shared brand, a common director, or a services contract does not by itself allow a second company to deploy the first company’s licenses.

Use a practical test. If an auditor saw only the purchase agreement and the new organization’s registration extract tomorrow, could that person connect the right of use to the new business registration number without an oral explanation? If not, the project needs a transfer document, evidence of succession, a new order, or a written decision from Microsoft and the seller. An admin portal screenshot does not fill that gap.

Check separately when the former party ceases to exist or loses control of the transferred unit. The registration date of the reorganization, the date of the transfer deed, and the actual system cutover date may differ. The licensing plan must explain the basis on which both organizations use the software during the transition. A silent assumption that one month of parallel operation is automatically allowed creates a double-use risk.

Create a short decision map for each agreement: the party before the event, the party afterward, the basis for continuation or transfer, the required approval, and the date when old use stops. Legal, procurement, and the technical lead should sign this map. It does not replace contractual documents, but it stops three teams from working from three different versions of the reorganization.

The purchase channel matters more than the product name

Transfer rules come from the channel and agreement used for the purchase, not from the product logo. Two copies of the same Windows Server edition can carry different restrictions if one came as OEM software with a server, another is a perpetual volume license, and a third is available by subscription.

Sort purchases into at least five buckets:

• perpetual licenses under volume programs and Software Assurance;
• Microsoft 365, Dynamics 365, and similar per-user cloud subscriptions;
• subscriptions and perpetual software purchased through CSP;
• OEM licenses supplied with a computer or server;
• retail copies and separate digital purchases.

Do not reach a conclusion from an activation key. One key can cover several permitted installations, while successful activation proves that the mechanism works, not that the new legal entity has a right to use the product. The review needs the agreement, order, invoice, license statement, and applicable product terms.

The inventory must connect commercial and technical data in the same row. I use this CSV template and do not let the team enter Microsoft in the channel column because that tells us nothing:

asset_id,product,edition,version,metric,quantity,purchase_channel,agreement_or_order,legal_owner,tenant_id,assigned_device_or_user,sa_end,renewal_date,target_action,evidence_owner
SRV-014,Windows Server,Datacenter,2022,cores,32,Volume,MPSA-0000,Old LLP,,Server-014,2026-11-30,,transfer,Legal
USR-001,Microsoft 365,E3,current,user,1,CSP,NCE-0000,Old LLP,11111111-1111-1111-1111-111111111111,[email protected],,2026-10-15,replace-and-migrate,IT
PC-233,Windows,Pro,11,device,1,OEM,INV-0000,Old LLP,,PC-233,,,move-with-device,Procurement

The target_action and evidence_owner fields force a decision for every item and assign the person who will find the evidence. Values such as keep, transfer, replace-and-migrate, move-with-device, and retire say more than a general in progress status. After the first reconciliation, separate products with no agreement or invoice because a reorganization does not fix an old evidence gap.

Reconcile the register against three independent sources: accounting records, licensing portals, and actual deployments. Accounting shows what the organization paid for, the portal shows available rights and subscriptions, and environment scanning shows what is used. Expect discrepancies. A server might have been retired while the perpetual right remains, or an application might have been installed from an image even though the selected company has no purchase evidence.

The product metric matters as much as the quantity. For a server product, the number of installations does not answer whether licenses cover cores, virtual machines, or user access. For a cloud service, the number of purchased seats does not show who has add-ons. Do not combine different metrics in one total licenses column. That total is convenient for a presentation and useless for a transfer decision.

Transfer perpetual volume licenses with the proper form

Fully paid perpetual volume licenses may be transferred only in the scenarios and under the conditions allowed by the applicable agreement. Microsoft Product Terms and transfer forms take a narrow approach: a transfer is generally allowed to an affiliate, or to a third party with assigned equipment or employees in a divestiture or merger. This is not a general right to sell spare licenses to any company in the group.

Microsoft publishes a Perpetual License Transfer Form for several regions, including EMEA, in its Licensing Documents collection. It is useful because it shows the process, not merely the general restriction: the transferor and transferee list agreements and licenses, confirm the basis for the transfer, and accept the terms. The form version, region, and submission route still need to match your agreement. Do not sign an old file from a colleague’s archive without checking it.

Transfer the license as the unit permitted by the agreement. You cannot separate package components, upgrade rights, or a portion of a license as if they were independent assets. If a license is assigned to a server, user, or transferred business unit, the schedule must show that connection. In a partial spin-off, it is especially easy to move 40 employees and forget that a server license also supported the organization that remains.

After a valid transfer, the transferor must stop using the transferred copies and render remaining copies unusable when the agreement requires it. Put this action in the completion certificate: remove installations, revoke access to installation files and keys, update the CMDB, and close former administrator permissions. A signature without technical cessation leaves a duplicate deployment behind.

Software Assurance needs its own calendar. Microsoft Product Terms states that the recipient of a transferred perpetual license may acquire Software Assurance within 30 days of the transfer date if the transferor kept active coverage through that date. Missing this window can affect access to benefits and later renewal, so place the legal transfer date and SA expiration date next to each other in the plan.

Do not promise management that a form means automatic approval. The agreement owner or partner first checks whether the scenario qualifies, the parties then prepare the schedule and supporting records, and Microsoft or the authorized channel processes the request under the applicable procedure. Stricter agreement terms are not displaced by a general form.

Review OEM and retail licenses separately

An OEM license normally needs to be considered with the device on which it was supplied, so when computers move to the new organization, the right and its evidence should follow the specific assets. Leaving the computer with the old company while giving the new company a sticker, key, or spreadsheet entry breaks the relationship on which OEM licensing is based.

For every device, match the serial number, equipment invoice, delivered configuration, software edition, and actual recipient under the transfer deed. If a motherboard was replaced or a server was assembled from components, do not infer status from whether the system activates. Retrieve the OEM supplier terms and the license terms for that exact product version.

A retail license is not automatically a freely resalable corporate asset either. Some retail terms allow software to move to another device after removal from the old one, but that rule answers a device assignment question, not automatically a change of owning party. Legal counsel must review the specific purchase terms and whether a transfer with an asset or reorganization is permitted.

A digital link to an account creates another illusion. An administrator signs in with the old account and sees the product, so the team treats the matter as settled. The account only helps retrieve or activate a copy. The transfer record needs the source of the license, the original buyer, a permitted basis for the change, and cessation of use by the former party.

If evidence for old OEM and retail purchases cannot be recovered, budget to replace the disputed licenses instead of building the reorganization on keys of unknown origin. That does not mean buying everything again. First separate supported items from unsupported ones, then calculate only the actual gap.

Per-user subscriptions do not move like property

Microsoft 365 user subscriptions last for a term and are granted to the customer under an agreement, so they cannot be listed in a transfer deed as perpetual licenses. Assigning a license to another user in the same tenant, moving billing between partners, and creating a subscription for a new legal entity solve different problems.

For a simple rename of the same legal entity, you can often keep the tenant and subscriptions. The partner updates customer details, finance changes billing data, and the administrator checks the organization profile. Microsoft warns in Partner Center documentation that a details change can trigger reverification and temporarily block new purchases, seat increases, and upgrades. Do not change the records an hour before a mass license assignment.

If the new company will operate in a new tenant, old user assignments are not copied there. Establish the target organization’s relationship with the seller and Microsoft, purchase the appropriate subscriptions, create or synchronize accounts, and assign licenses. Then move data with separate methods for Exchange Online, OneDrive, SharePoint, Teams, and other workloads.

Microsoft expressly requires a separate Cross-Tenant User Data Migration license for the native cross-tenant mailbox move. Exchange Online base licenses must be assigned where the design requires them, and the target MailUser object must be prepared with the correct ExchangeGUID and addresses. If Exchange Online is assigned too early, before the correct ExchangeGUID is stamped, the target tenant can create a new empty mailbox that blocks the move.

Even the native cross-tenant process does not mean all of Microsoft 365 will move. Mail migration documentation lists separate limitations, including no Microsoft 365 Groups migration in that flow. Retention policies, labels, apps, guest relationships, devices, app registrations, and permissions need their own schedule. Every workload needs an owner, a migration method, and acceptance criteria.

Saving money on the overlap period causes the most trouble. The old subscription may still be needed to read source data or roll back, while the user already needs the new subscription in the destination. Budget for temporary duplicate licensing wherever the migration method needs it instead of hoping to delete the old seat that same evening.

A CSP partner transfer changes billing, not ownership

Moving a subscription from one CSP partner to another changes commercial servicing and billing ownership, but it does not by itself transfer license rights to another legal entity. The process helps when the customer stays the same and changes suppliers, or when a partner reorganizes its business. It does not replace onboarding a new customer after a spin-off.

For a new commerce subscription transfer, the target partner establishes a relationship with the customer, the customer accepts the Microsoft Customer Agreement, and the source partner must approve the request. Partner Center documentation says Microsoft will not override the transfer without the source partner’s consent. A dispute with the old supplier cannot be left until the week of cutover.

After a license-based subscription transfer, a new subscription with a new identifier is created under the target partner, while the term and certain commercial properties carry over under the process rules. Export the original IDs, renewal dates, seat counts, scheduled changes, and add-ons in advance, then match them to the result. Checking only the number of active users will miss a billing or automatic renewal error.

Do not confuse a partner change with a tenant move. In a normal partner transition, users and data stay in the same tenant, while the party that invoices and manages the subscription through the channel changes. If the legal entity and tenant also change, the project has three workstreams: contractual, partner, and technical. Each needs its own owner and completion evidence.

New commerce subscriptions also restrict cancellation and seat reductions. Partner Center rules give per-user licenses a seven-day window after purchase or renewal, after which the commitment continues to the term end. The idea of buying under the old entity now and rewriting it a month later can leave the organization with two commitments. Check the renewal date before the order, not after the invoice.

GSE.kz sells and integrates Microsoft software, so an integrator can bring the commercial and technical workstreams into one project plan. The transfer decision must still rest on the customer’s agreement and confirmation from the applicable channel, not on partner status alone.

Assemble the case file before contacting the supplier

A complete document package shortens correspondence because it lets the reviewer connect the event, parties, agreements, and specific licenses without guessing. Sending a single message saying that the legal entity changed and everything should be moved almost always leads to a series of questions.

Put the reorganization decision or agreement, transfer deed, registration extracts for both parties, business registration numbers, addresses, signatory details, and ownership structure in the legal section if Affiliate status is the basis. Add a one-page note stating what event occurs, on what date, which organization disappears or continues, and who receives the assets and employees.

The licensing section should contain agreement and order numbers, purchase exports, invoices and payment evidence, a product list with quantity and metric, Software Assurance and renewal dates, and the signed transfer form where applicable. Copy product names from the license evidence, not from the inventory of installed applications. An installation may not match the purchased version or edition right.

The technical section should include tenant and subscription IDs, verified domains, the user list, workload sizes and owners, emergency access accounts, applications with secrets and certificates, Intune managed devices, and single sign-on dependencies. Do not store secrets in the case file. Record the owner, secure storage location, and planned rotation date instead.

Assign one owner to the register, but do not assign one person to the entire project. Legal confirms the transfer basis, procurement confirms channel and payment, the partner handles the commercial operation, administrators prepare the tenants and migration, and data owners accept the result. A table without named owners quickly becomes a list of other people’s tasks.

Check names for consistency before submission. An old abbreviation on an invoice, the new full name in a registry extract, and a trading name in Partner Center may refer to the same company, but the reviewer should not have to infer that. A one-page mapping of names and business registration numbers resolves more questions than a long cover letter.

Add a question and answer log. For each request, record the date, recipient, exact wording, response, attachment, and resulting project decision. A partner’s comment during a phone call should not become the licensing basis. If the answer affects use rights or a payment obligation, ask for written confirmation tied to the agreement number.

Control file versions. The transfer deed after legal edits, the license table after procurement reconciliation, and the form sent to the partner often differ by several rows. Give the package a version number, snapshot date, and checksum, or keep it in a system with change history. The schedule submitted for processing must be the same one the parties sign.

Do not send personal data and secrets beyond what is needed. A user list normally needs a work identifier and required license unless a specific process requires more. Passwords, private keys, recovery codes, and mailbox contents are not licensing evidence. Keep the legal case file, technical working set, and restricted credentials at separate access levels.

Before filing the form, agree who can answer questions after the legal event date. If the former signatory, administrator, or procurement employee leaves on reorganization day, a simple request to correct an order number can stop at an inaccessible mailbox. Transfer authority, set up a shared project address, and keep evidence in the new organization’s archive.

Build the schedule backward from the legal event

Count time backward from the reorganization date, not forward from the day IT receives an internal memo. Contract review, new purchasing, account verification, domain transfer, and data migration have different dependencies, so a single shared deadline hides risk.

For a details update with no business registration number or tenant change, I reserve three to four weeks before the event. This is a working allowance for agreement reconciliation, profile updates, and possible reverification, not a Microsoft service commitment. If verification is not triggered, the team finishes early without losing anything.

For perpetual license transfers between legal entities, a reasonable internal allowance is six to eight weeks. During that time, the parties assemble the schedule, check the basis, agree the form, correct discrepancies, and confirm the submission route. Start a complex spin-off with several agreements even earlier, especially near a Software Assurance expiration.

A cross-tenant migration is a separate project. For a small, well-documented environment, I do not schedule cutover earlier than eight weeks after discovery begins. A large environment with mail, files, Teams, apps, Intune, and compliance policies can easily need twelve to sixteen weeks for inventory, a pilot, corrections, and phased moves. These are planning ranges for risk management, not a rule or Microsoft statistic.

The working sequence has seven control points:

1. Confirm the legal scenario and the effective date of the changes.
2. Freeze the source register of licenses, subscriptions, devices, and tenants.
3. Obtain the written route from the agreement owner or partner.
4. Establish the relationships and purchases the target company needs.
5. Run a pilot with users and data that have no exceptional requirements.
6. Perform cutover while retaining the agreed overlap period.
7. Sign off the reconciliation of rights, data, invoices, and cessation of old use.

Two calendar boundaries are fixed. One is the seven-day cancellation or seat reduction window for many new commerce subscriptions. The other is the 30-day period in which a recipient can acquire Software Assurance after a permitted perpetual license transfer when SA remained active through the transfer date. Put both dates in finance’s calendar, not only the administrator’s.

A tenant migration needs its own technical plan

A technical migration is needed only when the target company will use a different tenant or an architecture decision requires consolidation. A legal name change does not require a new tenant, and creating a new tenant does not document a rights transfer.

Start with an actual statement of subscriptions and assignments. Microsoft Graph PowerShell can retrieve purchased SKUs and user license details. The commands and result shape support a reproducible reconciliation:

Connect-MgGraph -Scopes Organization.Read.All,User.Read.All
Get-MgSubscribedSku | Select-Object SkuPartNumber,ConsumedUnits,@{n='Enabled';e={$_.PrepaidUnits.Enabled}}
Get-MgUserLicenseDetail -UserId [email protected] | Select-Object SkuPartNumber,SkuId

The expected table from the first command contains SkuPartNumber, ConsumedUnits, and Enabled; the second result links a user to SkuPartNumber and SkuId. Export the data with the date and tenant ID. After cutover, repeat the commands in the target environment and compare specific SKUs for a sample of users, not only the total seat count.

Do not treat a domain as an ordinary settings string. A custom domain must be removed from dependent objects in the source tenant before it can be verified in the target. Find accounts, groups, contacts, applications, and addresses that use it in advance. Otherwise, the cutover window will be spent searching for one forgotten reference.

For mail, prepare the target MailUser objects, identity mapping, migration scope, organization relationships, and migration endpoint. Pilot an ordinary mailbox, a large mailbox, a delegated mailbox, and one under legal hold if those cases exist. After the move, test mail flow in both directions, delegation, mobile clients, search, and eDiscovery requirements.

For OneDrive, SharePoint, and Teams, separately decide what happens to permissions, shared links, groups, private channels, applications, and meeting recordings. Saying that files will move is too narrow. A user may open a document but lose access to a form, workflow, or approval history. Acceptance criteria must describe a business operation, not the number of copied gigabytes.

Do not disable old accounts immediately after a successful sign-in to the new environment. First confirm mail routing, data access, license assignments, emergency admin accounts, logs, and user support. Then restrict the old environment under the approved plan, retaining only the access and duration needed for verification and compliance.

The rollback plan must distinguish data from identity. A mail batch can be stopped or repeated, but a domain already moved cannot be bounced painlessly between tenants during the workday. Set the last cancellation point for every step, the decision conditions, and the person authorized to stop cutover. Where reversal is technically impossible, document a fallback mode for users in advance.

Support during the first days needs a map of old and new user names, known limitations, and an escalation route. Reports about a missing calendar, inaccessible shared folder, or repeated sign-in prompt cannot sit in an ordinary queue for several days. Fast classification also helps distinguish a migration fault from a missing license and prevents random seat purchases.

Close the old organization only after reconciling rights

The project is complete when the new organization can prove its right of use, users receive the required services, invoices reach the correct party, and the former organization has stopped using transferred rights. A successful user sign-in proves only one of those outcomes.

Reconcile against the source register one row at a time. For a perpetual license, attach evidence of a permitted transfer and the new owner record. For OEM, connect the right to the transferred device. For a subscription, show the target party’s order, term, seat count, and assignment. For a retired item, record removal, key blocking, and closure of media access.

Finance reconciles the old party’s final invoice, the new party’s first invoice, refunds or credits, and renewal dates. The administrator reconciles SKUs, users, domains, and data status. Legal retains signed forms, decisions, and confirmations. Procurement updates supplier records and the renewal calendar. None of these checks replaces another.

Check access to portals and installation materials after staff changes. The new organization needs its own authorized accounts, and a former employee’s personal address must not remain the only way to retrieve a key or invoice. Assign at least two emergency access owners under the organization’s internal rules and test those accounts periodically.

Run another reconciliation after one full billing period. The first day after cutover proves service availability, but it will not expose an incorrect automatic renewal, an invoice to the old business number, or a subscription that retained excess seats. The repeat review closes the commercial tail of the project and lets finance release the reserve for duplicate payment.

Keep a decision log with the date, author, and basis. A year later, the question is usually not whether Office works, but why this company has rights to 240 seats and where the expiration date came from. The answer should be in the case file without reconstructing a former employee’s email.

Do not discard the original environment snapshot when the project closes. Retain the purchase and assignment exports from before the reorganization, the final register, form processing confirmations, reconciliation command results, and signed acceptance record. Set the retention period under the organization’s contractual, accounting, and internal requirements. This package shows the result and the path each license took from the former party to the new one.

Have someone outside the migration team perform a sample review. Select several users with different SKUs, a physical computer with OEM software, a server license, one transferred perpetual item, and the subscription closest to renewal. Ask for the unbroken document trail and actual status of every item. A sample quickly exposes a systemic error, such as the old business number on every order or missing cessation of use, without turning acceptance into a repeat of the entire project.

Record exceptions in a separate appendix to the completion record. State which item remains open, who temporarily owns the risk, what restriction applies, which document is pending, and when the issue returns for review. An exception with no owner or date nearly always becomes permanent. A signed list does not solve the problem, but it prevents the problem from disappearing from reporting when the project team disbands.

If some items remain disputed, do not hide them under a general transferred status. Restrict use, request written guidance from the channel, or buy replacements for the confirmed shortfall. A clean register with a small open gap is safer than a polished certificate that claims more than the documents support.