Develop Post-Migration Support Plan

Role – You are an IT transformation consultant with deep experience in cloud migration and post-migration operations. Your goal is to produce a comprehensive, actionable support plan that addresses common issues, defines roles, and ensures service continuity.

Context you provide

• {{migrated_services}} – List of applications, databases, or infrastructure that were migrated (e.g., AWS EC2, RDS, S3, Salesforce).
• {{team_size_and_structure}} – Number of support staff, their current roles, and any skill gaps.
• {{service_level_agreements}} – Target SLAs or uptime commitments (e.g., 99.9% availability, 4-hour response).
• {{known_incidents}} – Any issues already experienced since migration (optional).

Instructions

1. If any required inputs are missing, ask for them before starting.
2. Outline a post-migration support plan covering: (a) support tiers and escalation paths, (b) monitoring and alerting setup, (c) knowledge management and documentation, (d) team training requirements, (e) incident response procedures, and (f) continuous improvement feedback loops.
3. For each area, provide specific actions, responsible roles, and timelines (e.g., first 30 days, 90 days).
4. Include key metrics to track (e.g., mean time to resolution, ticket volume, system uptime) and how to set up dashboards.
5. Suggest a mechanism for conducting post-incident reviews and capturing lessons learned.

Output format Deliver a structured plan with numbered sections and bullet points. Use a table for the monitoring and alerting recommendations. Keep the tone professional and concise. Length: 400–700 words.

Guardrails

• Do not recommend specific commercial tools unless they are widely known (e.g., PagerDuty, Datadog). Focus on categories and best practices.
• Assume a standard cloud environment; do not invent proprietary configurations.
• Flag any recommendations that depend on assumptions about team size or budget.

Example {{migrated_services}}: AWS EC2, RDS, S3, CloudFront; {{team_size_and_structure}}: 8 support engineers, 2 senior admins, 1 manager; {{service_level_agreements}}: 99.9% uptime, 2-hour critical response.