SAP S/4HANA Licensing Migration Paths: Greenfield, Brownfield, and Bluefield Compared

The Migration Path Decision and Its Licensing Consequences

SAP customers migrating from ECC or earlier SAP platforms face a fundamental architectural decision before any technical work begins: which migration path to take. The choice is consequential beyond the implementation programme itself — it shapes the commercial negotiation, determines which legacy licence liabilities survive into the S/4HANA environment, and affects the long-term cost of ownership in ways that are not apparent from implementation project plans alone.

The three primary migration paths are greenfield (new implementation), brownfield (system conversion), and bluefield (selective data transition, sometimes called hybrid or shell conversion). A fourth emerging option — RISE with SAP — adds a cloud deployment dimension but is not itself a migration methodology; it can be combined with any of the three technical approaches. Understanding how each path affects licensing — not just implementation — is essential for building a complete business case and negotiating effectively with SAP.

Greenfield Migration: The Clean Slate and Its Commercial Implications

A greenfield S/4HANA implementation starts from scratch. The organisation provisions a new S/4HANA environment, configures it based on current business requirements and SAP best practice, and migrates only the data needed to support operations in the new system. Legacy ECC customisations are reviewed and either remodelled in S/4HANA or replaced by standard functionality. The result is a clean, modern S/4HANA deployment without the accumulated technical debt of the previous environment.

Licensing Advantages of Greenfield

Greenfield migrations carry the strongest commercial negotiation leverage of the three paths. When an organisation is building an entirely new S/4HANA environment, it is making new licence commitments from a position of genuine choice — it is not constrained by an existing system configuration or a need to preserve specific functional capabilities. This translates directly into negotiation posture: the organisation can credibly negotiate the full scope of S/4HANA licences, functional add-ons, HANA database sizing, and digital access entitlements as a fresh commercial transaction.

In practice, SAP sales teams respond more aggressively to greenfield opportunities because the revenue potential is larger and the competitive risk (from other ERPs) is more credible. Discount levels achievable on greenfield negotiations are typically 10 to 15 percentage points higher than on brownfield conversions, where the commercial situation is more constrained. We have advised greenfield customers to achieve 40 to 50 percent discount from SAP list pricing when the negotiation was properly prepared and competitive alternatives were credibly presented.

Licensing Risks of Greenfield

The primary licensing risk in greenfield migrations is scope underestimation. Because the implementation starts clean, there is a tendency to scope the initial licence purchase around expected go-live functionality rather than the full deployment roadmap. SAP may agree to a lower initial licence cost on this basis, but subsequent expansion — adding business units, geographies, functional modules, or digital access entitlements post-go-live — is invariably more expensive than if the same scope had been negotiated upfront. The lesson from greenfield advisory work is clear: negotiate the full programme scope in the initial agreement, even if deployment is phased, to lock in the best commercial terms before you are committed to the platform.

Brownfield Migration: System Conversion and Inherited Liabilities

Brownfield migration — formally called System Conversion in SAP's methodology — converts the existing ECC system in place to S/4HANA. The technical database and application stack is upgraded, core configuration is retained, historical data is preserved, and customisations are assessed for compatibility. The result is an S/4HANA system that retains the organisation's operational continuity while gaining the architectural benefits of the new platform.

Brownfield is the most commonly chosen path, selected by approximately 40 percent of SAP migration projects, because it minimises business disruption and change management demands. For organisations with complex, deeply customised SAP landscapes — common in manufacturing, utilities, and financial services — brownfield is often the only practically viable path.

Licensing Implications of Brownfield

The critical licensing characteristic of brownfield conversion is that it inherits the commercial terms of the existing ECC agreement. This includes both the assets (existing licence entitlements, negotiated discount levels, maintenance fee rates) and the liabilities (unresolved indirect access exposure, under-licensed user types, oversized or incorrectly classified licence populations). A brownfield migration that proceeds without a pre-conversion licence audit is effectively carrying legacy compliance risk forward into the new environment — and SAP's audit team is aware that conversions create opportunities to regularise the licence position.

The discount leverage in a brownfield negotiation is lower than greenfield, because the organisation has already committed to the SAP platform and the conversation is about conversion terms rather than new licence selection. However, the migration creates a natural commercial moment that can be used to negotiate improvements — particularly on maintenance rate (seeking to hold or reduce the 22 percent Enterprise Support rate), on digital access terms (locking in document pricing before post-go-live expansion triggers additional fees), and on add-on engine pricing (negotiating EWM, TM, and other engine costs before they are needed operationally).

Conducting a Pre-Brownfield Licence Audit

We strongly recommend a structured licence audit before beginning any brownfield technical planning. The audit should map the current licence entitlements (by user type, by module, by metric) against actual system usage, identify user populations that are over- or under-classified, quantify any indirect access exposure from existing integrations, and document the HANA database requirements of the converted S/4HANA environment (which may differ significantly from the existing ECC database sizing).

