Assign the R by Component
Apply migration strategies to workload components rather than forcing one strategy onto an entire application.
Portfolio label mismatch The sheet says "rehost claims app." The architecture says web, data, reporting, and document generation each have different constraints. Component-level choices prevent both over-modernizing and under-modernizing. 7 Rs, component by component Treat the tier, not only the app Use whole-application labels for planning, but make engineering choices at the component level where constraints actually live. Shortcut One R for the whole app. The plan spends change where it creates value. Migration strategy should be as granular as the workload's real constraints. 01 Web 02 Data 03 Report Web tier Low state
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in