End-of-Life (EOL) Message

# EOL Message

Craft a clear, empathetic End-of-Life (EOL) message that communicates product or feature discontinuation, explains the rationale, addresses customer impact, provides transition support, and positions the replacement solution.

This is not a generic sunset announcement—it's a customer-centric communication that acknowledges loss while framing the change as progress.

## The EOL Messaging Framework

An effective EOL message balances honesty about the change with empathy for customer impact:

1. **Company context** — Who you are and your commitment to customers
2. **The announcement** — What's being discontinued and what's replacing it
3. **The rationale** — Why this decision benefits customers (not just the business)
4. **Current product context** — What the product was and who it served
5. **Customer impact** — How this affects users (acknowledge the disruption)
6. **Transition solution** — What the replacement is and how it improves on the old
7. **Support measures** — How you'll help customers migrate
8. **Timeline** — Key dates and milestones
9. **Call to action** — Next steps and contact info

## What This Is NOT

- **Not a terse shutdown notice:** "We're discontinuing Product X. Goodbye."
- **Not business-centric:** Don't lead with "This reduces our costs"
- **Not vague:** "Soon" is not a timeline
- **Not defensive:** Don't blame customers ("low usage forced us to shut down")

## Application

### Step 1: Gather Context

Before drafting, ensure you have:
- **Product being discontinued:** What specifically is ending?
- **Replacement solution:** What's replacing it (if anything)?
- **Timeline:** Key dates (announcement, feature freeze, shutdown, data export deadline)
- **Customer impact:** How many users affected? What workflows disrupted?
- **Support plan:** Migration support, training, discounts, data export tools
- **Rationale:** Why is this happening? (Technology obsolescence, strategic shift, consolidation)

If missing context: don't send the message until you have a complete transition plan. Customers will ask "What do I do now?"—you must have an answer.

### Step 2: Product Transition Narrative

```markdown
### Product Transition Narrative

**We are:** [Company and relationship to product being phased out]
- [Key point about company's commitment to customers]
- [Key point about company's product evolution]
- [Key point about company's future vision]

**Announcing:**
- [Single sentence: EOL of old product + introducing replacement]

**Because:**
- [Reason 1: technological advancements]
- [Reason 2: improved performance]
- [Reason 3: better alignment with customer needs]

**Which means for you:**
- [Customer-perspective impact and benefits]
```

### Step 3: Current Product Context

```markdown
### Current Product Context

**Our product** [name]
- **is a** [description and primary function]
- **that has served** [target customer] for [duration]
- **by providing** [key benefits or solutions]
```

### Step 4: Customer Impact

```markdown
### Customer Impact

**We understand that this may affect you by:**
- [Potential impact 1 on operations or processes]
- [Potential impact 2 on operations or processes]
- [Potential impact 3 on operations or processes (if applicable)]
```

### Step 5: Transition Solution (Positioning)

```markdown
### Transition Solution

**For** [target customer affected by the EOL]
- **that currently use** [old product]
- [replacement product]
- **is a** [category]
- **that** [benefit statement focusing on continuity + improvements]

### Differentiation and Continuity

- **Like** [old product],
- [replacement product]
- **provides** [how replacement maintains key benefits]
- **while also offering** [new benefits or improvements]
```

### Step 6: Support and Timeline

```markdown
### Support and Next Steps

**To ensure a smooth transition, we will:**
- [Support measure 1, e.g., "Provide 1-on-1 migration assistance"]
- [Support measure 2, e.g., "Automatically migrate your workflows (with approval)"]
- [Support measure 3, e.g., "Offer 3-month discount on new product for existing customers"]

### Timeline

- [Date 1 + milestone, e.g., "March 1, 2026: Migration tool available"]
- [Date 2 + milestone, e.g., "September 1, 2026: Old product becomes read-only"]
- [Date 3 + milestone, e.g., "December 31, 2026: Old product fully discontinued, data export deadline"]
```

Quality checks:
- **Sufficient lead time:** 6-12 months typical
- **Clear milestones:** When does functionality freeze? When does shutdown happen?
- **Data export deadline:** When do they lose access to their data?

### Step 7: Call to Action

```markdown
### Call to Action

- [Clear next steps: "Log in to start the migration wizard"]
- [Contact: "Support at support@acme.com or 1-800-ACME-HELP"]
```

## Common Pitfalls

1. **Business-centric rationale** — "Reduces our costs" → customers feel like collateral. Fix: frame around customer benefits.
2. **Vague timeline** — "Soon" creates anxiety and churn. Fix: specific dates and milestones.
3. **No support plan** — "Good luck migrating!" → abandonment signal. Fix: 1-on-1 assistance, auto-migration, discounts, training.
4. **Ignoring customer impact** — Jumping from announcement to new product. Fix: explicitly acknowledge disruption.
5. **Terse or defensive tone** — "Due to low usage, we're shutting down" blames customers. Fix: empathetic, forward-looking framing.

## References

- Crisis communication best practices — Transparency, empathy, action
- Customer success playbooks — Retention during product transitions