Create a Feature Deprecation and Sunset Migration Plan
Generate a structured, phased migration plan for retiring a software feature, including communication timelines and technical fallback strategies.
Prompt
Act as a Senior Product Manager. Your task is to create a comprehensive deprecation and sunset plan for a software feature. First, ask me these 3 questions: 1. What is the feature name and its primary user base? 2. What is the reason for deprecation and the target sunset date? 3. Are there any direct functional alternatives or data export requirements? Once I answer, provide the plan using the following rules: 1. Use a clear, chronological phase structure. 2. Include specific communication milestones for email, in-app notifications, and support documentation. 3. Define a fallback strategy for users who fail to migrate. 4. Detail the technical steps for data archival or deletion. Output format: ## Phase 1: Planning and Communication ## Phase 2: Execution and Support ## Phase 3: Sunset and Post-Migration. Each section must use a table to list tasks, owners, and dates. End with a risk mitigation section. This is not legal or contractual advice; consult your legal team regarding terms of service changes.Example output
Tips and common edits
Why this works
- Forces a structured, phased approach that prevents chaotic transitions.
- Includes specific tables to ensure accountability for each team member.
- Demands a risk mitigation section to address potential user pushback.
Use this prompt when you need to retire a product feature without causing user churn. Have your feature details and target dates ready. Works best in ChatGPT, Claude, or Gemini.
Common edits
- Adjust the phase dates to match your specific development cycle.
- Add a row for legal review if the feature sunset affects subscription tiers.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Define beta cohorts and launch exit metrics
Build a structured cohort plan and clear release criteria for your upcoming beta launch. Use this to prevent feature creep and ambiguous testing timelines.
Schedule phased customer communications for feature sunsetting
Create a structured, multi-channel communication timeline to retire a software feature without alarming customers or breaking workflows.
Stress Test Your Product Requirements Document for Edge Cases
This prompt audits your feature PRD to identify hidden technical risks, permission gaps, and scope creep before development begins.
Draft a Zero-to-One Product Discovery Experiment Card
Generates a structured, one-page test card with a falsifiable hypothesis, cheap validation test, and numeric kill threshold for new features.
Design a customer grandfathering plan for pricing changes
Structure a fair, phased grandfathering framework that updates customer pricing without triggering mass cancellations.
Draft a customer advisory board charter
Create a clear operational charter for a customer advisory board. Use it to align senior executives, define member terms, and prevent sessions from becoming feature wishlists.
- Draft high-usage account outreach for product deprecation
- Write a beta tester welcome and feedback guide
- Analyze customer feedback using Jobs to Be Done
- Construct a quarterly product review executive narrative
- Decline a stakeholder feature request diplomatically
- Draft a working-backwards press release and FAQ