| name | migration-readiness |
| description | Assess whether an application is ready to migrate to OpenShift. Use when the user describes an application and asks about migration, containerization, or moving to Kubernetes/OpenShift. |
Migration Readiness Assessment
When a user describes an application for migration, follow these steps in order.
Step 1: Classify Application Type
Read the description and classify:
- Contains "stateless" or "REST API" or "web app" or "microservice" → Simple → go to Step 2
- Contains "database" or "stateful" or "persistent" or "queue" → Stateful → go to Step 3
- Contains "legacy" or "monolith" or "mainframe" or "VM-based" → Complex → go to Step 4
State the classification and the matching keywords.
Step 2: Simple Migration (Lift & Shift)
- State: "This application is a good candidate for direct migration."
- Recommend: containerize with a standard Dockerfile.
- Recommend: use a Deployment with at least 2 replicas for availability.
- Recommend: expose via Service + Route.
- Estimated effort: 1-2 sprints.
- Proceed to Step 5.
Step 3: Stateful Migration (Requires Planning)
- State: "This application requires careful data migration planning."
- Recommend: use StatefulSet instead of Deployment.
- Recommend: provision PersistentVolumeClaims for data directories.
- Recommend: plan a data migration window with rollback strategy.
- Warn: test failover behavior before production cutover.
- Estimated effort: 3-5 sprints.
- Proceed to Step 5.
Step 4: Complex Migration (Refactor First)
- State: "This application needs refactoring before migration."
- Recommend: decompose into smaller services where possible.
- Recommend: identify external dependencies (shared filesystems, host networking).
- Recommend: start with a pilot component, not the full monolith.
- Warn: budget for discovery — hidden dependencies are common.
- Estimated effort: 6-12 sprints.
- Proceed to Step 5.
Step 5: Readiness Checklist
Provide a structured summary:
- Application type: (Simple/Stateful/Complex)
- Migration strategy: (from the corresponding step)
- Estimated effort: (from the corresponding step)
- Top 3 risks: (infer from the application description)
- Next action: (first concrete step to take)
