Sunsetting a product is a managed transition, not a single shutdown date. The work is to decide what will end, set distinct milestones, identify customer dependencies, provide a realistic migration path, and keep support aligned with the commitments made. A sound plan protects customer continuity while giving the business a clear, orderly route to closure.
What a product sunset includes
“Sunset” can refer to several different changes: stopping new sales, ending renewals, halting feature development, ending updates, withdrawing support, or shutting off access. These events do not have to happen together. Define exactly what is changing before setting dates or notifying customers.
Lifecycle policies illustrate the distinction. Moxa’s policy for covered hardware and supporting software separates active, discontinuation-notification, end-of-life, and end-of-service phases; it excludes software covered by a separate policy and customized products governed by contract. Microsoft likewise distinguishes support phases under its Fixed and Modern Lifecycle Policies. Check the applicable product entry and terms rather than treating “end of life” as a universal milestone. Moxa product lifecycle policy; Microsoft lifecycle overview.
How to decide whether to sunset a product
Build an evidence-based case
Document the strategic reason for ending the product and the evidence behind it. Consider customer use and value, product viability, operating and maintenance costs, opportunity cost, technical dependencies, market alternatives, and operational risk. A single financial metric is not a sufficient universal decision rule; the available guidance establishes no standard threshold that applies to every product.
#1 Best Overall
Understand who relies on the product before deciding how quickly to act. Separate active, business-critical use from low or occasional use, and examine differences among customer segments and accounts. Pragmatic Institute’s end-of-life playbook guidance recommends executive alignment, customer and market input, segment analysis, and a specific recommendation. Salesforce describes its own retirement decisions as considering usage information, customer feedback, and direct customer conversations. These are planning examples, not a formula that guarantees a good outcome. Pragmatic Institute end-of-life playbook; Salesforce end-of-life policy.
Make the decision cross-functional
Bring together product, engineering, security, sales, support, legal, finance, and customer-success leads. Each group sees a different exposure: engineering may know about integrations and technical dependencies; support can identify recurring customer problems; legal can assess contracts and jurisdiction-specific obligations; customer-facing teams can identify accounts that need individual migration assistance.
Rank #2
- Physical Condition: No Defects
- Great one for reading
- It's a great choice for a book person
How to plan the sunset timeline
Set milestones and owners
Build a dated plan with a named owner for each change. Depending on the product, milestones may include the announcement, last order or renewal, end of enhancements, end of updates, end of support, data export or migration cutoff, and final shutdown. State which functions remain available between milestones so customers can plan around the real transition rather than an ambiguous end date.
Allow time appropriate to the affected population, migration complexity, contractual obligations, and customer operating cycles. There is no universal notice period established by these sources. A product policy, customer contract, or applicable law may impose requirements; obtain product- and jurisdiction-specific review before committing to dates.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
Use policy examples carefully
The figures below describe the named organizations’ policies, not general standards for all product sunsets.
| Policy example | What it says | Scope and qualification |
|---|---|---|
| Moxa | Discontinuation notification is issued at least six months before entry into the end-of-life phase. Its policy says the end-of-life phase is expected in principle to last at least six years. | For products covered by Moxa’s policy and notices issued from July 1, 2026; product-specific considerations apply. Separate software policies and customized-product contracts are excluded. Moxa policy. |
| Microsoft Modern Lifecycle Policy | At least 12 months’ notice before support ends when no successor is offered. | The stated provision excludes free services and preview releases. A separate provision calls for at least 30 days’ notice for certain required customer actions needed to avoid significant degradation, unless otherwise noted. Microsoft Modern Lifecycle Policy. |
How to handle alternatives and migration
When a successor exists, assess whether it can actually carry customers’ work—not just whether it has a similar name. Map the current product’s important workflows to the alternative and identify differences, prerequisites, migration effort, and customer costs before describing it as a replacement.
Rank #4
- Workflow coverage: Which jobs, features, and business processes will transfer, and which will change or disappear?
- Migration work: What data, configuration, integrations, permissions, and training must move?
- Continuity: How long will customers receive support during and after migration, and what dependencies could interrupt service?
- Commercial impact: Will licensing, renewal terms, or customer costs change?
- Timing and reversibility: What must happen first, and can customers test or roll back before committing?
If there is no in-house successor, say so plainly. Point customers toward realistic options only when they have been assessed; do not imply that an alternative is equivalent without evidence. Microsoft’s lifecycle overview identifies App Assure as application-compatibility assistance for some enterprise migration scenarios. Eligibility and current availability should be checked with Microsoft before presenting the program as an option for a particular customer. Microsoft lifecycle overview.
Make migration assistance part of the sunset plan, not an afterthought. Specify who will help, what documentation or tools are available, how customers can escalate unusual dependencies, and how support will work while they transition.
Recommended Free Tools
Best Value
How to communicate a product retirement
Give affected administrators and buyers direct, repeated notice through channels likely to reach them. A useful communication explains the decision without obscuring the practical consequences. It should identify:
- What product, feature, service, or customer group is affected.
- What will stop working, and the date each change takes effect.
- What will continue to work before the final shutdown.
- What alternatives exist, if any, and where they differ.
- How to export data, migrate, request help, or raise an account-specific concern.
- What support remains available and until when.
Salesforce describes its general practice as providing written notice to administrators, reminders, recommended alternatives where available, and support through the retirement date. Those are Salesforce’s stated practices, not proof that any particular communication approach prevents disruption. Salesforce end-of-life policy.
A practical communication package can include an initial notice, a product-status page, milestone reminders, migration documentation, support scripts, and an escalation route for customers with unusual dependencies. Make the dates and actions consistent across all of them, and update the material if the plan changes.
How to execute and close the sunset
Track customer migration readiness and unresolved dependencies against the milestone plan. Give each responsible team an escalation path for risks that could affect data access, security, contractual commitments, or continuity. If a milestone must move, communicate the change promptly and consistently rather than letting different channels show conflicting dates.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteAt closure, make the actual end state match the stated one: sales availability, renewals, service access, updates, support, and data handling should follow the announced plan and governing terms. A 2026 European Parliament publication page describes a commissioned study mapping 83 cases of digital product and service discontinuation and examining economic, competition, and consumer harms. The figure is a map of cases in that study, not an estimate of how often products are sunset or proof that every retirement causes harm. European Parliament study publication page.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
