Select workloads and processes for migration
Assess portfolio dependencies, business value, constraints, readiness, compliance, data, licensing, and operational ownership.
- Lesson
- d4-lesson
- Practice pool
- d4-questions
- Application
- sap-l06
Select workloads, sequence migration, design target architecture, manage cutover, and choose modernization opportunities from business and technical evidence.
Assess portfolio dependencies, business value, constraints, readiness, compliance, data, licensing, and operational ownership.
Choose and sequence migration strategies, tooling, waves, data transfer, testing, cutover, rollback, and stakeholder decisions.
Translate source dependencies and future requirements into a secure, resilient, operable, and cost-aware AWS target.
Evaluate managed, serverless, container, event-driven, data, integration, and operating-model changes after business constraints are understood.
Discover applications, data, infrastructure, interfaces, users, owners, contracts, licenses, performance, recovery, compliance, business windows, and upstream/downstream dependencies. Group workloads into waves that can be moved and validated coherently.
Choose retain, retire, relocate, rehost, replatform, repurchase, or refactor from business value and constraints. Rehosting can accelerate exit but preserves operational debt. Refactoring may create value but increases scope, skill, test, and cutover risk. Modernization is not automatically part of the first migration wave.
The target architecture must improve or consciously preserve identity, network, data, resilience, operations, security, performance, and cost. Define migration tooling, data synchronization, freeze windows, validation, traffic shift, reconciliation, communications, rollback, dual-operation risk, and source decommission criteria.
Modernize when a measured bottleneck and operating model justify managed, serverless, container, event-driven, decoupled, or data-platform change. Use an incremental strangler path where appropriate and deliver value before a total rewrite completes.
Create a migration wave for a stateful application with unknown dependencies and a short outage window. Explain discovery, strategy, target, data synchronization, cutover, rollback, and the modernization work you intentionally postpone.