Migration Strategy, Frameworks & Discovery

A customer drops SAP CRM and adopts Salesforce instead. Why is this repurchasing and not replatforming, even though both involve a new system?

Name all six perspectives of the AWS Cloud Adoption Framework (CAF). Which one is most often forgotten, and what fails if it is?

Migrating SAP from Oracle to HANA on AWS: is that rehosting or replatforming, and what single fact decides it?

Teams lift-and-shift to AWS planning to right-size 'later'. Why does this usually backfire on cost rather than just deferring savings?

How can you tell you are still in the MAP Assess phase and not yet in Mobilize — what is the deliverable that marks Assess as done?

Application discovery for an SAP migration has confirmed instance counts and DB sizes. Which single question, if unanswered, can silently reclassify the migration's R-strategy?

You need to map which SAP systems talk to which before grouping migration waves. Agentless or agent-based discovery — and what does the wrong pick cost you?

In the MAP Migrate phase (DEV > QA > PRD), the go-live assessment runs in QA only — not PRD. Why is it deliberately not run in PRD?

AWS ADS costs nothing to run. What is the minimum collection window before you trust its data for SAP sizing, and what's the failure if you cut it short?

SAP Quick Sizer gives you a capacity recommendation. Should you add your own safety buffer on top of it? What does the 65% figure tell you?

How do you recognize the MAP Mobilize phase versus Migrate — what is built and validated, and what is deliberately NOT yet done?

In the CAF flywheel, a stakeholder asks for the prioritized list of capability gaps and the action plan. Is that an Envision or an Align output, and why does the order matter?

Your SAP LMDB has a clean inventory of every SAP system. Why is it still insufficient for a data-center-exit migration that includes non-SAP workloads?

How many phases does AWS MAP actually have, and where do people go wrong by adding a 'run/optimize' phase?

A sponsor freezes the SAP migration go-live date (Timeline) but later doubles the Scope. Among Scope / Timeline / Strategy, why can't you change one in isolation?

List all 6 Rs of AWS migration strategy.

An SAP Migration Readiness Assessment (MRA) returns several capabilities marked yellow rather than green. What does yellow mean, and does it block the migration?

When right-sizing SAP for AWS, why is the on-prem server's allocated CPU/RAM the wrong number to size from — and what number is right?

AWS ADS recommends an m6g instance for one of your servers. Before accepting it for an SAP workload, what must you check, and why can't ADS make this call alone?

For sizing, when do you reach for SAP Quick Sizer versus EarlyWatch Alert + SAPS rating? What distinguishes the two situations?

You're about to kick off wave 1 of an SAP migration. How many waves ahead should you have planned, and what goes wrong if you only plan the current one?

In a data-center-exit SAP migration, where in the timeline do you place SAP production systems, and why not migrate them first to de-risk early?

Why must application portfolio discovery come before you apply the 6 Rs, TCO, and target architecture — not after?

Among owner questionnaires, CMDB/LMDB exports, vCenter exports, and APM data, which discovery source is the LEAST trustworthy for sizing — and why is the CMDB not the safe default?

At what landscape size does a 'big-bang' single-wave SAP migration stop being appropriate, and in what order do you move systems within it?

An SAP app server runs on a VM while its database sits on physical hardware. Which of the four dependency categories is this, and how is it different from application-to-infrastructure?

Why should the SAP global transport file system (and a Solution Manager running ChaRM) be moved during the production wave rather than an early non-prod wave?

It seems obvious to migrate the highest-priority applications first. Why does this usually fail in practice during wave planning?

An SAP S/4HANA app server is an r6i.2xlarge (8 vCPU, 64 GB) but ADS shows peak of 25% vCPU and 40% RAM. What do you downsize to, and what must you confirm before committing?

In attribute-based scoring for migration prioritization, what does the importance/relevance factor add on top of per-value scores, and why isn't equal weighting enough?

A typical SAP rehosting migration to AWS runs 6–9 months. What external event most often forces that timeline shorter, and why does it change your negotiating room?

Two SAP systems are integrated. One pair (app server + its DB) must migrate together; another (ERP and BW over RFC) need not. What property decides 'migrate together'?

Two SAP migration plans are identical except one keeps the same hostnames after moving to AWS and one changes them. Which needs the longer timeline, and why?

What server-count progression is recommended across SAP migration waves, and why not just run every wave at the 500-server maximum to finish faster?

Can non-production and production SAP systems share a migration wave, and must a heavily-shared database server move in the same wave as its apps?

Application prioritization runs in both the Assess and Mobilize phases. How do the ranking criteria differ, and what goes wrong if you swap them?

What is the atomic unit a migration wave is built from — and why can't you balance waves by simply splitting servers evenly across them?

