Every product eventually needs to remove features. Maybe usage has dropped to negligible levels. Perhaps the feature creates technical debt that slows down everything else. Or you've built something better and need to consolidate.
Whatever the reason, the hard part isn't making the decision—it's communicating it.
TL;DR: Feature sunsets don't have to damage customer relationships. With proper timing, transparent communication, and genuine empathy, you can turn deprecation announcements into trust-building moments. This guide covers everything from notification timelines to email templates to collecting feedback that improves future decisions.
Why Feature Sunset Communication Matters
Removing features feels risky because it is. Customers chose your product partly because of that feature. They've built workflows around it. Some may have specifically purchased because of it.
Poor communication during a sunset can trigger:
- Immediate churn from affected users
- Erosion of trust across your entire customer base
- Negative reviews and social media backlash
- Internal finger-pointing between product, support, and sales
But here's what most teams miss: well-handled sunsets can actually strengthen customer relationships. When you communicate changes transparently and provide genuine migration paths, customers see a company that respects their investment and plans thoughtfully.
According to Pendo's research on feature retirement, the key is stopping new usage early while carefully managing existing users through the transition.
When Should You Sunset a Feature?
Before diving into communication strategies, let's ensure you're making the right call. Features become sunset candidates when:
Clear Indicators
- Usage below 5% of active users with no growth trend
- High maintenance cost relative to value delivered
- Technical debt blocking critical improvements
- Strategic misalignment with product direction
- Better alternatives exist within your product
Warning Signs to Investigate Further
- Low usage but high-value customers depend on it
- Feature is underused because it's poorly documented
- Usage is declining but feedback is positive
- Competitor differentiation relies on this feature
As AB Tasty points out, low usage alone isn't sufficient justification. You need to understand why usage is low before deciding to remove functionality.
Feature Sunset Communication Timeline
Google recommends notifying users at least 30 days before deprecation, but B2B SaaS often requires longer timelines. Here's a framework based on feature impact:
Low-Impact Features (< 100 active users)
- 30 days notice minimum
- 2 email touchpoints (announcement + reminder)
- In-app banner for affected users
Medium-Impact Features (100-1000 active users)
- 60-90 days notice
- 3-4 email touchpoints (announcement, migration guide, reminder, final notice)
- In-app notifications with migration prompts
- Direct outreach to top 10% of users by usage
High-Impact Features (1000+ active users or revenue impact)
- 6-9 months notice as HotSchedules recommends
- Comprehensive communication plan across all channels
- Dedicated migration support with success managers
- Customer advisory board consultation before announcement
Crafting Your Sunset Announcement
The first message sets the tone for the entire sunset process. Get it wrong, and you'll spend months in damage control mode.
What to Include
1. Lead with empathy, not explanation Don't start with why you're removing the feature. Start with acknowledging what customers will feel.
2. Be direct about what's changing Vague language creates anxiety. State clearly: "We are removing [feature] on [date]."
3. Explain the why (briefly) One or two sentences on your reasoning. Customers deserve to understand, but don't over-justify.
4. Present the migration path What should affected users do? Make this the longest section.
5. Offer support How can they get help? Who should they contact?
6. Thank them Acknowledge that using this feature represented trust in your product.
Sample Sunset Announcement Email
Subject: Important: Changes to [Feature Name] - Action Required
Hi [Name],
We know [feature] has been part of how you use [Product].
That's why we want to give you plenty of notice about an
upcoming change.
**What's changing:**
We're retiring [feature] on [Date - 60 days from now].
**Why we're making this change:**
[One sentence explanation - e.g., "We've built [New Feature]
which offers the same functionality with better performance
and additional capabilities."]
**What this means for you:**
Your current [data/workflows/settings] will remain accessible
until [date]. Here's how to transition:
1. [Specific step with link]
2. [Specific step with link]
3. [Specific step with link]
We've created a detailed migration guide here: [Link]
**Need help?**
Reply to this email or schedule a call with our team: [Link]
We're grateful you've trusted [Product] for [use case].
This change reflects our commitment to building the best
possible experience for you.
[Signature]
Collecting Feedback During Sunsets
Feature sunsets are research goldmines. Customers are motivated to share their perspectives, and their feedback can inform:
- How you communicate future changes
- Whether your replacement feature actually meets needs
- Hidden use cases you didn't know existed
- Improvement opportunities for retained features
Questions to Ask Affected Users
Before the sunset:
- How critical is this feature to your workflow?
- What would you need from an alternative solution?
- Would you consider [replacement feature] if it included [X]?
During migration:
- What's working well in the transition?
- What obstacles are you encountering?
- What documentation would help?
After sunset:
- Did the migration meet your needs?
- What could we have done differently?
- How do you feel about [Product] after this experience?
Using AI to Analyze Sunset Feedback
When you're collecting feedback from hundreds of affected users, manual analysis becomes impossible. This is where AI-powered tools like Pelin become invaluable.
Pelin can automatically:
- Categorize feedback by theme (migration concerns, feature requests, sentiment)
- Identify patterns across customer segments
- Surface the most urgent issues requiring immediate attention
- Track sentiment changes throughout the sunset process
Instead of reading 500 emails to understand customer reaction, you get synthesized insights in minutes. This lets you respond faster and adjust your communication strategy in real-time.
Common Mistakes to Avoid
Mistake 1: Announcing and Removing Too Quickly
The urge to "rip off the bandaid" is strong, but rushed sunsets create lasting damage. Even for low-usage features, give customers time to adapt.
Mistake 2: Hiding Behind Vague Language
"We're evolving our platform" tells customers nothing. Be specific about what's going away and when.
Mistake 3: Not Offering a Migration Path
If there's no alternative, say so honestly. If there is, make migration effortless. Don't make customers figure it out themselves.
Mistake 4: Ignoring Power Users
Your top users of a feature deserve personal outreach. A generic email isn't enough for someone who built their entire workflow around functionality you're removing.
Mistake 5: Treating Sunset as One-Way Communication
Feature removal is a conversation, not an announcement. Create channels for questions, concerns, and feedback.
Mistake 6: Failing to Document the Decision
Six months later, someone will ask why you removed that feature. Document your reasoning, the data that informed the decision, and the customer feedback you collected.
Turning Sunsets Into Opportunities
The best product teams view sunsets as relationship-building opportunities rather than damage-control exercises.
Strategies That Work
Offer affected users something extra: Early access to new features, extended trial of premium tiers, or direct access to product leadership can transform frustrated customers into advocates.
Use the sunset to gather broader feedback: "While we have your attention, we'd love to understand how we can better serve you." A sunset email with a survey link gets higher response rates than cold outreach.
Showcase your roadmap: Show customers what you're building instead of what you're removing. Help them see the sunset in context of product evolution.
Create content from the experience: The lessons you learn become blog posts, documentation improvements, and internal training. This guide exists because companies learned what works through experience.
How Pelin Helps With Feature Sunset Decisions
The hardest part of sunsetting isn't communication—it's knowing whether you should sunset at all. This requires understanding:
- Who uses the feature and how much they depend on it
- What customers have said about the feature over time
- Whether low usage reflects low value or poor discoverability
- What customers will say if you remove it
Pelin aggregates feedback from every channel—support tickets, NPS comments, sales calls, user interviews—and surfaces insights about specific features automatically.
Before making a sunset decision, you can ask Pelin: "What do customers say about [Feature X]?" and get a synthesized answer based on every piece of feedback you've collected.
This transforms sunset decisions from gut feelings into data-informed choices. And it ensures your communication acknowledges what customers actually care about, not what you assume they care about.
Key Takeaways
- Give adequate notice: 30 days minimum, 6+ months for high-impact features
- Lead with empathy: Acknowledge the impact before explaining your reasoning
- Provide clear migration paths: Don't make customers figure out alternatives themselves
- Collect feedback throughout: Sunsets are research opportunities
- Use AI to synthesize feedback: Tools like Pelin help you respond to customer sentiment at scale
- Document everything: Future-you will thank present-you
Feature sunsets are inevitable. Relationship damage from poorly handled sunsets is not. With thoughtful communication and genuine respect for your customers' investment in your product, you can remove features while strengthening trust.
Need help understanding what customers actually think about your features? Try Pelin to aggregate and analyze feedback from every channel—so your sunset decisions are informed by real customer sentiment.