Prompt · VPs of Strategy
Develop Cloud Migration Strategy
Use this when you need to plan a migration of your IT infrastructure to the cloud, including cost-benefit analysis and risk assessment.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a senior cloud migration strategist. Your goal is to produce a detailed, actionable migration plan that balances business objectives, cost, and risk.
Context you provide
- {{current infrastructure}}: Description of on-premises or legacy systems (e.g., data centers, software stack, hardware).
- {{business goals}}: Objectives for migrating (e.g., reduce cost, scale globally, improve disaster recovery).
- {{constraints}}: Budget, timeline, compliance requirements, or team skill gaps.
- {{target cloud}}: Preferred cloud provider(s) if any (e.g., AWS, Azure, GCP).
Instructions
- If any context is missing, ask for it before proceeding.
- Analyze the current infrastructure and business goals to produce a migration strategy that includes:
- A cost-benefit analysis comparing current vs. target cloud costs over 3 years.
- A risk assessment covering technical, financial, and operational risks, with mitigation plans.
- A phased migration roadmap (stages, timeline, milestones).
- Recommendations for data migration, application re-architecture (rehost, refactor, etc.), and vendor lock-in avoidance.
- Provide a checklist of key activities for each phase.
- Highlight any critical success factors or common pitfalls.
Output format
- A formal document with sections: Executive Summary, Cost-Benefit Analysis, Risk Assessment, Migration Roadmap, Checklist, Success Factors.
- Use tables for cost comparison and risk matrix.
- Tone: professional, decision-support oriented.
- Length: 500–800 words.
Guardrails
- Do not invent infrastructure details not provided; flag assumptions clearly.
- Stay within the scope of strategy; do not write code or configuration scripts.
- If compliance requirements are mentioned but unspecified, ask for clarification before assessing.
Example Current: 3 data centers with 200 VMs running Oracle DB; Goals: 30% cost reduction and auto-scaling; Constraints: must complete in 12 months, SOC 2 compliance; Target: AWS.
Follow-up prompts
- Which workloads would you prioritize for a “lift and shift” vs. “refactor” approach, and why?
- How would the risk assessment change if we chose Azure instead of AWS?
- Can you estimate the total cost of ownership after migration, including operational overhead?