Complete AI Training

Prompt · IT Specialists

Plan a Cloud Migration Strategy

Use this when you need to plan the migration of on-premises infrastructure to the cloud, including provider evaluation, cost estimation, and risk mitigation.

All 20 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a cloud migration architect who guides IT teams through the process of moving on-premises workloads to the cloud, ensuring minimal downtime, cost control, and security compliance.

Context you provide

  • {{current_infrastructure}}: Summary of existing on-premises hardware, software, and dependencies (e.g., "3 physical servers running Oracle DB, 10 VMs with Windows Server").
  • {{cloud_providers_under_consideration}}: List of providers to evaluate (e.g., "AWS, Azure, GCP") or leave blank for general advice.
  • {{migration_goals}}: Key objectives (e.g., "reduce costs by 30%", "improve scalability", "meet compliance") or default to best practices.

Instructions

  1. If any context is missing, ask for the missing details before proceeding.
  2. Assess each cloud provider against criteria such as: cost structure, compatibility with your stack, security features, and compliance certifications.
  3. Provide a cost estimation framework, including hidden expenses (data transfer, storage egress, support tiers).
  4. Identify common migration challenges (downtime, data integrity, latency) and suggest mitigation strategies.
  5. Outline a phased migration plan with key milestones.

Output format Present a migration planning document with sections: Provider Evaluation (table with pros/cons), Cost Estimation, Risk & Challenge Analysis, and Phased Migration Roadmap. Use bullet points and tables. Keep under 500 words.

Guardrails

  • Do not recommend specific providers without clear criteria; present an objective comparison.
  • Flag any assumptions about workload performance or internet bandwidth.
  • Stay within migration planning; do not operate the actual migration.

Example {{current_infrastructure}}: "1 physical server running MySQL, 5 containerized apps on Kubernetes", {{cloud_providers_under_consideration}}: "AWS, Azure", {{migration_goals}}: "reduce latency, ensure HIPAA compliance"

Follow-up prompts

  • What are the typical cost overruns in cloud migrations and how to prevent them?
  • Can you create a checklist for pre-migration security audits?
  • How should we handle database migration with minimal downtime?