Seller field guide · 3 min read
Can you license company data after an acquisition?
An acquisition does not by itself establish that every acquired record can be licensed for AI use. First confirm what rights transferred, which restrictions continue, and who can authorize the proposed transaction. Keep acquired and legacy records distinguishable while that review is incomplete.
Separate ownership from permitted use
The UK ICO identifies original collection purposes, lawful sharing and changed responsibilities as acquisition due-diligence questions. That is UK guidance, currently marked as under review, rather than a rule covering every transaction worldwide. Ask qualified counsel to assess the agreements and jurisdictions relevant to your own acquisition.
For the operating team, the practical task is to assemble evidence. Identify whether the archive was included in the transaction, which entity now controls it, and whether customer, supplier, employee or software terms limit reuse. Possessing an exported drive is not an answer to any of those questions.
Source notes: ICO: data-sharing diligence after mergers and acquisitions (UK)
Build a provenance register before combining systems
Maintain separate labels for acquired company, original system, date range and applicable contract set. Combining two workspaces can make ordinary IT operations easier while making it harder to identify records subject to different commitments. Preserve that distinction in the inventory even if the systems have already been integrated.
Use the register below to expose unresolved questions before asking a buyer to evaluate the content. Mark unknowns explicitly. An undocumented assumption should not become an assertion that the company has unrestricted rights.
| Item to document | Evidence to assemble | Question to resolve |
|---|---|---|
| Transferred rights | Transaction schedules and relevant agreements | Which entity can authorize this proposed use? |
| Customer restrictions | Contract versions by customer and period | Which records must remain excluded? |
| Source system | Workspace owner and export provenance | Can the original population be separated? |
| Existing licenses | Prior data-sharing and licensing commitments | Is there a conflicting right or exclusivity clause? |
Source notes: NIST: Privacy Framework
Make the initial buyer conversation conditional
Describe the candidate systems and history without transferring the acquired archive. Make the ownership review an explicit condition of the proposed scope. A buyer can discuss the kind of material it evaluates while the seller resolves authorization; an expression of interest does not cure a rights gap.
After review, prepare a package limited to approved sources. Preserve the exclusion register, the version of the scope that was authorized and the identity of the person empowered to sign. Keep deal diligence, privileged advice and personal employee records outside the operational dataset.
Source notes: Handshake: employer data partnerships
Illustrative scenario · fictional company
A fictional software acquisition keeps two archives separate
Lakeview Software acquires a smaller product company and inherits a support archive. The acquisition team finds that older enterprise contracts restrict secondary use, while later customers used different terms. Rather than combining all tickets with Lakeview’s existing support history, the team keeps contract periods and company origin distinct. Counsel reviews the proposed scope, and restricted customers stay excluded. The evaluation package includes only the approved cohort; no assumption is made that the entire acquired archive is licensable.
When to pause or narrow the scope
Client work and customer files are excluded from this starting scope. Assess company-owned internal records separately from personnel, health, privileged or NDA-restricted material.
- The transfer documents do not establish who controls the relevant records.
- Contract cohorts cannot be separated reliably.
- A prior license or exclusivity commitment conflicts with the proposed transaction.
Your preparation checklist
- Identify the legal entity that now controls each source.
- Assemble acquisition schedules and inherited restrictions.
- Preserve original-company and contract-period identifiers internally.
- Check prior licenses before negotiating new rights.
- Obtain documented authorization for the final scope before transfer.
Start with a description of the records. The quote form does not ask you to upload a dataset.
Discuss your dataSources and further reading
- ICO: data-sharing diligence after mergers and acquisitions (UK) · Checked October 26, 2026
- NIST: Privacy Framework · Checked October 26, 2026
- Handshake: employer data partnerships · Checked October 31, 2026
This is general information, not legal advice or confirmation that a buyer will accept your records. Published buyer ranges describe their programs, not an offer for your dataset. Buyers may pay QuoteMyData when a deal closes; see how we are paid.
