# Product Sunsetting

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

- Type: practice
- Domain: Leadership & teams
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/product-sunsetting/>)

## What 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.

## Why 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.

## When 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.

## How 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.

## A practical 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.

## Where 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.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/product-sunsetting/#visualization-product-sunsetting>)

## Sources

1. [Retiring Your Service](<https://www.gov.uk/service-manual/agile-delivery/retiring-your-service>) — GOV.UK Service Manual · Government service guidance
2. [Product End of Support and Retirements](<https://learn.microsoft.com/en-us/lifecycle/overview/product-end-of-support-overview>) — Microsoft Lifecycle · Vendor lifecycle guidance

## Related topics

- [Roadmap Communication](<https://wiki.soroush.uk/topic/roadmap-communication/>)
- [Product Risk Management](<https://wiki.soroush.uk/topic/product-risk-management/>)
- [Stakeholder Management](<https://wiki.soroush.uk/topic/stakeholder-management/>)