A CCoE task is 'build communities of practice and bridge skill/knowledge gaps'. Which of the three CCoE pillars owns it, and how is that pillar distinct from the other two?

Why is a CCoE described as 'multilingual', and what misconception about it does that label correct?

If you measure a CCoE on how quickly and efficiently it adopts new technology, what failure mode do you create?

Rehosting SAP as-is to AWS is the lowest-effort R. What is its built-in downside, and when is 'carry it over unchanged' actually the right call?

For a homogeneous (rehost) SAP migration to AWS, which SAP-native and AWS accelerators are available, and why does homogeneity widen the toolset?

'Lift, tinker, and shift' — what scenarios count as replatforming an SAP system, and what extra effort does the heterogeneous path add over a pure rehost?

The AWS CAF migration is an iterative flywheel of four phases. After Envision and Align, what do the Launch and Scale phases each deliver for an SAP program?

Beyond vCPU, memory, and storage, what application metadata must current-state discovery capture to assign the right R and target architecture per SAP system?

When is an automated discovery tool like AWS ADS overkill for an SAP migration, and when does it become essential?

Right-sizing and dependency mapping both depend on one upstream artifact from discovery. What must a fact-based SAP application inventory actually capture to be usable?

Migration Evaluator gave you right-sized AWS cost projections. Why can't you build your migration wave plan from it directly?

SAP is one of the most highly integrated enterprise applications. In migration planning, what artifact do long-running SAP shops build around integration, and how must each interface be characterized?

You're outsourcing an SAP-on-AWS migration and its ongoing managed services to a system integrator. What two credentials must that partner hold for full SAP + AWS supportability?

AWS frames decisions as one-way vs two-way doors. Applied to migration strategy, what makes a single strategy for critical SAP systems risky, and what's the reversible fix?

In an assess-phase prioritization matrix built to move non-production first, how are the SAP-environment values scored, and how do you pull an eager business unit's apps to the top?

When scoping how much downtime an SAP cutover can afford, why isn't a single 'downtime' number enough — what two kinds must you separate?

A team wants to relocate (hypervisor lift-and-shift) their SAP production VMs running on VMware straight onto AWS to save effort. Why is this the wrong R for SAP?

Before a production SAP cutover on AWS, what should you rehearse repeatedly, and why run HA/DR drills both with and without data?

Replatforming SAP-on-Oracle to AWS forces one mandatory OS move. Which OS, and what cost catches teams who assume 'it's free'?

In SAP terms, refactoring isn't just re-architecting for the cloud. What does it actually mean, and what are the two transition styles?

A cloud architect is asked 'what kind of high availability does the cloud offer?' before anyone has stated an uptime requirement. Why is answering that the wrong way to start an SAP migration?

When building the cloud cost case for SAP, teams instinctively map each on-prem server to an equivalent cloud instance. Why does AWS say that's the wrong comparison?

AWS gives three guiding principles for migrating any application to the cloud. What are they, and how can a compliance requirement turn into an application change under one of them?

When picking which applications to decommission during an SAP cloud migration, why start from the business process rather than the application's function?

To cut cutover downtime, a team plans database replication between on-prem and AWS. What cost does that carry, and what general trade-off does it illustrate?

While an SAP migration is under way, why must the schedule budget for ongoing operational and development effort — and what dates must it explicitly respect?

SAP-to-AWS migration drivers split into business and technical. Give the most common of each — and the hard technical deadline that often forces the timeline.

Why does SAP's 2027 support commitment push customers toward S/4HANA now, and what low-disruption on-ramp do some pick to start on AWS?

Of the six Rs, only two are described as specifically applicable to SAP migrations to AWS. Which two, and what source-database condition triggers the second?

The book calls AWS CAF 'an algorithm with variables.' What does that mean, and what value chain do its transformation domains form?

You've mapped SAP application-to-component and application-to-infrastructure dependencies. Which two of the four dependency categories do teams routinely miss, and what's a concrete example of each?

After scoring your application portfolio for migration priority, what should the score distribution look like, and where do the scoring templates come from?

When mapping dependencies for wave planning, which relationships are high priority to keep together in one wave, and which connections are explicitly not binding?

Wave planning generally moves risky, complex systems later, so why might an app running on end-of-life Windows 2008 get pulled into an earlier wave instead?

How many applications make a good migration pilot, and what one workload must it include for an SAP program?

A wave plan is more than dependency groups. Beyond dependencies, what dimensions can define a wave's boundaries, and what nontechnical dates can force its timing?

SAP splits migrations into homogeneous and heterogeneous. What draws the line, and how do rehost / replatform / refactor map onto it?

What size qualifies a database as 'large' for SAP-on-AWS migration planning, and what method keeps technical downtime minimal when the OS/DB don't change?

You're keeping the same database and only changing the OS, so it's homogeneous and you can just backup/restore. When is that assumption wrong?