practiceLeadership & teams

Product Sunsetting

The managed retirement of a product, feature, service, or version while reducing harm and helping affected people transition.

Download Markdown (.md)

01What it means

Product sunsetting is the deliberate process of ending availability and support. It covers the decision rationale, dependencies, customer communication, migration or exit options, contractual duties, data handling, operational shutdown, and post-retirement support. A sunset is a product change with real users, not merely a technical deletion.[1][2]

A product transition with real user consequences Decide, communicate, migrate, disable safely, and support the aftermath
  1. 01Evidence-based decisionUsers, economics, risk, obligations, alternatives
  2. 02Impact mapCustomers, data, integrations, processes
  3. 03Transition planTimeline, migration, export, refund, support
  4. 04Milestones + monitoringRepeated communication and exception handling
  5. 05Closure + reviewDisable safely; retain or delete as promised

Sunsetting includes contracts, vulnerable groups, integrations, data promises, refunds or exports, and operational readiness—not only deleting code.

02Why it matters

Keeping every offering alive consumes attention, infrastructure, support capacity, and security effort. Ending one carelessly can interrupt essential workflows, trap customer data, breach commitments, or damage trust. A disciplined sunset releases resources while treating customers and partners fairly.

03When to use it

Consider sunsetting when an offering no longer supports strategy, usage cannot justify its costs or risks, a replacement is materially better, a supplier or platform ends support, or safe operation is no longer feasible. Begin planning before announcing a date.

04How it works

  1. Build an evidence-based case covering users, economics, risk, obligations, and alternatives.
  2. Map affected customers, integrations, data, contracts, internal processes, and vulnerable groups.
  3. Choose a proportionate timeline with migration, export, refund, or support arrangements.
  4. Communicate early through channels customers actually use and repeat key milestones.
  5. Monitor transition progress, exceptions, complaints, and operational readiness.
  6. Disable safely, retain or delete data as promised, and review outcomes after closure.

05A practical example

Example

A reporting product retires a legacy dashboard after usage and security analysis. Customers receive six months’ notice, an account-level impact list, automated report conversion, data export, office hours, and a documented exception path. The team tracks migration completion before disabling access.

06Where it breaks

Usage data may understate importance to a small but dependent group. Long notice periods increase operating cost and security exposure, while short ones transfer cost to customers. A replacement is not equivalent if it removes accessibility, affordability, data portability, or critical workflows.

Common mistakes

  • Announcing an end date before mapping dependencies and obligations.
  • Relying on one email to reach affected customers.
  • Calling a replacement equivalent without testing real workflows.
  • Ignoring data export, retention, and deletion commitments.

07Sources

  1. Retiring Your ServiceGOV.UK Service Manual · Government service guidanceRetiring Your Service
  2. Product End of Support and RetirementsMicrosoft Lifecycle · Vendor lifecycle guidanceProduct End of Support and Retirements
View saved topics

Start typing to search titles, definitions, categories, and frameworks.