Why the Path You Choose Has Major Commercial Consequences
The choice between Greenfield, Brownfield, and RISE with SAP (Cloud ERP Private) is not purely a technical decision. It determines your licensing structure for the next decade, your contractual obligations to SAP, the pace at which SAP can increase your costs, and your ability to negotiate competitive commercial terms.
SAP's sales organisation is heavily incentivised to direct customers toward RISE with SAP (now Cloud ERP Private). RISE generates higher average contract values, longer lock-in, and carries infrastructure margin that on-premise or third-party hosted migrations do not. This incentive structure creates a systematic conflict of interest between SAP's commercial objectives and the objective analysis each customer needs.
Want an Independent View of Your SAP Position?
Our advisors are former SAP insiders working exclusively for enterprise buyers. A free 30-minute discovery call will tell you whether independent advisory would materially change your commercial outcome.
Book a Free Consultation → Download Free SAP Audit Guide →Our S/4HANA migration licensing advisory team provides independent analysis of migration path commercial implications without any alignment to SAP's preferred outcome.
The best SAP ECC-to-S/4HANA migration deals are signed when the customer has genuine time and alternatives. As the 2027 deadline passes, SAP's account teams know that customers face extended maintenance fees or migration costs regardless — which reduces their urgency to offer competitive terms. If you have not started your commercial analysis, start now. See our article on why 2026 is the best year in a decade to negotiate with SAP.
Path 1: Greenfield — New Implementation on S/4HANA
Greenfield: Start Clean on S/4HANA
A Greenfield implementation starts from scratch on S/4HANA — new system configuration, new processes, new master data. Your ECC landscape is decommissioned after go-live. Nothing from the old system is technically carried across, though data migration is a significant project component.
Licensing implications: Greenfield means building a new Effective License Position (ELP) from scratch. You need S/4HANA user licences, engine licences, and any add-on products required for your new system. Your existing ECC perpetual licences may have some residual value as conversion credits, but this must be explicitly negotiated — SAP does not automatically apply perpetual licence value to a new S/4HANA purchase.
Commercial advantage: Greenfield gives you the cleanest negotiating position of the three paths. You are buying a new system from scratch, which means you can run a genuine competitive evaluation (including non-SAP alternatives), benchmark pricing independently, and structure the deal entirely on your terms. This commercial leverage disappears in Brownfield and RISE scenarios where your existing landscape constrains your choices.
Commercial risk: Greenfield projects are expensive and long. Implementation costs for a large enterprise can reach eight figures. The implementation risk is significant — SAP projects of this scale regularly overrun. Factor full risk contingency into your business case and ensure your contract addresses project failure scenarios.
Path 2: Brownfield — System Conversion to S/4HANA
Brownfield: Convert Your Existing ECC System
A Brownfield conversion (also called a system conversion or "lift and shift with simplification") converts your existing ECC system directly to S/4HANA. Your customisations, configuration, and data are carried across. SAP's Software Update Manager (SUM) with the Database Migration Option (DMO) handles the technical conversion.
Licensing implications: Brownfield is the most commercially complex migration path from a licensing perspective. Your existing ECC user types do not map directly to S/4HANA user types. SAP will conduct a licence reclassification exercise during which your current user base will be assessed against S/4HANA user type definitions — and the result is almost always an increase in licence cost. Users who held Limited Professional licences in ECC may need Professional licences in S/4HANA due to role changes driven by the new system. This delta licence cost must be quantified, challenged, and negotiated before you commit to the conversion path.
Commercial advantage: Brownfield is faster and less disruptive than Greenfield. Your existing ECC perpetual licences retain value through the conversion — you are upgrading rather than replacing, which gives SAP less room to argue you need an entirely new licence structure.
Custom code risk: Brownfield projects require extensive custom code analysis. SAP's custom code compatibility tooling identifies ECC custom code that will not run on S/4HANA. The cost and time to remediate custom code is frequently underestimated and becomes a major project risk. Understand your custom code volume before committing to a Brownfield timeline. Our guide to custom code migration licensing implications is relevant reading.
Path 3: RISE with SAP / Cloud ERP Private — Managed Cloud Migration
RISE / Cloud ERP Private: SAP Manages the Infrastructure
RISE with SAP (rebranded as SAP Cloud ERP Private in July 2025) is SAP's bundled offering: S/4HANA software, managed cloud infrastructure, and SAP Enterprise Support under a single subscription contract. SAP manages the infrastructure on a hyperscaler of SAP's choosing. The customer migrates their ECC processes into S/4HANA on this managed environment.
Licensing implications: RISE represents the most fundamental change to your SAP commercial relationship of the three paths. You move from perpetual licences (owned in perpetuity, with annual maintenance) to a subscription model (no ownership, annual subscription fee tied to SAP's commercial terms at renewal). Your existing perpetual licences may be used as conversion credit, but the terms of that conversion — including the credit value SAP attributes to your existing licences — are highly negotiable.
Lock-in risk: RISE / Cloud ERP Private involves the deepest lock-in of the three paths. Once your data and processes are in SAP's managed cloud environment, your switching cost is significant. SAP's commercial team knows this and will seek to lock in pricing terms at the lowest negotiating pressure point — which is when you are most committed to the path and least willing to walk away. Independent advisory before contract signature is essential. See our guide to RISE hidden costs for the full picture.
What SAP does not tell you: RISE includes BTP credits that the majority of customers never fully consume. The infrastructure sizing in the initial proposal is frequently over-provisioned. SAP's RISE SLAs are written to SAP's benefit, not the customer's. All of these are negotiable — but only before signature.
The Licensing Commercial Comparison
From a pure commercial standpoint, the three migration paths have different long-term cost profiles:
- Greenfield on-premise or hosted: Highest upfront implementation cost, but lowest ongoing cost if you manage your own infrastructure and negotiate perpetual licences. Full commercial control at every renewal point. Requires significant internal technical capability.
- Brownfield on-premise or hosted: Lower upfront cost, but licence reclassification at conversion often negates the savings. Good commercial control, but custom code remediation can be expensive and time-consuming.
- RISE / Cloud ERP Private: Bundled pricing is easier to budget, but the total five-year cost including renewal escalation typically exceeds Greenfield or Brownfield on a like-for-like basis. The infrastructure margin SAP earns adds 20–40% to the total cost versus self-managed hosting.
During migration — regardless of path — many organisations run ECC and S/4HANA in parallel for an extended period. SAP's standard licence position is that both systems require full licensing during the parallel run. This parallel landscape cost is frequently not included in migration business cases and can represent a significant unbudgeted expenditure. Our guide to SAP ECC-to-S/4HANA parallel landscape licensing covers how to negotiate this issue.
How to Use the Migration Decision as a Negotiation Lever
The period between initiating the migration decision and signing the contract is the single best opportunity most organisations will ever have to renegotiate their entire SAP commercial relationship. SAP's account team is highly motivated to close the migration deal — it represents one of the largest bookings in their pipeline.
Use this motivation to negotiate: a better per-FUE or per-user rate, favourable conversion credit terms for existing perpetual licences, capped renewal escalation, reduced maintenance on any retained on-premise components, extended payment terms, and favourable RISE SLAs if that path is chosen. Our SAP contract negotiation service is designed specifically for these high-stakes migration negotiations.
The leverage disappears after signature. Engage independent advisors before you commit.
Still Running SAP ECC? Get an Independent Migration Commercial Assessment
Our team provides independent analysis of all three migration paths, including a commercial comparison for your specific ECC landscape, licence volume, and budget. We have no incentive to direct you toward RISE — our only interest is your commercial outcome.
Book a Free ECC Migration ReviewRelated Guides
- SAP ECC End of Maintenance 2027: What to Negotiate
- SAP ECC Extended Maintenance to 2030 and 2033: Is It Worth Paying?
- SAP ECC 2027: The 12-Month Action Plan
- SAP S/4HANA Cloud vs On-Premise Licensing: 2026 Cost & Risk Comparison
- SAP ECC to Cloud Conversion Credits: How to Maximise Value
- Our S/4HANA Migration Licensing Service