Zarlent

Can I license the data from a product I am retiring or pivoting away from?

Often yes, for records your company owns, such as code, internal chats, tickets and design files. Customer data is different: it was collected under a privacy policy and a purpose, and the FTC says reusing it for AI training under a quietly changed policy can be unfair or deceptive.

No buyer pays to be mentioned

What could your company's records earn? Get a range in 30 seconds. Free, no obligation.

Why does a retired product still have value?

The work records behind a product are not tied to its sales. Code history, engineering chat, support tickets and design files show how real decisions were made, and buyers pay for that. Buyers also say records from retired systems may still count: note them in your inventory and the buyer will say whether it can use the export (prepare your records).

Published ceilings per company, from buyer listings read 20 Nov 2026 (by industry):

What the retired product leaves behindPublished ceiling
Private software code with history$250K–$500K
Legacy-language code (COBOL, Fortran)$250K–$500K
Usage data from an AI app or agent$250K–$500K
Product database of a SaaS company with a data team$250K–$500K
Everyday production codeup to $250K

These are ceilings, not typical deals. A buyer prices the whole company, so a retired line adds to the offer rather than earning its own.

What about customer data from the product?

This is where care is needed. Customers shared data under your privacy policy and contract. In February 2024 the FTC warned that it would pursue firms that "adopt more permissive data practices", such as sharing data with third parties or using it for AI training, and tell users only through a quiet, retroactive change to the terms of service or privacy policy (The Record, 14 Feb 2024).

The FTC cited a 2023 case in which a genetic testing company retroactively widened the third parties it shared data with, without notice or consent. It settled and agreed to have stored DNA samples older than 180 days destroyed (same source).

Records you hold for clients are usually out of scope for any license. Keep them out (what AI data buyers check).

Does EU or UK law change this?

Yes. The GDPR says personal data must be collected for specified purposes and not further processed in a way that is incompatible with them, and must be kept in an identifiable form no longer than necessary (Article 5(1)(b) and (e), GDPR text). A retired product's user data should usually be deleted or anonymized, not licensed. See companies outside the US.

What should I do with the old data?

  1. List what the product holds. Separate your own work records from user and customer data.
  2. Read the privacy policy and customer contracts that were in force when the data was collected.
  3. License the work records; de-identify anything personal first (de-identification).
  4. Delete or archive user data under your retention rules, with a written record.
  5. Check your contracts for transfer, deletion and notice duties when the product ends.

Do I keep running the business while I license?

Yes. You license a copy through a read-only connection, so nothing changes in your systems (keep your business running).

What has company data sold for?

We record 40 public data sales, each with its price, date and source. Search all 40 recorded data sales.

Questions

Can I license the code of a product I discontinued?

If your company owns it, yes. Check that contractors assigned their rights, and open-source terms for any bundled code. This page is general education, not legal advice.

Do I have to tell customers I am licensing records?

Not for your own internal work records. For records that contain customer personal data, your privacy policy and local law decide, and the FTC has warned against quiet policy changes.

Does a pivot change what buyers pay?

Buyers price size, years of history, linked systems and industry. A pivot does not lower the price by itself.

Sources