Plain-English definitions for every term vendors use when they're shutting down your software — plus answers to the questions everyone asks.
Last updated: March 13, 2026
A vendor's announcement that a software product will permanently shut down by a specific date. Access is cut off, and customer data is deleted from servers after the deadline. Unlike a feature removal or pricing change, a sunset is irreversible.
The term "sunset" comes from the idea of something reaching the end of its useful life — like the sun setting at the end of the day. Companies use it as a softer alternative to "shutdown" or "cancellation."
The date when a vendor stops providing software updates, bug fixes, and security patches. A product can be end-of-life but still technically running — especially common with on-premise software. In SaaS contexts, EOL and sunset often happen simultaneously.
For cloud products, EOL usually means full shutdown because there's no way for customers to run the software themselves after vendor support ends.
A formal notice that a product, feature, or API is outdated and will be removed in a future release. Deprecated features usually still work during a transition period — sometimes months or years — but vendors expect customers to stop using them.
Deprecation is not the same as sunset. It's a warning label, not an end date. However, repeated deprecation notices often lead to an eventual sunset announcement.
The technical act of shutting down servers, databases, and infrastructure. When a product is decommissioned, the hardware and software that powered it are turned off or repurposed. Decommissioning is the backend process that follows a public sunset announcement.
The period of time between a sunset announcement and the actual shutdown date — the window during which customers can export data and move to alternatives. Migration windows vary widely: some vendors give 18 months, others give 60 days.
Use the full migration window. Waiting until the final weeks is extremely common and leads to lost data and rushed decisions.
The ability to download your own data from a SaaS platform before it shuts down. Most vendors provide a data export feature as part of their shutdown process. Common export formats include CSV (for structured data), JSON, and ZIP archives containing files.
Always export raw data, not just reports or summaries. You want the underlying records so you can import them into a new platform.
When a company acquires a startup primarily for its engineering talent rather than its product. The startup's product is usually shut down shortly after the acquisition. Acqui-hires are a common trigger for SaaS sunsets — especially for smaller, venture-backed tools.
A pivot is when a company changes its product direction but continues operating. A sunset is when a specific product stops entirely. Sometimes companies sunset one product while pivoting to another — which can create confusion about whether migration paths exist within the same vendor's portfolio.
When switching away from a platform is difficult because your data, integrations, or workflows are deeply tied to it. High vendor lock-in increases the cost and risk of a sunset — which is why evaluating data portability before adopting any SaaS product is good practice.
An informal term for the wave of SaaS shutdowns happening as the startup funding environment tightened from 2022 onward. Many products that grew during the 2020–2021 funding boom are now shutting down as venture capital dried up and profitability requirements replaced growth-at-all-costs strategies.
A SaaS sunset is when a software vendor announces they will permanently shut down a product, end all support, and eventually delete customer data. Unlike a maintenance window or a feature removal, a sunset means the product is going away entirely — usually with a fixed deadline.
The vendor's servers stay on long enough for customers to export their data, then everything is deleted. You will not be able to log in, recover data, or access anything after the shutdown date.
They are often used interchangeably, but technically:
For cloud/SaaS products, the two usually happen together or very close together — you can't run a cloud product yourself after the vendor shuts down the servers.
It varies dramatically. General patterns:
Do not rely on generous notice. Export your data as soon as any sunset is announced.
Yes — unless you export it before the shutdown date. Once the deadline passes, data is typically deleted and cannot be recovered, even by the vendor's support team.
Most vendors provide export functionality during the sunset window. Use it early. The export process often takes longer than expected for large datasets, and support response times slow down as shutdown day approaches.
What to export before any shutdown:
Export your data immediately. Do this before anything else — before evaluating replacements, before notifying your team, before scheduling a migration project.
Data export can fail, take longer than expected, or surface data integrity issues. You want to discover these problems early, while support is still available and you have time to resolve them.
After securing your data:
Often yes — especially for annual plans where significant time remains after the shutdown date. Most vendors will proactively offer prorated refunds for the unused portion of your subscription.
If a refund isn't offered automatically:
Credit card chargebacks are a last resort but can be effective if a vendor shuts down without proper refunds.
The most common reasons:
The 2022–2024 funding pullback created a wave of shutdowns from startups that raised large rounds in 2020–2021 and couldn't sustain themselves in a tighter environment.
Before adopting any SaaS tool:
Yes. The pace of SaaS shutdowns accelerated significantly starting in 2022 and has not slowed. Several factors are driving this:
This is not a temporary trend. Planning for the possibility of a tool sunsetting is now basic operational hygiene, not an edge case.
SunsetProof maintains a Sunset Tracker with verified shutdown dates and migration resources. Other useful sources:
Need a printable version? Our Survival Guide includes a full printable checklist.
We publish detailed, step-by-step migration guides for active shutdowns — with honest alternative comparisons and data export walkthroughs.
Delighted → Jun 2026 Project Online → Sep 2026 Drift → 2026