Key takeaway
A new owner, a new licensee and a new user are different events. Trace each against the actual agreement rather than relying on the acquisition announcement.
Separate the transaction from the grant
A buyer acquiring a business may expect its data license to move with the business. An operating team may also start sharing licensed files with the new parent before anyone reviews the agreement. These are separate questions: which legal person holds the contract, whether rights or obligations are transferred, whether a control event triggers a clause, and which people may access the material.
The UK government’s Model Services Contract illustrates the distinction. Its assignment/novation clause addresses supplier transfers subject to the authority’s prior written consent and gives the authority different routes; supplier change-of-control notification is separately addressed. This is an asymmetric public-services model, not the rule for a private dataset acquisition. Read the transaction’s actual agreement and governing law.
Build an entity map before asking whether the data can move. Use registered legal names and identifiers, rather than a brand or domain. A finance team paying an invoice, an affiliate owning shares and a company holding the licensed grant need not be the same person.
Worked example: four changes to the same license
In this hypothetical license, Harbor Analytics Ltd, entity H-101, is the sole named recipient. The fictional terms require prior written consent to assignment, require notification of a specified change of control, and do not include automatic affiliate use. No real agreement is being described. The deal lead completes the following map before authorizing a migration.
The assumptions about entity continuity are facts entered for these fictional scenarios, not conclusions about the legal effect of a real share sale or merger. Counsel must verify the actual transaction documents, local law and relevant contractual triggers.
| Hypothetical event | Entity/access fact recorded | Required review under assumed terms |
|---|---|---|
| Parent acquires Harbor's shares | H-101 remains the licensed entity; parent P-300 becomes owner | Review defined change-of-control trigger and notification; no new parent access inferred |
| Operating assets sold to Quay AI Ltd | Q-202 would operate the product and hold a copy | Assignment/novation or new license review; Q-202 is not the existing named recipient |
| Harbor merges into another entity | Whether H-101 continues and who succeeds to obligations is unresolved | Hold migration; obtain transaction-specific legal analysis |
| Brand and payment address change only | Assume H-101 remains, but proposed billing party differs | Verify identity and payment mechanics; do not silently rewrite the grant |
Check access separately from contract transfer
In the hypothetical share acquisition, the parent asks its group engineering team to ingest Harbor's archive into a common platform. The licensed legal person may still be H-101, but the intended users and environment have changed. The entity-continuity row therefore cannot authorize the platform migration on its own.
The completed access row identifies the group operator, legal entity employing the users, storage location, onward access and intended product purpose. If a supplier is providing services rather than receiving an independent use right, document that arrangement and its constraints for the appropriate review. Do not treat every group company as internal merely because it uses one login system.
For the hypothetical asset sale, Q-202 needs an explicit route to the relevant rights and obligations. Copying the raw package before obtaining the required consent would bypass the very decision the entity map was created to expose. The migration owner holds the copy while the contract and permission route are resolved.
Carry evidence and obligations through the proposed transfer
A transfer discussion needs more than the original signature page. Assemble amendments, package identifiers, notices, exclusions, approved users, sublicensing provisions, confidentiality terms and any continuing delivery or correction duties. Record which party will perform each duty after the event and which creditor or counterparty must agree.
For its own model, government buyer guidance separately discusses IPR-license transfers and an exception for standard commercial software governed by vendor terms. It is another reason to list each underlying permission rather than treating the main services contract as the entire rights chain; it supplies no private dataset transfer entitlement.
In this hypothetical asset sale, Harbor has delivered one restricted snapshot and still owes a correction under its agreement. The transfer proposal assigns a person to identify the affected artifact and seeks a reviewed arrangement for the continuing obligation. A purchase agreement saying assets include data is not used as a substitute for that license review.
Also check the seller-side rights chain. If the licensor itself changes or a database asset moves, the relevant grantor and supporting permissions need review. This article does not decide the underlying ownership transfer. The point is to keep contract, entity, access and rights evidence connected rather than letting a corporate closing erase the operational record.
Make closing conditions useful to the migration team
The completed hypothetical decision allows Harbor to update its verified billing contact while holding group-platform access and the Q-202 asset migration. The merger row remains unresolved. The record names the exact consent or legal analysis required, its owner, and the system action that must wait. This gives the deal team concrete work instead of a broad request to check the contracts.
Use offer comparison to retain transfer and control-trigger differences, and due diligence to verify the proposed recipient's identity and operation. The ownership guide concerns who can grant rights; this map concerns how a corporate event changes an existing grant and its access conditions. A new location may also require the separate transfer-recipient review.
VOID's earlier permission for a named-recipient introduction is not permission to introduce or disclose material to every acquirer's affiliate. A new recipient or sample request needs its own decision. Conditional receiving-program compensation and the absence of an upfront seller referral fee do not alter the owner's control over that disclosure boundary.