The audit findings create both a risk reduction outcome (resolving compliance issues before migration, under commercial terms more favourable than post-audit findings) and a negotiation asset (demonstrating to SAP that the conversion includes a rationalised, audited licence position rather than an inflated ECC entitlement carrying forward into S/4HANA).

Bluefield Migration: Selective Data Transition and Licence Rationalisation

The bluefield approach — sometimes called shell conversion or selective data migration — combines elements of both greenfield and brownfield. The technical approach builds a new S/4HANA environment (as in greenfield) but uses SAP's migration tooling to selectively transfer configuration, master data, and transactional data from the existing ECC system. Organisations can choose to migrate only relevant data — for example, open items, current master data, and recent transaction history — while leaving legacy and archived data in the old system or an archive solution.

Bluefield was developed as a middle path for organisations that found greenfield too disruptive (requiring complete configuration rework) but brownfield too limiting (carrying forward technical debt they wanted to eliminate). The methodology has matured significantly, with specialised tools from SAP and third parties (notably SNP Group's Bluefield methodology) supporting selective data transfer at scale.

Licensing Implications of Bluefield

Bluefield's selective approach creates a valuable licence rationalisation opportunity. Because the organisation is building a new technical environment and migrating only the data it needs, it has the opportunity to right-size the licence entitlement at the point of transition. User populations can be re-assessed and re-classified based on actual S/4HANA role requirements rather than inherited ECC assignments. Modules that were licensed but not actively used in ECC can be excluded from the S/4HANA migration scope, removing future maintenance obligations. Indirect access exposure from legacy integrations can be formally addressed as part of the migration agreement rather than inherited.

This rationalisation potential makes bluefield commercially attractive, particularly for organisations that suspect their ECC licence estate is over-sized or incorrectly classified after years of organisational change, mergers, and system evolution. The negotiation leverage is intermediate between greenfield (full flexibility, highest discount potential) and brownfield (continuity, lower discount room) — bluefield provides the flexibility to right-size while retaining some of the negotiation simplicity of a conversion approach.

RISE with SAP: Cloud Deployment Across All Migration Paths

RISE with SAP is SAP's cloud migration bundle — a subscription that combines S/4HANA software, cloud infrastructure (hosted by SAP or a hyperscaler), Business Technology Platform (BTP) access, and managed services under a single annual fee. RISE is not a migration methodology; it is a commercial and technical deployment framework that can be applied to greenfield, brownfield, or bluefield migration approaches.

The commercial logic of RISE is to simplify the procurement conversation: instead of separate application licences, HANA database licences, infrastructure procurement, and support arrangements, the customer purchases a unified subscription. This simplification is genuine to some extent, but it does not eliminate the add-on licensing complexity described in our S/4HANA hidden costs analysis. EWM, TM, Digital Access, and other functional add-ons must still be separately negotiated within the RISE framework.

The most important RISE negotiation consideration is the subscription term and annual pricing escalation. RISE contracts are typically three to five years, with annual price increases in the range of 2 to 4 percent tied to CPI provisions. The initial RISE subscription fee is the baseline from which all future costs escalate, making the first-year price the most important commercial negotiation point. Organisations that accept SAP's first RISE proposal without negotiation typically pay 20 to 35 percent more than those who engage with independent advisory support and benchmark the pricing against market reference data.

Choosing the Right Path: A Decision Framework

The right migration path depends on the intersection of implementation complexity, organisational appetite for disruption, legacy licence liability, and commercial negotiation objectives. Greenfield is the right choice for organisations that are prepared to invest in a full implementation programme, want maximum licensing flexibility, and have either a relatively standard SAP landscape or a strong commitment to adopting standard S/4HANA processes. It provides the highest discount potential and the cleanest commercial starting point.

Brownfield is appropriate when operational continuity is paramount, the existing SAP landscape is complex and heavily customised, and the organisation lacks the change management capacity for a full reimplementation. The key requirement is conducting a thorough licence audit before migration to ensure legacy liabilities do not transfer forward on unfavourable terms.

Bluefield suits organisations that want the rationalisation benefits of a new environment without the full scope of a greenfield implementation — particularly those with a complex, over-sized, or incorrectly classified ECC licence estate that represents a genuine optimisation opportunity. The selective data migration capability also reduces the data management complexity that greenfield migration requires.

In all cases, the migration represents a commercial inflection point that should be treated as such. SAP migrations happen infrequently — often once per decade — and the commercial terms agreed at migration will shape the organisation's cost of ownership for a sustained period. Independent advisory support in the commercial negotiation phase is not an optional enhancement; it is the mechanism by which buyers avoid the structural disadvantage of negotiating with one of the world's most sophisticated enterprise software vendors without equivalent preparation.