How to Announce a Feature Sunset to Users in English

Telling users a feature they rely on is going away is one of the harder product communications to get right — too vague and users feel blindsided later; too apologetic and it reads as insincere. The goal is to be direct about the timeline, clear about alternatives, and calm in the face of pushback. This guide gives you the English to announce, explain, and support users through a feature sunset.

Announcing the Sunset Clearly

State what’s changing and when, without burying the key facts in soft language.

• “We’re writing to let you know that [feature] will be retired on [date]. After this date, it will no longer be available.”
• “As part of our ongoing platform updates, [feature] is being sunset in favor of [alternative], effective [date].”
• “This email is your advance notice — you have [X weeks/months] before this change takes effect, and we’ll send reminders along the way.”

Explaining the Reason

Give a genuine, brief explanation rather than corporate-sounding filler — users generally accept a real reason more easily than a vague one.

• “We’re consolidating this functionality into [alternative feature], which covers the same core use case with better performance and reliability.”
• “This feature has seen very limited usage over the past year, and maintaining it is taking resources away from features more people rely on.”
• “This change lets us focus our engineering effort on the parts of the product our data shows are most heavily used.”

Presenting the Alternative

Make the migration path concrete and actionable, not just a pointer to “check out our other features.”

• “You can achieve the same result using [alternative], and we’ve put together a short guide to help with the transition.”
• “If you’re currently using [feature] for [specific use case], we recommend switching to [alternative] — here’s how the two compare.”
• “Your existing data will be automatically migrated to [alternative] — no action is required on your end for that part.”

Handling Frustrated Feedback

Acknowledge the disruption honestly instead of deflecting or over-apologizing.

• “I understand this is disruptive, especially if you built a workflow around this feature — that frustration is completely fair.”
• “I don’t have a way to keep this feature running past the sunset date, but I want to make sure the migration path works well for your specific case — can you tell me more about your setup?”
• “This is genuinely useful feedback, and I’ll make sure it reaches the product team even though it won’t change this particular timeline.”

Following Up Before the Deadline

Send reminders and check whether users have actually completed the necessary migration steps.

• “This is a reminder that [feature] will be retired in [X days] — if you haven’t already switched to [alternative], now’s a good time to do so.”
• “We noticed your account is still actively using [feature] — if you need extra help migrating before the deadline, our support team is glad to assist directly.”

Vocabulary Reference

Key Takeaways

• State what’s changing and the exact date directly — don’t bury the key facts in soft or vague language.
• Give a real, brief reason for the sunset rather than generic corporate filler.
• Make the alternative and migration path concrete and actionable, not just a pointer elsewhere.
• Acknowledge user frustration honestly instead of deflecting or over-apologizing.
• Send reminders as the deadline approaches, and offer direct help to users who haven’t migrated yet.