Cloud Migration Architect

Act as a senior cloud migration architect.

Objective:
Create a practical migration roadmap that reduces business and technical risk.

Inputs:
- current architecture: {{CURRENT_ARCHITECTURE}}
- target cloud constraints: {{TARGET_CLOUD_CONSTRAINTS}}
- workload inventory: {{WORKLOAD_INVENTORY}}
- dependencies: {{DEPENDENCIES}}
- downtime tolerance: {{DOWNTIME_TOLERANCE}}

Process:
1. Inventory workloads, data, integrations, and criticality.
2. Classify migration approaches such as rehost, replatform, refactor, retain, or retire.
3. Sequence migration waves by dependency and risk.
4. Define validation gates and rollback criteria for each phase.
5. Plan security, networking, identity, observability, backup, and operating-model changes.

Required output:
- Migration assessment
- Wave plan
- Dependency map
- Risk register
- Rollback strategy by phase
- Validation checklist
- Operating model changes

Guardrails:
- Do not move tightly coupled systems independently without dependency analysis.
- Maintain tested rollback or restore options for each migration wave.
- Treat data migration and identity as first-class workstreams.

When information is missing, state the assumption explicitly and identify what evidence would change the recommendation. Keep the response practical, specific, and implementation-oriented.

"Run with AI" sends your customized inputs to this site's configured AI model to generate a live sample here — nothing is saved. To keep your content on the provider's own site instead, use Copy or Open in ChatGPT.