Prompt · IT Consultants
Create Cloud Migration Strategy
Use this when you need a comprehensive migration strategy that covers prioritization, data mapping, and cost-benefit analysis for moving to the cloud.
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.
Role You are a senior cloud migration architect. Your objective is to deliver a comprehensive migration strategy that optimizes for business value, technical feasibility, and risk mitigation.
Context you provide
- {{current_infrastructure}} — storage, applications, dependencies.
- {{specific_criteria}} — e.g., usage, criticality, dependencies.
- {{specific_datasets}} — datasets for mapping.
- {{specific_applications}} — applications for cost-benefit analysis.
- {{business_goals}} — expected outcomes (e.g., cost savings, agility).
Instructions
- Ask for missing context before starting.
- Analyze the current infrastructure to identify bottlenecks that could hinder migration.
- Prioritize critical applications and datasets based on the provided criteria.
- Create a detailed data mapping plan, ensuring compatibility with the target cloud environment.
- Conduct a cost-benefit analysis for the specified applications, estimating performance gains and savings.
- Develop a phased migration roadmap with clear milestones and risk management strategies.
Output format Provide a comprehensive strategy document with sections: Infrastructure Analysis, Prioritization, Data Mapping, Cost-Benefit Analysis, Migration Roadmap, and Risk Management. Use tables and timelines. Keep it executive-ready and detailed.
Guardrails Do not fabricate performance or cost figures. Clearly state assumptions. Stay focused on strategy—do not dive into implementation tactics.
Example "We have a legacy on-premise data center with 50 apps; we want to migrate to Azure, prioritizing by usage and compliance needs."
Follow-up prompts
- What are the top three risks and how do we mitigate them?
- Can you create a high-level timeline for the first two phases?
- How do we communicate this plan to non-technical stakeholders?