Product Sunset Email to Customers: 9 Deprecation Templates

The short answer
Lead with what is going away and the exact end date. Give the real reason in one or two sentences, name the replacement, list the migration steps, say what happens to customer data, and name a person to contact. Send it at least 60–90 days ahead for features, longer for APIs, then send reminders.
Nine product sunset email to customers templates: feature deprecation, API sunset, plan retirement, integration end-of-life, migration help, final reminders.
On this page
- 01When should you send a deprecation notice?
- 02What a good deprecation email contains
- 03Template 1: First feature deprecation announcement
- 04Template 2: API version sunset notification
- 05Template 3: Pricing plan retirement
- 06Template 4: Integration end-of-life
- 07Template 5: Whole product discontinued (end of life)
- 08Template 6: Migration-help offer for heavy users
- 09Template 7: Midpoint reminder
- 10Template 8: Final reminder before shutdown
- 11Template 9: Shutdown complete
- 12The hard version: sunsetting something customers love
- 13What to do if there's no reply
- 14Handling the replies that come back
A product sunset email to customers is the message nobody wants to write. You are taking something away, and the reader did not ask for that. The good news is that most of the anger these emails cause comes from avoidable mistakes: a vague date, a reason dressed up as strategy, no clear path forward, or one email and then silence until the feature breaks.
Below are nine copy-paste templates covering the whole sequence, from the first announcement to the email after shutdown. Each uses bracketed placeholders: [FEATURE], [END DATE], [REPLACEMENT], [MIGRATION STEPS], [WHO TO CONTACT]. Replace every one before sending. A stray bracket in a deprecation notice reads as carelessness at exactly the moment you need trust.
When should you send a deprecation notice?#
Send the first notice as soon as the decision is final and you know the end date. Not before, because a notice you later reverse teaches customers to ignore the next one. Not much after, because every week of delay comes out of the customer's migration window, not yours.
How much notice depends on how much work the change creates for the customer. Removing a button they click once a month is not the same as retiring an API version their production code calls a million times a day. The table below is a practical starting point. It is our suggestion based on common practice, not a legal standard.

