Study SAP-C02 Migration Assessment and Wave Planning: key concepts, common traps, and exam decision cues.
Migration assessment questions are about deciding what should move, when it should move, and how much it should change. SAP-C02 rewards candidates who classify workloads before migration begins instead of throwing every application into the same wave.
| Need | Strongest first fit | Why |
|---|---|---|
| portfolio visibility and migration tracking | Migration Hub | central migration coordination |
| application-by-application migration choice | 7Rs assessment | not every workload should move the same way |
| financial migration justification | TCO analysis | cost matters to migration sequencing |
| lower-risk execution ordering | wave planning | move by dependency and risk, not random order |
| Trap | Better rule |
|---|---|
| assuming every workload should rehost first | migration path depends on value, risk, and change tolerance |
| building waves by team preference only | dependency and cutover risk should drive sequencing |
| skipping portfolio assessment | hidden dependencies break migration plans later |
| ignoring TCO | migration choices should still make business sense |
Migration-assessment questions usually hinge on dependency and treatment fit. Use Migration Hub for centralized assessment and tracking. Use the 7Rs to classify how workloads should move or change. Plan migration waves around dependencies, risk, and business sequencing. SAP-C02 rewards structured assessment over “start with the easiest app alphabetically.”