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

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

Example for: deprecating the legacy 'CSV Report Generator' in a B2B analytics platform by October 1st.

Phase 1: Planning and Communication

TaskOwnerDue Date
Draft sunset FAQ and help docsProduct MarketingJuly 15
Send 'Feature Deprecation' email to usersCustomer SuccessAugust 1
Implement in-app banner warningEngineeringAugust 15

Phase 2: Execution and Support

TaskOwnerDue Date
Launch 'Export to JSON' migration toolEngineeringAugust 20
Conduct webinar on new workflowCustomer SuccessSeptember 1
Review support ticket volume trendsProduct OpsSeptember 15

Phase 3: Sunset and Post-Migration

TaskOwnerDue Date
Disable CSV generator UI accessEngineeringOctober 1
Redirect users to JSON toolEngineeringOctober 1
Archive legacy data to S3 bucketData TeamOctober 15
Risk Mitigation
  • Low Adoption: If usage of the new JSON tool remains under 40% by September 15, trigger a targeted email campaign highlighting JSON compatibility with Excel.
  • Data Loss Concerns: Provide a one-click download button for historical CSVs until December 31, 2024, to ensure zero data loss during the transition.
  • Support Overload: Prepare three pre-written response templates for support agents to handle common user complaints regarding the format change.
Written by AI from this prompt. Your results will vary.

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.

Keep exploring

More in Product Management
Product Management

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.

Product Management

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.