When deciding among re-host, re-platform, re-architect, or replace migration strategies, what factors are most critical?

• A. Team preference for cloud vendor.
• B. Downtime tolerance.
• C. Organizational readiness.
• D. Workload characteristics, dependencies, downtime tolerance, cost, risk, and organizational readiness.

Answer: (D)

Deciding how to migrate—re-host, re-platform, re-architect, or replace—depends on a holistic assessment of how a workload behaves and what the business can tolerate during the move. The best path emerges when you weigh workload characteristics, the dependencies between components, how much downtime you can accept, cost considerations, risk, and how ready the organization is to operate in the cloud.

Workload characteristics tell you what changes are feasible. Stateless apps with clean boundaries may re-host quickly, while tightly coupled, data-heavy services may benefit from re-platforming or re-architecting to take advantage of managed services and cloud-native patterns. Dependencies matter because if a workload relies on on-prem roots, licensing, or specific integration points, moving APIs, data stores, or authentication can drive the choice toward a platform or architecture change rather than a simple lift-and-shift. Downtime tolerance is critical for planning cutover windows and sequencing; some strategies allow near-zero downtime with careful design, while others require longer windows or phased migration. Cost considerations balance upfront effort, licensing shifts, and ongoing operation expenses, influencing whether you optimize for speed, control, or managed services. Risk assessment looks at security, compliance, data gravity, and potential vendor lock-in, guiding whether to standardize on proven services or embrace newer cloud-native approaches. Organizational readiness covers skills, processes, and the ability to operate and support the chosen design after migration.

When these factors are considered together, you can select the most appropriate path. If speed with minimal changes fits and dependencies are clean, re-host might be suitable. If you can gain value by moving to managed services without rewriting code, re-platforming makes sense. If you need significant architectural shifts to exploit cloud-native capabilities, re-architecting is appropriate. If a vendor-managed solution meets requirements with minimal custom work, replacement can be the best option. The comprehensive set of factors in the choice reflects why it’s the best answer, rather than focusing on a single element like downtime, vendor preference, or readiness alone.