The SaaS Sunset Strategy: How to Shut Down or Pivot Gracefully
Quick Answer: Minimum Notice Period by Situation
| Your situation | Minimum notice | Legal requirement |
|---|---|---|
| Monthly B2C subscriptions | 30 days | Recommended; may be required by ToS |
| Annual B2C subscriptions | 60 days + prorated refund | Must refund unused time or face chargebacks |
| SMB B2B (monthly contract) | 60 days | Check individual contracts |
| Enterprise B2B (annual SLA) | 90–180 days | Check SLAs — may be legally binding |
| Immediate insolvency / legal force | 30 days minimum | Data export must still be provided |
| Acquisition / handoff to new owner | 30 days with migration path | Migration support is the expectation |
Golden rule: 90 days is the industry standard minimum that preserves reputation. Anything less than 30 days in any scenario invites chargebacks, Twitter backlash, and legal exposure.
Who Is This Guide For?
| If you are... | Focus on |
|---|---|
| Founder shutting down a bootstrapped SaaS | Timeline + data portability + communication templates |
| VC-backed company pivoting | Investor communication + acqui-hire section |
| Acquired product being wound down | User migration + SEO preservation (301 redirects) |
| Legal/compliance team | GDPR/CCPA data deletion + refund obligations |
The 6th and final phase of the SaaS lifecycle is the "Sunset."
Whether you are shutting down due to failure, being acquired, or pivoting to a new product, how you exit determines your reputation for the next decade.
A messy sunset invites lawsuits, angry mobs on Twitter, and permanent brand damage. A graceful sunset can actually build respect.
1. The "Graceful Exit" Timeline
Do not pull the plug overnight. You need a structured wind-down phase.
- T-Minus 90 Days: Internal decision made. Legal review of contracts. Stop accepting new signups.
- T-Minus 60 Days: Public Announcement. Email to all users. Pro-rated refunds calculated.
- T-Minus 30 Days: "Final Call" for data export. Read-only mode activated (optional).
- Day 0: Servers shut down. DNS redirected to a static "Goodbye" page.
- Day +30: Secure data deletion (GDPR compliance).
2. The Golden Rule: Data Portability
Your users' data belongs to them. Holding it hostage or deleting it without warning is the cardinal sin of SaaS.
The Technical Requirement: Build a "One-Click Export" feature if you don't have one.
- Minimum: CSV export of core records (contacts, invoices, tasks).
- Better: JSON dump of full account history.
- Best: Direct migration tool to a competitor (see below).
3. Communication Strategy (Templates)
Be honest. Don't hide behind corporate jargon like "strategic realignment."
The "Shutdown" Email Structure:
- The Headline: Direct and clear. "Important: [Product Name] is shutting down on [Date]."
- The Reason: Brief explanation. "We couldn't find a sustainable business model."
- The Impact: "Your account will remain active until..."
- The Action: "Download your data here."
- The Money: " refunds for annual plans will be processed by..."
- The Alternative: Recommend a competitor.
4. Recommending Competitors (The Classy Move)
It sounds counter-intuitive, but helping your users move to a competitor is the ultimate goodwill gesture.
- Negotiate a discount code with a top competitor for your users.
- Create a specific migration guide ("How to move from Moydus to [Competitor]").
- This turns a painful disruption into a managed transition.
5. Legal & Compliance Checklist
- Terms of Service: Check your termination clauses.
- Refunds: Process pro-rated refunds for annual plans immediately. Do not wait for users to ask.
- Data Deletion: You must wipe PII (Personal Identifiable Information) from your backups and databases after the grace period to comply with GDPR/CCPA.
- Domain: Keep the domain active for at least 1-2 years, pointing to a static page or your new venture. Broken links rot the web.
6. The Pivot Option (Asset Salvage)
If you aren't shutting down but pivoting, the strategy changes.
- Don't force migration: If the new product is different, don't just migrate users automatically.
- The "Legacy" Mode: Can you leave the old version running in "maintenance mode" (no new features, critical security patches only) for a premium price?
- Open Source: Consider open-sourcing the code if it has community value. This buys immense goodwill.
Summary
Failures happen. In the startup world, they are expected. But integrity is permanent. Handle your sunset with the same care you handled your launch, and your users will follow you to your next venture.