Product sunset plan: what to do with the support and engineering history

What happens to a retired product's records?

When a product is sunset, its support tickets, code, release notes and decision records stay behind, and they are often the least planned part of the shutdown. The retention plan decides whether that history is kept intact, archived with an owner, or lost when licenses and hosting end. For a company with 50+ full-time employees at peak (contractors excluded), a retired product may leave years of connected records that a licensing review could value.

This guide is written for operators and sponsors managing a sunset. It treats data retention as a step in the plan, ahead of customer communication and infrastructure shutdown.

Which sunset records are worth preserving?

Customer-owned content inside the product is a separate matter. A company may not hold the right to license content its customers created in the product, so that content is excluded unless rights are confirmed.

What is the sunset timeline, and where does retention fit?

Link this to your renewal calendar: SaaS renewals as data checkpoints shows how to catch the contract dates that control access.

The sunset retention screen

Four questions decide whether a retired product's history is worth a licensing review.

• Records: did the product run for several years with a real customer base, leaving connected tickets, code and decisions?
• Rights: does the company own the work product and have the right to license it, with customer content and personal data handled separately?
• Reach: can you introduce the owner, CEO, CFO or authorized representative who can decide?
• Readiness: will someone preserve exports before accounts lapse, and will the owner consider an exclusive license for an agreed term?

The data inventory builder helps list systems and history at the metadata level.

What do you say to the sponsor?

How does the introduction work?

1. Register, then give the sponsor your referral link or submit the company through the referral form.
2. SourceX checks size, history, breadth and rights.
3. The company inventories the sunset product's systems.
4. Price and terms are agreed with the company.
5. Buyers review, typically responding within about two weeks once the company is deal-ready.
6. The deal closes, data goes out under redaction rules set in advance, and the company is paid.
7. Your reward follows once SourceX has been paid.

De-identification and redaction rules are agreed with the company before any work starts.

How do you preserve the history without a big project?

Keep it narrow. Pick the three or four systems that hold the product's work: the ticketing tool, the code and review platform, the incident or on-call tool and the shared drive holding decision documents. Ask each administrator to confirm, in writing, the oldest record date and the export route. Store the confirmation next to the sunset plan.

Then set a calendar hold for the date before each contract ends. If a vendor says data is deleted on termination or after a short grace period, treat that date as the deadline, not the contract end date. Related histories, such as sales engagement records tied to the product's customers, follow the same logic.

Avoid two shortcuts. Do not forward tickets or code to anyone for a quick look, since partners never receive or describe confidential records. And do not delete accounts to cut cost before the owner has decided; a deleted archive cannot be recovered.

What should the sunset plan record about each system?

Give every system tied to the product one row in the plan, so a successor can find the history later without asking around.

Review the table at the end-of-support meeting. Any row marked "no" before accounts lapse is a loss to record, not a surprise to discover later.

How do partner rewards work?

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 cumulative per referred company. The reward becomes payable only after the buyer pays and SourceX receives its fee; a lead, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. It is a share of SourceX's fee and is never deducted from what the company receives. Sponsors should check their own firm policies on accepting fees connected to portfolio companies, and read the program terms.

When is this the wrong move?

Skip the licensing review if the product served few customers for a short time, if the records are mostly consumer personal data, if customers own the content and have not agreed, if the same data has already been licensed for AI training, or if the company is under the 50+ full-time employees at peak baseline. If exports were never taken and the vendor deletes data at termination, record the loss and document it. If a trustee or assignee controls the assets, bring them in before anything else; the earlier guide on keeping Xero records after a business closes shows the same approach in a wind-down.

Next step

Add a records line to your next sunset plan and run the screen. If the company qualifies, register as a partner. The private equity operating partner page explains how sponsors use the program, and who qualifies lists the baseline.