Deprecated API Migration Consultation Script

Role: Senior Solutions Support Architect specializing in developer advocacy, API lifecycle management, and enterprise integrations.

Context

• Deprecated endpoint: {{legacy_endpoint}}
• Target replacement endpoint: {{new_api_version}}
• Customer technology stack: {{customer_integration_stack}}
• Hard sunset deadline: {{cutoff_deadline}}
• Core architectural impact: {{breaking_change_impact}}
• Canonical documentation link: {{migration_guide_url}}

Task

Generate a comprehensive technical consultation script for a 1-on-1 developer support meeting, guiding an engineering customer through retiring {{legacy_endpoint}} and migrating to {{new_api_version}} before {{cutoff_deadline}}.

Method

1. Review the architectural divergence between {{legacy_endpoint}} and {{new_api_version}} in the context of {{customer_integration_stack}}.
2. Formulate a collaborative opening that validates the customer's effort while reinforcing the security and performance drivers behind the deprecation.
3. Script a clear architectural walk-through explaining {{breaking_change_impact}} and how the modern schema prevents existing technical debt.
4. Provide spoken code-level migration instructions tailored to {{customer_integration_stack}}, highlighting exact payload adjustments.
5. Prepare firm, empathetic responses for deadline extension requests beyond {{cutoff_deadline}}.
6. Script a structured Q&A phase addressing token authentication, rate limiting, and dual-run testing strategies.
7. Conclude the consultation by confirming migration milestones and pointing to {{migration_guide_url}} for asynchronous support.

Constraints

• MUST clearly articulate that {{cutoff_deadline}} represents an absolute service shutdown unless an executive exception exists.
• MUST provide code refactoring syntax examples tailored to {{customer_integration_stack}}.
• MUST NOT offer unapproved custom reverse-proxy shims or insecure long-term workarounds.
• Pacing cues and conversational goals must be clearly annotated before each conversational section.

Output format

1. Meeting Agenda & Technical Objectives

A 4-point bulleted summary establishing call structure and mutual migration goals.

2. Spoken Consultation Script

Chronological dialogue divided into: Opening & Justification, Architecture & Breaking Changes ({{breaking_change_impact}}), Implementation Walkthrough, and Extension Pushback Handling.

3. Code Refactoring Reference Card

A dual-column markdown table contrasting a legacy request/response payload against the {{new_api_version}} format.

4. Action Item & Follow-up Ticket Template

A 100-word follow-up message containing timeline commitments, sandbox verification steps, and {{migration_guide_url}}.

Self-review

• Does the script clearly explain the necessity of migrating {{legacy_endpoint}}?
• Are code migration suggestions technically viable for {{customer_integration_stack}}?
• Does the dialogue provide firm yet respectful responses to extension demands regarding {{cutoff_deadline}}?