Enterprise API Deprecation and Migration Roadmap Notice

Role: Lead Platform Product Strategist specializing in developer ecosystems and backward-compatibility governance.

Context

• Legacy component being sunset: {{legacy_api_name}}
• Modern replacement service: {{replacement_service}}
• Hard shutdown date: {{sunset_hard_deadline}}
• Customer segment impacted: {{affected_customer_tier}}
• Documentation and migration guides: {{developer_support_link}}
• Strategic business benefit: {{key_migration_benefit}}

Task

Draft a comprehensive and reassuring migration planning email directed to {{affected_customer_tier}} outlining the retirement timeline for {{legacy_api_name}}, the strategic advantages of transitioning to {{replacement_service}}, and the support resources available before {{sunset_hard_deadline}}.

Method

1. Open with an announcement of the platform lifecycle phase for {{legacy_api_name}}.
2. Highlight {{key_migration_benefit}} to frame the migration as a platform enhancement rather than an inconvenience.
3. Establish a structured milestone timeline leading up to {{sunset_hard_deadline}} (brownouts, sandbox availability, final cutoff).
4. Direct technical teams to documentation and tooling located at {{developer_support_link}}.
5. Define dedicated support channels, office hours, and migration assistance programs.
6. Detail consequences of missed migration deadlines clearly without sounding confrontational.
7. Provide unambiguous contact points for enterprise escalation.

Constraints

• MUST clearly emphasize {{sunset_hard_deadline}} in both the subject and the body text.
• MUST NOT leave technical migration requirements ambiguous or unspecified.
• Tone MUST balance technical firmness with empathetic customer partnership.
• Keep total email length under 400 words.

Output format

Subject Line: Important Planning Notice: Deprecation Schedule for {{legacy_api_name}} & Transition to {{replacement_service}}

1. Strategic Context & Performance Benefits (1 short paragraph highlighting {{key_migration_benefit}})
2. Key Transition Milestones (Bulleted timeline detailing 3 distinct dates before {{sunset_hard_deadline}})
3. Migration Resources & Developer Support (Bulleted list referencing {{developer_support_link}})
4. Required Action Items & Support Contacts (Closing summary paragraph with contact link)

Self-review

• Is {{sunset_hard_deadline}} prominently surfaced with zero ambiguity?
• Does the email frame the transition to {{replacement_service}} around customer value?
• Are links and support references cleanly formatted for quick developer uptake?