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?

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?

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?

Technical system conversion finishes successfully. A manager asks whether the new S/4HANA functions are now live. What's the honest answer?

A system conversion has three technical steps: DB to HANA, repository import, data conversion. Why can't you reorder the last two?

Why is selective data transition treated as its own scenario rather than a flavor of conversion, and why can a customer rarely run it alone?

What exactly are 'migration objects' in the S/4HANA migration cockpit — and what's wrong with thinking of them as blank templates you build?

A stakeholder calls the project 'greenfield.' Which SAP scenario is that, and what does it technically rest on?

Before a system conversion, which tool sets the target version and prepares the conversion software — and don't confuse it with the new-implementation installer?

In a new implementation you must load legacy data. What tool does it, and what's the key capability that decides whether it fits a non-SAP source?

What are the three migration scenarios to SAP S/4HANA defined by SAP?

In a new implementation, which tool installs the S/4HANA system, and what does the resulting SID tell you about whether this was a conversion?

After SWPM installs a new S/4HANA system in a greenfield project, what state is its configuration in, and how does that shape the next phase?

When can inserting an intermediate step to SAP S/4HANA Finance make sense instead of going straight to full SAP S/4HANA?

For a decentralized SAP ERP landscape you want to consolidate while moving to S/4HANA, what three broad approaches does SAP outline?

A customer insists on SAP S/4HANA Cloud, public edition. What does that single decision lock in about the available migration scenarios?

Beyond redesigning processes, what data-quality payoff does a greenfield new implementation offer that an in-place conversion cannot?

Sizing a new-implementation landscape, an architect plans only the ABAP instance and assumes Fiori comes with it. What's missing, and why is that a landscape-planning error, not just a config step?

A colleague still calls the third migration scenario 'landscape transformation' and treats it as one fixed procedure. What is outdated in both of those assumptions?

Why would a company consolidate several SAP ERP systems into a single SAP S/4HANA system instead of keeping them separate and replicating data between them?

In a landscape transformation, what are the two subprojects, and which scenario prepares the 'master system' before any selective data is moved?

Selective data transition normally assumes at least one SAP ERP source system. Can the approaches handle a non-SAP source, and what tool comes into play if so?

How does the state of your source system decide whether all three migration scenarios are even on the table?

A team assumes it must first harmonize all its SAP ERP systems before it can move to S/4HANA. Why is that usually the wrong instinct?

Unlike a new implementation or a system conversion, a customer usually cannot run a selective data transition in-house. What technical reason forces SAP experts into the loop?

For a single central system whose current processes still fit the business, why is a system conversion usually the default, and often the fastest route to S/4HANA?

What does a 'consolidation based on a leading configuration' use as its template, and what is the end goal?

In a system-conversion-based consolidation of several SAP ERP systems, which system do you actually convert, and what gets pulled from the rest?

How does running one central SAP ERP system versus a decentralized landscape change which migration scenarios you can consider?

If the main goal is to return heavily customized developments to the SAP standard, which scenario is usually preferable — and is the other one strictly ruled out?