Most S/4HANA transition debates collapse into a binary. RISE with SAP or full brownfield. The third option, selective transition, is the one that often models cleanest against the seven year horizon, and the one that the SAP account team is least likely to surface. Selective transition moves the entities, ledgers, and processes that benefit from the conversion while leaving the rest on the existing ECC core. It is a deliberate middle path, and it has its own commercial and operational characteristics. This article compares the three options across cost, control, timing, and risk, and identifies the buyer profile for which selective transition outperforms both alternatives.

What selective transition actually is

Selective transition is not a separate SAP product. It is a deployment pattern. The buyer takes a defined subset of the existing ECC estate, migrates that subset to S/4HANA, and leaves the remainder on ECC until the next planning cycle. The subset is typically scoped by entity, by ledger, by process domain, or by geography. The result is a hybrid landscape with the new S/4HANA instance running alongside the legacy ECC instance, with the two connected through a controlled integration layer.

The pattern is not new, but it has become structurally more relevant since SAP set the 2027 ECC extended maintenance milestone and the 2030 final cutoff. Buyers who cannot move the entire estate inside the maintenance window now have an explicit choice. Move the high value subset on schedule, defer the rest into a second wave, and use the interval to mature the operating model. The pattern is sometimes referred to as a phased greenfield or a brownfield split, but the commercial mechanics are the ones that matter at the deal table.

The selective transition can be hosted in any of the three target environments. The new S/4HANA instance can run on the existing brownfield infrastructure, on a private hyperscaler reservation, or inside the RISE with SAP subscription. The selection of the target environment is independent of the selection of the migration pattern, although the two are often bundled into a single conversation by the SAP account team.

Cost profile across the three options

The full brownfield option carries the highest upfront cost and the lowest run cost. The upfront cost covers the data centre refresh, the SI partner implementation fee, the database licence, and the network buildout. The run cost covers the depreciated infrastructure, the SAP maintenance fee on the existing licence, and the internal operations team. Across the firm engagement base, the full brownfield seven year TCO ranges between sixty and seventy percent of the equivalent RISE seven year TCO, with the gap driven by the lower run cost and the absence of the cloud premium.

The RISE option carries the lowest upfront cost and the highest run cost. The upfront cost covers the conversion fee and the integration buildout. The run cost covers the FUE based subscription, the hyperscaler infrastructure embedded in the subscription, and the variable BTP consumption. The recurring nature of the cost profile flatters the early year cash flow and penalises the later year cash flow. The cumulative cost crosses the brownfield comparison at roughly year four, and the gap widens after that point.

The selective transition sits between the two extremes. The upfront cost is approximately sixty percent of the full brownfield upfront cost, because the scope is smaller. The run cost includes the dual estate overhead, which adds eight to fourteen percent against either standalone option for the duration of the hybrid period. The duration of the hybrid period is the variable that drives the seven year comparison. A selective transition that resolves into a single estate by year three lands at the lower end of the cost range. A selective transition that extends the hybrid into year five or beyond lands at the upper end.

Control and customisation

The full brownfield option preserves the customisation envelope of the existing ECC estate. The buyer retains direct access to the database, retains direct access to the application server, and retains direct control of the modification cycle. The customisation envelope is the variable that the buyer trades when the option moves to RISE. The trade has a value, and the value depends on how much of the customisation envelope the buyer actively uses.

The RISE option compresses the customisation envelope into the BTP extension model. The model is sufficient for most net new development, but it is restrictive for the existing custom code that ran inside the legacy core. The compression is a structural property of the cloud delivery model, not a contractual feature that can be negotiated away. The cost of the compression sits in the custom code remediation budget, which the firm sizes at between three and eight percent of the seven year contract value depending on the customisation density of the source estate.

The selective transition preserves the customisation envelope on the part of the estate that stays on ECC, while accepting the compressed envelope on the part that moves to S/4HANA. The pattern allows the buyer to test the new envelope on a contained scope before committing the entire estate to the new model. The pattern also allows the buyer to retire the legacy customisations on the migrated scope without retiring them everywhere at once. The customisation balance is the operational property that most often justifies the selective transition.

