Sunsetting a software product: license its records, sell the IP, or both?
Selling product IP transfers the code, trademarks and customer contracts to a buyer for good; licensing the records of building and supporting the product, such as tickets, pull requests, Jira issues and design documents, grants AI developers a time-limited training right while the company keeps ownership. Both can happen if the IP sale leaves those records with the company.
The verdict: two different assets, often two different buyers
Sell the IP when someone wants to keep running the product: a competitor, a large customer, or a company that wants the code base and the installed base. License the records when the product is going away but the history of building and supporting it is rich: years of support tickets with resolutions, pull requests with review threads, Jira issues tied to releases, and design decisions with their outcomes. When both kinds of buyer exist, an advisor can often arrange both, provided the asset purchase agreement leaves the internal records, and the right to license them, with the seller.
The two transactions answer different questions. An IP acquirer asks what the product can earn from here. An AI data buyer asks what the records show about how real software work gets done, step by step. That is why the records of a retired product can be worth licensing even when nobody wants the product itself.
Selling product IP vs licensing product records, side by side
| Dimension | Selling the product IP | Licensing the product's records |
|---|---|---|
| What changes hands | Source code, trademarks, domains, customer contracts, sometimes staff | A license to use defined records for AI training |
| Ownership afterwards | The acquirer owns the transferred assets | The company keeps ownership of its data |
| Typical counterparty | Strategic acquirer, competitor, customer or roll-up | AI labs and data buyers |
| What the counterparty values | Revenue, customers, roadmap, code quality | Depth of history, workflows, decisions and outcomes |
| Exclusivity | A permanent transfer | Typically exclusive for AI training for an agreed term |
| Price basis | Negotiated with the acquirer | One all-in price agreed with the company, SourceX's fee included |
| Diligence focus | Chain of title, open-source use, customer contracts | Rights to the records, privacy, completeness of exports |
| Effect on customers | Customers move to the acquirer or are migrated | None directly; redaction rules are agreed before any work begins |
| Payment | Purchase price at closing, sometimes with an earn-out | One-time payment, typically within about 60 days of invoicing once the buyer selects the data |
When selling the IP wins
- The product still has paying customers and an acquirer who wants to keep serving them.
- The code base is current, documented and maintainable by someone else.
- A strategic buyer values the customer relationships more than the company does.
- The seller wants a clean exit from the product with no continuing involvement.
When licensing the records wins
- The product is being shut down and no acquirer wants to run it.
- The code is dated, but the history behind it spans years of tickets, reviews and releases.
- The company itself is established: a US business that reached 50+ full-time employees at peak (contractors excluded), has several years of documented operations and has an executive able to authorize the license.
- Most of the records were created by the company's own staff, and customer contracts do not restrict their use.
Qualification looks at the company as a whole, so a sunset product's archive becomes one part of a wider inventory that may also include email, CRM, finance and support systems. Check the baseline on who qualifies and use the company fit checker for a preliminary, non-binding read.
When both can happen, and what the deal documents must say
Both transactions can close if the IP sale is drafted to leave the internal records with the seller. Four clauses usually decide it:
| Clause | Why it matters for a records license | Question for deal counsel |
|---|---|---|
| Definition of purchased assets and of books and records | A broad definition can sweep support tickets, repositories and project history into the sale | Are internal development and support records excluded, or does the seller keep a copy with the right to license it? |
| Excluded assets schedule | The cleanest place to reserve the records and the right to use them | Does the schedule name the systems and archives the seller keeps? |
| Confidentiality and non-use covenants | Can restrict the seller's later use of information about the product | Does the covenant permit a redacted AI-training license of retained records? |
| Transition services and data destruction | Shutdown plans can delete archives before anyone exports them | Who exports which system, and by what date? |
Ownership of the records needs its own check. The Copyright Office's circular on works made for hire explains that work an employee prepares within the scope of employment belongs to the employer, while commissioned work from outside contributors is made for hire only in listed categories and only with a signed written agreement. Code and documents from outside developers may therefore need a written assignment before the company can license them.
Customer data inside tickets is a separate question. FTC staff have stated that companies' promises not to use customer data for purposes such as training models are enforceable, whether they appear in privacy policies, terms of service or marketing, so check what the product's terms and privacy policy promised users.
This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.
How an advisor raises it during a product-line exit
| Stage of the exit | What to do about the records |
|---|---|
| Strategic review or engagement letter | Ask which systems hold the product's history and how many years they cover |
| Teaser and buyer outreach | Decide whether internal records are offered to IP buyers or held back |
| Letter of intent | Flag that the seller intends to keep internal records and may license them |
| Purchase agreement drafting | Reserve the records in excluded assets and align the confidentiality covenants |
| Closing and transition services | Agree who exports each system and confirm the exports are complete |
| Shutdown of remaining tools | Keep support desks, repositories and project tools running until exports are verified |
The people to involve are the CEO or founder, the CTO or VP of engineering who knows what the repositories and project tools hold, the head of support, and the CFO who owns the tool subscriptions and the deal economics. The M&A advisor overview shows how this fits a wider sell-side practice.
What to say to the seller
How the license sits alongside the rest of the company
A records license is typically exclusive for AI training for an agreed term, and the company keeps ownership; whether it can still use its own data afterwards is covered separately. If the whole company could be sold later, read who keeps license proceeds if the company is sold mid-deal. Sellers who confuse a managed license with selling data to a broker may find the comparison of data brokers, marketplaces and transaction layers useful.
Advisors who make the introduction can earn a partner reward. Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Rewards become payable only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. The reward comes out of SourceX's fee, so it never reduces the seller's proceeds; check your engagement letter and any professional rules on third-party fees before accepting it.
Next step
Before the next product-line exit you advise on, register as a partner so you can introduce the seller as soon as the records question comes up.
Common questions
Does selling the source code also sell the ticket and project history?
It depends on the purchase agreement. A broad definition of purchased assets, or of books and records relating to the product, can include support tickets, repositories and project tools, while a well-drafted excluded-assets schedule can keep them with the seller. Raise the question at the letter-of-intent stage, before drafting starts, so the acquirer is not surprised later.
Can the acquirer object to an AI training license of the retained records?
It can if the purchase agreement gives it grounds, for example through confidentiality or non-use covenants, a non-compete, or an assignment of all product records. If the agreement expressly reserves the records and the right to license them, the acquirer has agreed in advance. Settle it openly during negotiation rather than relying on silence in the contract.
Is one product's history enough for a license?
Qualification happens at company level, not product level. The company needs 50+ full-time employees at peak with contractors excluded, several years of documented operations, rights to the records and an authorized sponsor. A retired product's tickets, reviews and project history then form part of the company's wider data inventory alongside its other business systems.
What if outside contractors wrote most of the code?
Check the contractor agreements first. Work by employees within the scope of their jobs generally belongs to the company, but commissioned work by outside contributors generally needs a signed written assignment for the company to own it. Without one, the company may lack the rights to license that material, and the rights review may exclude or limit it.
Should the license happen before or after the IP sale closes?
Either can work if the documents line up. Licensing before closing needs the acquirer's awareness and an agreement that carves the records out; licensing after closing needs the seller to have kept both the records and the rights. In both cases, export every relevant system before any of them is shut down, because deleted archives cannot be licensed.
Related pages
- Which US businesses are a fit for a SourceX data licensing introduction
- Check Company Fit for Data Licensing
- Referral opportunities for M&A advisors
- Can a company still use its own data after signing an exclusive license?
- Who keeps data license proceeds if the company is sold mid-deal?
- Data broker vs data marketplace vs data transaction layer: what is the difference?
Free resources
- NPV calculator — Net present value with a discounted cash flow table.
- Time value of money calculator — Future and present value with optional regular payments.
- Business DSCR calculator — Debt service coverage from cash flow and loan terms.
- All free tools · MCP resource center
By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-10
Know a US company with valuable proprietary data?
Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.
Refer a company →I own a business
Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.
Start an assessment