SAP S/4HANA Migration · Migration Scenarios: Greenfield, Brownfield & Selective

You must keep a system's business downtime as short as possible during conversion. Do you pick the standard or the downtime-optimized procedure, and what do you pay for it?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Migration Scenarios: Greenfield, Brownfield & Selective

A customer's ERP source system still runs on Oracle, not HANA. Does that block a system conversion to S/4HANA, and what handles the database side?

SAP splits a migration into Preparation, technical implementation, and process adaptation. Where do prechecks/preconversions run, and why does that placement matter?

When you use a migration object in the cockpit, which fields does it activate by default, and what's the trap for someone who assumes a full field set?

A stakeholder calls the project a 'brownfield' migration. Which SAP scenario is that, and what concretely survives the move?

A customer wants SaaS/cloud S/4HANA but is leaning toward a brownfield conversion. What constraint do you have to flag?

What is the core trade-off that should drive the choice between keeping the old system vs starting fresh in an S/4HANA migration?

Start learning today

Free to start — download the app or use it in your browser.