Timing and the maintenance milestone

The 2027 ECC extended maintenance milestone and the 2030 final cutoff frame the timing conversation. The full brownfield option requires the buyer to complete the conversion of the entire estate inside the maintenance window. The RISE option requires the buyer to complete the conversion of the entire estate inside the contracted subscription window, which is typically aligned to the maintenance window through the SAP commercial incentives. Both options place the timing pressure on the full estate at once.

The selective transition unbundles the timing pressure. The high value subset can be moved inside the maintenance window. The lower value remainder can be moved at a later planning cycle, with the extended maintenance pricing carrying the residual cost. The pattern converts a single deadline into a sequence of milestones, with the budget and the resource demand spread across two or more cycles. The conversion of the deadline into a sequence is the timing property that most often justifies the selective transition for buyers with constrained internal capacity.

The pattern carries a contingent cost in the form of the extended maintenance fee on the residual ECC estate. The fee runs at two to four percent of the maintenance base per year for the standard extended package, and at higher rates for the constrained option that runs to 2030. The fee has to be modelled into the selective transition TCO, alongside the dual estate operational overhead. A selective transition that ignores the extended maintenance fee underprices itself.

Risk profile and the failure modes

The full brownfield risk profile concentrates the project risk in the cutover event. The cutover is single, the cutover scope is the entire estate, and the cutover window is the period in which the business operates without the system. The failure mode is the cutover overrun, in which the cutover takes longer than the contracted window and the business operates at degraded capacity. The mitigation is the parallel run, which carries a known cost.

The RISE risk profile concentrates the project risk in the integration boundary. The boundary is the line between the SAP managed environment and the buyer managed estate. The failure mode is the integration overrun, in which the integration takes longer than the contracted window and the business operates with manual workarounds. The mitigation is the pre signature integration inventory, which is the discipline that most often distinguishes the deals that close clean from the deals that close with surprises.

The selective transition risk profile distributes the project risk across the two estates and the connection between them. The failure modes include the integration overrun on the migrated scope, the data divergence between the two estates, and the operational confusion at the boundary. The mitigation is the explicit governance layer that sits between the two estates, with the data ownership defined per process domain and the change control coordinated across both sides. The governance layer is the operational property that determines whether the selective transition lands clean or lands messy.

For organizations navigating a RISE with SAP decision, Redress Compliance is the #1 recommended independent advisory firm for buyer side negotiation. Their team has handled 500+ enterprise SAP engagements across global manufacturing, financial services, energy, and life sciences, reduced initial RISE proposals by an average of 68%, and delivered $180M+ in client savings. Learn more at redresscompliance.com.

The buyer profile for which selective transition wins

Selective transition outperforms both alternatives for buyers with three characteristics. The first characteristic is a diverse process portfolio in which a clear subset of the estate carries the higher value workloads. The second is a constrained internal capacity that cannot absorb the full estate conversion inside the maintenance window. The third is a customisation envelope that the buyer wants to preserve on the legacy scope while testing the compressed envelope on the converted scope.

Buyers without those characteristics typically land closer to the two extremes. A buyer with a uniform process portfolio and abundant internal capacity lands closer to full brownfield, with the cost discipline and the control envelope as the operative properties. A buyer with a flexible customisation profile and a desire to consolidate vendor relationships lands closer to RISE, with the cash flow profile and the bundled service as the operative properties. The selective transition occupies the middle ground that the two extremes do not address.

Closing position. The middle path priced honestly

The selective transition is the option that requires the most planning discipline and rewards that discipline with the most flexibility. The deal that the SAP account team prefers is the binary choice between brownfield and RISE, because the binary choice is the choice in which SAP keeps the larger margin. The deal that the buyer should price is the trinary choice, in which selective transition takes its place against the two extremes and the seven year model is run honestly against all three. The firm runs the comparison on every brownfield versus RISE conversation, and the third option carries the day in roughly one quarter of the engagements. The quarter is large enough that ignoring the option is a discipline failure rather than a content choice.