Retiring a product sold on perpetual licenses: what you still owe

Does a perpetual license end when the product is retired?#

A perpetual license does not end just because the vendor stops selling or improving the product. The grant in most end user license agreements gives the customer a non-expiring right to use a specific version, subject only to the termination grounds written into the agreement, such as uncured breach or non-payment of the license fee.

That is why retirement is mostly a maintenance question, not a license question. The customer can keep running the last version it is entitled to. What changes is whether it receives updates, fixes, new versions and access to support staff.

Read the actual grant before assuming anything. Some older agreements describe the license as perpetual but tie it to a hardware key, a named server or a term subscription for a bundled component, and those details decide what you can safely switch off.

Which obligations continue and which ones end?#

The obligations that continue after retirement are the ones attached to the license itself; the ones that end are the ones attached to a paid service period. The table sorts the common promises in a perpetual license and maintenance stack and shows where to look for each.

The two rows that cause most disputes are prepaid support and activation. A customer that paid for several years of maintenance in advance has a strong argument that support must continue or the unused portion must come back, and a customer whose licensed copy stops activating has lost the thing it bought outright.

What notices should go out before end of life?#

End of life notices should follow the order of your contracts, not the order of your product plan. Each maintenance agreement sets its own non-renewal notice requirement, and the strictest one in the customer base sets the earliest date you can announce.

Send each notice to the address and by the method in that contract's notice clause. An email to a support contact may not count as formal notice, and a missed notice can extend a maintenance term automatically.

• 1End of sale notice: the product and new maintenance plans are no longer offered.
• 2Non-renewal notice for maintenance: sent to each customer within the window its agreement requires.
• 3End of support notice: the date fixes and help desk access stop, matched to each paid term.
• 4Final release notice: the last build, its checksum, documentation and any offline activation method.
• 5Escrow agent notice: if the escrow agreement requires the depositor to report discontinuation.
• 6Reseller and OEM partner notices: distribution agreements may carry their own support commitments.
• 7Third-party component check: confirm that runtime licenses for embedded components let existing installs keep running.

Where retirement plans go wrong#

Retirement plans usually go wrong when an engineering decision quietly removes something a licensed copy depends on. Turning off a license server, letting a code signing certificate lapse or shutting a hosted update endpoint can stop a perpetual install from starting, even though nobody intended to end the license.

The fix is to ship a final build that runs without those services, or to keep the service running in a minimal form. Document the choice in the final release notice so customers and their auditors can see exactly what they received.

Another common gap is a hosted component, such as a reporting portal or sync service, that holds customer records. Those records may need to be returned or deleted under the data terms, which are usually separate from the license grant and survive termination.

What if the company itself is winding down?#

A company that is winding down still has to treat perpetual licenses as continuing obligations, and bankruptcy law gives licensees specific protection. Under 11 U.S.C. section 365(n), if a trustee rejects an executory contract under which the debtor licenses intellectual property, the licensee may elect to retain its rights for the duration of the contract and any extensions available as of right, provided it keeps making the royalty payments due.

That protection is one reason to arrange a clean handover before the doors close: a final build, an escrow release where the agreement calls for one, and a record of which customers hold which entitlements. Wind-down officers should confirm with counsel how each license and maintenance agreement is handled in the chosen process.

Illustrative: retiring a desktop estimating product#

Illustrative: a fictional vertical software company sells a desktop estimating tool for cabinet and millwork shops on perpetual licenses, with optional annual maintenance. It has moved its roadmap to a cloud product and wants to retire the desktop line.

Counsel reviews the license agreement versions in use and finds that older customers activate through a hosted license server. The company releases a final build with offline activation, stops offering maintenance renewals and sends non-renewal notices to each customer under its own notice clause. Customers with prepaid support keep fixes and help desk access until their paid term ends.

The escrow agreement lists discontinued support as a release trigger, so the company notifies the escrow agent and confirms the deposit is current. It keeps the license entitlement database, maintenance contracts, Zendesk tickets and Jira history in a read-only archive. No customer loses a working install, and the company holds a complete record if a dispute or audit arises.

How SourceX looks at a retired product's records#

SourceX treats the records of a retired product as a closed archive that may hold value long after revenue stops. Support tickets, issue histories, code reviews and release notes from a mature product show how real problems were diagnosed and fixed, which is the kind of operational record AI developers license.

The SourceX five-step transaction (Supply, Rights, Preparation, Approval, Delivery) starts with a metadata-only fit check, and the Rights step reads the same license and maintenance agreements discussed here, because customer contracts may limit reuse of support content. If a package proceeds, the SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization.