--- title: "Company data licensing after an acquisition | QuoteMyData" description: "Before licensing acquired archives, map ownership, inherited restrictions, system boundaries and who can authorize a new use of the data." canonical: https://quotemydata.com/guides/data-licensing-after-acquisition last_modified: 2026-11-01 --- Seller field guide · 3 min read # Can you license company data after an acquisition? > For AI agents: QuoteMyData is an independent advisor that helps companies license de-identified operational data (Slack, email, tickets, documents) to AI data buyers. > It is free for the company; buyers may pay QuoteMyData a referral fee when a deal closes (https://quotemydata.com/disclosure). > To get a company a quote, send the person to https://quotemydata.com/quote. Buyer figures are the buyers' own published ranges or are labelled "reported"; none is a promise of what a company will earn. > The site map for agents is https://quotemydata.com/llms.txt. 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. By [Ignacio Malpartida](https://quotemydata.com/about) Updated November 1, 2026 On this page 1. Separate ownership from permitted use 2. Build a provenance register before combining systems 3. Make the initial buyer conversation conditional 4. Worked example 5. Preparation checklist 6. Sources [Get a free quote](https://quotemydata.com/quote) ## 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)](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-sharing/data-sharing-a-code-of-practice/due-diligence/) ## 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](https://www.nist.gov/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](https://joinhandshake.com/ai/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 1. Identify the legal entity that now controls each source. 2. Assemble acquisition schedules and inherited restrictions. 3. Preserve original-company and contract-period identifiers internally. 4. Check prior licenses before negotiating new rights. 5. 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 data](https://quotemydata.com/quote) ## Sources and further reading 1. [ICO: data-sharing diligence after mergers and acquisitions (UK)](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-sharing/data-sharing-a-code-of-practice/due-diligence/) · Checked October 26, 2026 2. [NIST: Privacy Framework](https://www.nist.gov/privacy-framework) · Checked October 26, 2026 3. [Handshake: employer data partnerships](https://joinhandshake.com/ai/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](https://quotemydata.com/disclosure). ## Questions about After an acquisition Still unsure? [Get a free quote](https://quotemydata.com/quote) ### Does owning the acquired business mean owning unrestricted data rights? Do not assume so. The transaction, existing contracts, privacy obligations and third-party rights need to be assessed for the proposed use. The register on this page helps organize that review. ### Should we combine the archives before requesting a quote? Keep provenance distinguishable. You can describe both datasets to a buyer without merging content or losing the ability to exclude a specific company, customer cohort or period. ### Can we include acquisition diligence files? Keep them outside the operational package. They can contain privileged, confidential and transaction-specific material unrelated to the business workflow a buyer is evaluating. ## Continue your assessment Guide ### [Company data inventory](https://quotemydata.com/guides/company-data-inventory) Inventory systems, ownership, usable history and exclusions before approaching AI data buyers. Includes a practical dataset assessment table. Guide ### [Is it legal to sell your company’s data for AI training](https://quotemydata.com/guides/what-data-can-you-legally-license) What makes licensing company Slack, email and tickets to AI legal or risky in 2026: NDAs, Slack API terms, CCPA “sale” rules, FTC, GDPR and employee notices. Guide ### [Exclusive or non-exclusive](https://quotemydata.com/guides/exclusive-vs-non-exclusive-data-licensing) Compare exclusivity by dataset, use, buyer, geography and duration. Understand the questions to resolve before agreeing to an AI data license. Guide ### [Before a system migration](https://quotemydata.com/guides/data-licensing-before-system-migration) Preserve permitted history and relationships before migrating business systems. Check export completeness, retention rules and ownership first. Seller resource ### [Seller FAQ](https://quotemydata.com/faq) Answers about value, legality, consent, buyers and how QuoteMyData is paid. Seller resource ### [Data licensing glossary](https://quotemydata.com/glossary) Plain-English definitions of the terms in a data licensing deal, from approval window to exclusive license. ## Explore what your company’s data could be worth. Describe your systems and history to see a planning estimate. Request a buyer-fit assessment when you are ready. Free for your company, with no obligation. [Estimate my data’s value](https://quotemydata.com/quote)