This guide is general information and does not replace a scoped technical, security, legal, financial, or compliance assessment.
What to examine
- Rehost for speed and limited change
- Replatform for focused operational improvement
- Refactor for deeper scalability or maintainability
- Replace when a modern product solves the need better
- Retain when migration value is not yet sufficient
- Retire systems that no longer justify cost and risk
What to do next
The right choice depends on business value, technical debt, change tolerance, dependency complexity, skills, budget, and long-term ownership—not fashion.
Recommended next step
Run a structured discovery and cloud readiness assessment before selecting target services or committing to a migration schedule.