| What is going away | Suggested minimum notice | Reminders | Who must hear about it |
|---|---|---|---|
| Minor UI feature with a direct replacement | 30 days | 1 in-app banner plus 1 email | Users who touched it in the last 90 days |
| Core feature or workflow | 60–90 days | Midpoint and 7 days out | All admins plus active users of the feature |
| Pricing plan retired (customers moved or repriced) | 60–90 days, or what your terms require | 30 days and 7 days out | Billing contacts and account owners |
| Third-party integration end-of-life | 60–90 days, or as soon as the partner tells you | Midpoint and 7 days out | Admins of workspaces with it connected |
| Public API version | 6–12 months | Quarterly, then monthly, then weekly | Developer contacts and API key owners |
| Whole product discontinued | 90 days minimum, longer for paid annual plans | Monthly, then 7 days and 1 day out | Every customer and billing contact |
Check your contract before you pick a date
What a good deprecation email contains#
Every template below follows the same order, because the reader is asking the same questions in the same order. They want to know what is changing, when, why, what they should do, and who will help them.
- What is going away, named exactly as it appears in the product. Not 'some legacy functionality'.
- The end date, with a time zone if anything happens at a specific hour. Put it in the subject line.
- The real reason, in one or two plain sentences. 'Fewer than 2% of accounts use it and it blocks [X]' beats 'to sharpen our focus'.
- What replaces it, or a plain statement that nothing does.
- The migration steps, numbered, or a link to them.
- What happens to the customer's data and settings on the end date, and how to export them.
- A named person or a specific channel to contact, not a generic support address alone.
Write it in plain language. The U.S. federal plain language guidance, now hosted on Digital.gov, comes down to this: write for your specific reader, use short sentences, and put the most important information first. A deprecation email is a good test of that advice, because the reader is already annoyed and will not hunt for the date.
Template 1: First feature deprecation announcement#
Use this for the first notice of a core feature going away. It carries the full timeline so every later email can be shorter.
Subject: [FEATURE] will be removed on [END DATE]
Hi [First name],
We're removing [FEATURE] from [Your Company] on [END DATE]. After that date it will no longer appear in your account.
Why: [ONE OR TWO SENTENCE REAL REASON, e.g. it runs on infrastructure we're retiring, and keeping it would mean freezing work on the things most of you ask for].
What replaces it: [REPLACEMENT]. It covers [WHAT IT DOES THE SAME]. It does not yet cover [WHAT IT DOESN'T], and we'd rather tell you that now than have you find out.
What you need to do before [END DATE]: [MIGRATION STEPS].
Your data: [WHAT HAPPENS TO IT, e.g. existing reports stay viewable as read-only until [DATE]; export them any time from Settings > Export].
Timeline: today, announcement. [DATE], [REPLACEMENT] available to everyone. [DATE], reminder. [END DATE], [FEATURE] removed.
If this creates a real problem for your team, reply to this email or contact [WHO TO CONTACT]. A person reads every reply.
[Your name], [Title], [Your Company]
Template 2: API version sunset notification#
Developers want dates, versions and endpoints. Skip the pleasantries and lead with the facts. If you serve the API over HTTP, also send the Deprecation response header (RFC 9745, published March 2025) and the Sunset header (RFC 8594). That way, client code and monitoring can see the deprecation as well as people. RFC 9745 says the Sunset timestamp must not be earlier than the Deprecation one.
Subject: API [VERSION] sunset on [END DATE] — action required
Hi [First name],
API [VERSION] is deprecated as of today and will stop responding on [END DATE] at [TIME, TIME ZONE]. Requests after that will return [STATUS CODE / BEHAVIOUR].
Your account made [N] calls to [VERSION] in the last 30 days, mostly to [TOP ENDPOINTS]. API key(s) affected: [KEY LABELS].
Replacement: [NEW VERSION]. Breaking changes: [LIST, e.g. pagination moves from offset to cursor; the [FIELD] field is renamed [NEW FIELD]]. Full migration guide: [LINK].
From today, responses from [VERSION] include Deprecation and Sunset headers, so you can alert on them.
Why: [REAL REASON, e.g. [VERSION] can't support [SECURITY / SCALING REQUIREMENT] without breaking changes, so we're making them once, in [NEW VERSION]].
Questions or a hard blocker: [WHO TO CONTACT / DEVELOPER CHANNEL]. If you can't migrate by [END DATE], tell us before [EARLIER DATE] so we can talk about it.
[Your name], [Your Company] Developer Platform
Template 3: Pricing plan retirement#
This one is half deprecation notice, half price change. Say plainly whether the customer will pay more, less or the same. Ambiguity here reads as a hidden price rise.
Subject: Your [OLD PLAN] plan is being retired on [END DATE]
Hi [First name],
We're retiring the [OLD PLAN] plan on [END DATE]. Your account is currently on it.
What happens: on [END DATE], or at your next renewal after that date, whichever is later, your account moves to [NEW PLAN]. Your price changes from [OLD PRICE] to [NEW PRICE] per [PERIOD]. [OR: Your price does not change.]
What you gain: [FEATURES]. What changes: [ANY LOST LIMIT OR FEATURE, stated plainly].
Why: [REAL REASON, e.g. we've had two overlapping plans for a year and it's confusing new customers and our own billing team].
If you'd rather choose a different plan, you can switch any time before [END DATE] at [LINK]. If you want to cancel instead, you can do that at [LINK] and you won't be charged the new price.
Questions about your bill: [WHO TO CONTACT].
[Your name], [Your Company]
Template 4: Integration end-of-life#
Integrations often end because the partner changed something, not you. Say so factually, without blaming them, and do not speculate about their reasons.
Subject: Our [PARTNER] integration ends on [END DATE]
Hi [First name],
Your workspace has the [PARTNER] integration connected. It will stop syncing on [END DATE].
Why: [FACTUAL REASON, e.g. [PARTNER] is retiring the API version our integration uses, and the replacement doesn't support [CAPABILITY] that the integration depends on]. / [OR: usage has dropped to a level where we can't maintain it to the standard you'd expect].
What stops working: [LIST, e.g. new records won't sync; existing synced records stay where they are].
Alternatives: [REPLACEMENT, e.g. our native [FEATURE], a Zapier/Make connection using these steps: [LINK], or a CSV export on a schedule].
Before [END DATE], we suggest you [MIGRATION STEPS].
Need help choosing? Reply here or contact [WHO TO CONTACT].
[Your name], [Your Company]
Template 5: Whole product discontinued (end of life)#
The biggest version. Customers need to know about refunds, data export and what to move to. If you can honestly recommend another product, do it, because it is the most useful sentence in the email.
Subject: [PRODUCT] is shutting down on [END DATE]
Hi [First name],
We've decided to discontinue [PRODUCT]. It will shut down on [END DATE]. I wanted you to hear it from us directly, with enough time to plan.
Why: [THE REAL REASON, e.g. [PRODUCT] never reached the number of customers it needs to sustain itself, and we'd rather close it properly than let it decline].
Between now and [END DATE]: [PRODUCT] keeps working as normal. No new features, but we'll fix security issues and serious bugs.
Billing: [e.g. we've stopped all renewals. If you paid annually, we'll refund the unused months to your original payment method by [DATE]. You don't need to do anything].
Your data: export everything from [LOCATION] in [FORMATS]. After [END DATE] the export stays open until [DATA DELETION DATE]; after that, your data is permanently deleted.
Where to go next: [REPLACEMENT OR ALTERNATIVES]. [If applicable: we've agreed with [ALTERNATIVE] that you can import your export directly.]
Thank you for using [PRODUCT]. If you need anything during the move, contact [WHO TO CONTACT].
[Founder or exec name], [Title], [Your Company]
Template 6: Migration-help offer for heavy users#
Send this one-to-one, from a real person, to the accounts that rely on the feature most. Pull the list from usage data. These are the customers most likely to churn if the migration goes badly.
Subject: Help moving off [FEATURE] before [END DATE]
Hi [First name],
You'll have seen that [FEATURE] is going away on [END DATE]. Your team is one of our heaviest users of it, [SPECIFIC DETAIL, e.g. you have 40 active workflows built on it], so I'd like to make sure the move to [REPLACEMENT] doesn't cost you a week.
I can [CONCRETE OFFER, e.g. do a 30-minute call to map your workflows to [REPLACEMENT], or have our team migrate them for you and send them back to review].
Here's a link to book a time: [LINK]. Or reply with what works and I'll fit around you.
[Your name], [Title], [Your Company], [Direct email or phone]
Template 7: Midpoint reminder#
Short, and only to people who have not migrated yet. If your data can tell who has moved, do not email the ones who have.
Subject: Reminder: [FEATURE] is removed on [END DATE] ([N] days)
Hi [First name],
A reminder that [FEATURE] will be removed on [END DATE], [N] days from now. Your account still [SPECIFIC SIGNAL, e.g. has 12 reports that use it].
To move to [REPLACEMENT]: [MIGRATION STEPS, short version]. Full guide: [LINK].
Stuck? [WHO TO CONTACT].
[Your name], [Your Company]
Template 8: Final reminder before shutdown#
Send this 7 days out, and optionally again 1 day out. Put the date and the consequence in the subject line. The body should be readable in ten seconds.
Subject: Final notice: [FEATURE] is removed in 7 days, on [END DATE]
Hi [First name],
This is the last reminder. On [END DATE] at [TIME, TIME ZONE], [FEATURE] will be removed and [CONSEQUENCE, e.g. any workflow still using it will stop running].
If you haven't already: 1. [STEP]. 2. [STEP]. 3. Export anything you want to keep from [LOCATION].
If you need help in the next 7 days, contact [WHO TO CONTACT]. We've added extra support cover this week.
[Your name], [Your Company]
Template 9: Shutdown complete#
Most teams skip this one. It is worth sending because it answers the support tickets you would otherwise get the morning after.
Subject: [FEATURE] has now been removed
Hi [First name],
As announced on [ORIGINAL DATE], [FEATURE] was removed on [END DATE].
What's still available: [e.g. your exported data; read-only access to past reports until [DATE]].
If something stopped working that you didn't expect, reply to this email and tell us what you see. We'll look at it the same day.
Thank you for your patience through the change.
[Your name], [Your Company]
The hard version: sunsetting something customers love#
Sometimes the feature you are removing is popular. A vocal group of customers chose you partly because of it. Every instinct says to soften the email with phrases like 'streamlining the experience' or 'focusing on what matters most'. Don't. Those phrases tell a loyal customer that what they valued did not matter, and they will read every euphemism as a sign of something worse.
Do three things instead. Admit that people liked it. Give the real reason, even if it is unflattering, such as cost, a maintenance burden, a security problem or a strategic bet. Then offer the most generous migration path you can afford, and a direct line to someone senior.
| Instead of this | Write this |
|---|---|
| We're sunsetting [FEATURE] to streamline your experience. | We're removing [FEATURE]. We know a lot of you rely on it, and this wasn't an easy call. |
| As part of our ongoing focus on core value… | It costs us [X] to run and maintain, and only [Y] accounts use it. We can't justify it against [WHAT WE'RE BUILDING INSTEAD]. |
| We're excited to introduce [REPLACEMENT]! | [REPLACEMENT] covers most of what [FEATURE] did. It doesn't do [GAP] yet, and we're not promising a date for that. |
| Please contact support with any questions. | If this breaks something for you, email me directly at [ADDRESS]. I'm [NAME], [TITLE]. |
Expect replies, and some of them will be angry. That is useful information. Answer each one personally in the first week. Log what people say they will lose. If one gap comes up again and again, consider extending the date for affected accounts rather than holding the line for everyone.
One more rule: do not make promises in replies that the product team has not agreed to. 'We'll look at adding [GAP] to [REPLACEMENT]' is fine. 'It'll be there by March' is a second deprecation email waiting to happen.
What to do if there's no reply#
Silence is the normal outcome for most of your list, and that's fine as long as they have migrated. The silence that matters is from accounts that still use the feature as the end date gets close. Go back to the usage data instead of waiting for replies.
- 1
Segment by behaviour, not by who opened the email
Two weeks before the end date, pull the accounts that still use the feature. Open rates are unreliable because of privacy features in mail apps, so they don't tell you who has actually migrated.
- 2
Change the channel
Add an in-app banner or modal for those accounts, shown at the point where they use the feature. Someone who ignores email will still see a notice on the screen they are working in.
- 3
Escalate to a person for high-value accounts
For your largest affected customers, have the account owner send a short personal note (Template 6, shortened) or call. One line works: 'You're still on [FEATURE], which goes away on [END DATE]. Can I help?'
- 4
Try a different contact
If the original recipient has left the company, email the account's billing contact or other admins. Bounces and auto-replies saying someone has left are a common reason a notice goes unread.
- 5
Decide on a grace period before the date, not after
If a meaningful share of accounts has not moved, decide now whether to give them a short extension. Announce it in writing. Quietly leaving the feature running teaches customers that your end dates are soft.
Handling the replies that come back#
The announcement goes out through your product email or ESP. The replies come back to a person's inbox: 'Can we get an extension?', 'Where's the export?', 'Does the replacement support X?' Every one of them needs an accurate answer with the right dates, and you will get the same five questions a hundred times.
We build AI Emaily, an AI email client, and this is the part it is good at. Put the sunset facts, dates and approved answers into its Context brain. It then drafts replies to each customer in your voice, which you review and approve before anything sends. It can also surface accounts that wrote in and never got a follow-up. It is not a bulk sender or an ESP, so it will not send the announcement itself.
There is a 7-day free trial, with no permanent free plan. Plans are at aiemaily.com/pricing, and the product overview is at aiemaily.com.
Frequently asked
See it in AI Emaily
Keep reading
Sources

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.