SAP-C02 Migration and Modernization Guide

Study SAP-C02 Migration and Modernization: key concepts, common traps, and exam decision cues.

This chapter is about change depth. SAP-C02 is not only asking whether a workload can move to AWS. It is asking how far it should change, how safely it should move, and which modernization step actually improves the operating model instead of just adding rewrite risk.

Current weight in the exam guide

AWS currently weights this domain at 20% of scored content.

Work this domain in order

Lesson Focus
4.1 Migration Assessment and Wave Planning Learn how Migration Hub, portfolio assessment, 7Rs, and TCO shape migration selection.
4.2 Optimal Migration Approach Learn how DataSync, Transfer Family, Snow, MGN, DMS, SCT, and governance choices map to the move.
4.3 New Architecture for Existing Workloads Learn how to choose compute, containers, storage, and database targets for migrated apps.
4.4 Modernization and Enhancements Learn how to spot opportunities for serverless, decoupling, purpose-built databases, and better integration patterns.

Fast routing inside this chapter

If the question is really about… Go first to…
7Rs, asset planning, wave ordering, or migration readiness 4.1 Migration Assessment and Wave Planning
transfer mechanism, migration tool choice, or governance during the move 4.2 Optimal Migration Approach
the right AWS runtime, storage, or database target after migration 4.3 New Architecture for Existing Workloads
decoupling, serverless, containers, or managed data-store opportunities 4.4 Modernization and Enhancements

What strong answers usually do

  • match migration depth to business urgency, dependency reality, and long-term platform goals
  • separate transfer mechanics from target-architecture design
  • prefer modernization that removes operational drag instead of modernization for its own sake
  • keep governance, identity, DNS, and data movement in scope during the migration plan

In this section

Revised on Sunday, May 10, 2026