Private equity and portfolios
Non-core software products: sell, sunset, maintain or license the records?
By SourceX Editorial · Updated
Short answer
A holding company has four options for a non-core software product: sell it, sunset it, keep maintaining it, or license its internal records, and the last can combine with any of the other three. The decision rule: settle what happens to issue, code review and support history before signing a sale or sending end-of-life notices.
Key takeaways
- Licensing internal records is not a separate exit; it can sit alongside a sale, a sunset or continued maintenance.
- In an asset sale, the purchase agreement decides whether the seller keeps any copy of, or rights to, historical records.
- Cancelling a sunset product's tools starts vendor deletion clocks on its issue, chat and support history.
- Customer content stays governed by customer contracts; internal engineering and support records are usually the company's to decide on.
- Recency fades after a product stops changing, so a sunset decision is also a timing decision for any license.
What are the options for a non-core software product?#
The options for a non-core software product are to sell it, sunset it, keep maintaining it, or license the records it produced. The first three decide the product's future. The fourth decides what happens to its history, and it can be combined with any of the others.
Holding companies tend to weigh the first three on revenue, support cost and team capacity, and treat records as an afterthought. The table puts records on the same line as customers and staff.
| Option | Customers | Staff | Records |
|---|---|---|---|
| Sell | Contracts usually move to the buyer, subject to consent and assignment terms | Some move with the product; others are redeployed | Transfer with the product unless the agreement reserves copies or rights |
| Sunset | Receive end-of-life notice, then migrate or leave | Redeployed or released after wind-down support | Customer data returned or deleted per contract; internal records kept or deleted per schedule |
| Maintain | Keep service, often with limited new features | A small dedicated team or shared engineers | Keep accumulating in live systems |
| License the records | Unaffected when customer content is excluded | Unaffected | A prepared subset is licensed and the company keeps ownership |
When selling the product is the better path#
Selling a non-core product works when another owner values its customers, code and team more than you do, often a competitor or a specialist acquirer in the same vertical. The deal is usually an asset sale of the product line, and the purchase agreement lists what transfers: code, trademarks, customer contracts, domains and the product's records.
Records are where sellers lose options without noticing. The issue tracker, code review history, support tickets and release notes often transfer by default as part of the business. A holding company that wants a reference copy, or the right to license internal engineering records later, has to negotiate that before signing and confirm the buyer accepts it.
- List every system holding product history: issue tracker, source control, help desk, chat and documentation.
- Decide which records transfer, which the seller keeps a copy of, and on what terms.
- Check customer contracts for assignment consent and data return obligations.
- Agree export assistance and timing in any transition services agreement.
- Disclose any past license or data-sharing arrangement that involves the product.
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
When sunsetting is the better path#
Sunsetting fits a product with a shrinking customer base, no natural buyer and support costs that outrun what it earns. Customer contracts set the notice period, any transition help and what happens to customer data, which is usually returned or deleted.
The product's internal records follow different rules. Issue histories, code reviews, internal discussions and support outcomes belong to the company, but the tools that hold them start deletion clocks once cancelled. Atlassian states that after a cancelled subscription period ends, the site stays accessible for 15 more days and data is retained for 60 days on Free, Standard, Premium and Enterprise plans before permanent deletion. Zendesk's Service Data Deletion Policy starts an automated deletion process 90 days after cancellation that cannot be reversed once it begins.
Export and verify internal histories before cancelling any tool, then keep them in the company's own storage under its retention schedule.
When maintaining makes more sense#
Maintaining a non-core product makes sense when it still earns steadily, customers depend on it, and a small team can keep it secure. Many vertical software holding companies run long tails of products this way and treat them as cash generators.
The risks are concentrated rather than large: one or two engineers who understand the code, dependencies that drift out of support, and contracts that renew without review. Maintenance also keeps records accumulating, which keeps recency high if the group later decides to license internal history.
Where licensing the records fits#
Licensing the records fits when a product's history shows how real software was built and supported over time: issues linked to code reviews, fixes, releases and support outcomes. That linked history records human judgment on real problems, which is what AI developers look for in operational records.
Under the SourceX Enterprise Data Value Framework, uniqueness, domain expertise, human-generated signal and recency increase value, reproducibility reduces it, and preparation cost and privacy burden reduce net value. A niche vertical product with long, well-linked history can rate well on several drivers even when it earns little revenue.
Records from retired operations already reach this market. Forbes reported in April 2026 that after one company was wound down, its remaining internal chat, project-tracking tickets and emails became items offered to AI developers. If a license is granted, exclusivity is the term to watch: an exclusive license granted before a divestiture shows up in the buyer's diligence, while a non-exclusive license of internal records is simpler to disclose.
Decision rules for a holding company board#
A board decision on a non-core product goes faster with explicit rules. The table pairs the product's situation with a default path and the records step that has to be settled before the decision is executed.
| Situation | Lean toward | Records step to settle first |
|---|---|---|
| A credible buyer values the customers and code | Sell | Reserve a copy or license-back of internal records in the purchase agreement |
| The base is shrinking and no buyer exists | Sunset | Export issue, code review and support history before tools are cancelled |
| Steady earnings and a small, stable team | Maintain | Check retention settings so history keeps accumulating |
| Long, linked engineering and support history | Add a records license to any path | Confirm customer content can be excluded and prior grants are clear |
| The value sits mostly in customer-owned content | Sell, sunset or maintain without a records license | Treat records as customer-controlled under the contracts |
Illustrative: a legacy desktop product inside a vertical software group#
Illustrative: a fictional vertical software holding company owns a cloud platform for equipment rental businesses and, from an earlier acquisition, a legacy desktop scheduling product for event rental companies. The desktop product has a shrinking customer base, two engineers near retirement, years of Jira and Bitbucket history, and a Zendesk instance full of resolved tickets.
A competitor offers to buy the customer contracts and code but has no use for the old engineering records. The holdco CEO agrees an asset sale that transfers code and contracts, while the purchase agreement lets the group keep a copy of internal Jira issues, pull request reviews and resolved tickets with customer content excluded. Both engineers help with the export before the tools are cancelled.
The group then runs a metadata-only fit check on the retained history. Whether a license follows depends on buyer interest and preparation, but the option was preserved instead of lost in the sale.
How SourceX handles records from a non-core product#
SourceX handles retained product records through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The Rights step checks the purchase agreement, customer contracts and any prior grants; Preparation removes customer content and personal details; and the company approves every step.
Large repositories stay in the company's own storage or ship on encrypted drives rather than being hosted by SourceX, and the SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization for each package.
Frequently asked questions
Does licensing a product's records reduce what a buyer will pay for the product?
It depends on what the buyer is paying for. Most product buyers value customers, code and recurring revenue rather than old internal records. An exclusive license, or a restriction on the buyer's own use of the records, could matter, so disclose any license and prefer non-exclusive terms.
Can we license records from a product after we sell it?
Only if the purchase agreement lets the group keep a copy and use it that way. Once records transfer without a reservation, they belong to the buyer. Settle the question in the agreement before closing, not afterward.
What happens to customer data when a product is sunset?
Customer contracts usually govern it: notice, an export window for customers, then return or deletion. Customer data is not part of a records license unless contracts clearly allow it, so most holding companies return or delete it as agreed and consider only internal records.
Do code reviews by former engineers raise privacy issues?
They can carry names, usernames and comments about individuals. Preparation usually replaces names and identifiers and removes personal remarks while keeping the technical discussion. Employee notices and any privacy laws that may apply are reviewed with counsel before a license.
Is open-sourcing the code an alternative?
For some products it is a fifth option that gives customers a path after a sunset. It does not address the internal records, and publishing the code can reduce the uniqueness of related engineering history. Decide on records before publishing anything.
Sources
- Atlassian states that after a cancelled subscription period ends, the site stays accessible for 15 more days and is then deactivated; data is retained for 15 days for trials and 60 days for Free, Standard, Premium or Enterprise plans, then permanently deleted and unrecoverable. Source
- Under Zendesk's Service Data Deletion Policy, an automated process that permanently deletes the account's Service Data starts 90 days after the account is canceled or terminated, and once it starts it cannot be reversed. Source
- Forbes reported on April 16, 2026 that cielo24 former CEO Shanna Johnson used wind-down firm SimpleClosure to close the company, after which its remaining digital records (years of internal chat, project-tracking tickets and emails in employees' cloud drives) became items for sale to AI developers. Source
Related resources
- InsightRevenue options for an end-of-growth software product compared
- InsightWarranties to give and avoid when licensing code or tickets
- IndustryFintech software data
- QuestionCan SaaS data be licensed?
- InsightCan property management companies sell their data to AI companies?
- SolutionData licensing: granting defined rights to use your data
See if your company qualifies
A short company assessment. No data uploads are needed.