Decommissioning cost in RISE versus brownfield.

The cost of exiting a deployment model is rarely modelled in the initial decision. The buyer compares the cost of running RISE against the cost of running brownfield, selects the deployment model that presents the more favourable operating profile, and treats the decision as a stable commitment for the term of the analysis. The treatment is structurally incomplete because every deployment model eventually ends, either at the contractual term in the case of RISE or at the maintenance horizon in the case of brownfield, and the cost of the ending is itself a material component of the total cost of ownership. Across 500 plus engagements, the firm has reviewed decommissioning cost data from buyers transitioning between deployment models and the recurring finding is that decommissioning often costs 15 to 35 percent of the annual run rate of the deployment being exited. The cost is real, the cost is structural, and the cost varies materially between RISE and brownfield in ways that the initial decision should account for. The discipline is to model decommissioning into both comparisons rather than treating it as an end of horizon exception that does not affect the choice between models.

What decommissioning actually includes.

The decommissioning scope includes five categories of activity. The first is data extraction and migration to the successor environment, including the negotiated extraction format, the data quality validation, and the parallel running window during which both environments are operating. The second is the integration restructuring that points the connected systems at the successor environment rather than the deployment being exited, with the corresponding testing and cutover for each integration. The third is the application decommissioning itself, including the shutdown procedures, the archival of the historical data, and the contractual completion procedures with the deployment vendor.

The fourth category is the regulatory and audit obligations that may persist beyond the operational decommissioning. Many regulated industries require retention of historical transactional data for periods that extend beyond the active life of the deployment, and the retention obligation typically requires either ongoing access to the decommissioned environment in a read only mode or migration of the historical data to an alternative archival platform. The fifth category is the residual cost of the systems and processes that supported the deployment but cannot be immediately decommissioned, including the team members who provided basis support, the vendor management overhead, and any third party tools that were specifically licensed to support the exited deployment.

The aggregate cost across the five categories typically runs between 15 and 35 percent of the annual run rate of the deployment being exited. The lower end of the range applies to buyers who have planned the decommissioning at signature and have built the relevant contractual protections, data extraction provisions, and parallel running capabilities into the original deployment design. The higher end applies to buyers who arrive at the decommissioning without the upfront planning and must assemble the decommissioning capability under time pressure during the active exit.

RISE decommissioning at the end of the contractual term.

RISE decommissioning at the end of the contractual term is the scenario that most RISE engagements eventually face, either because the buyer chooses not to renew or because the renewal commercial position is not acceptable and the buyer transitions to an alternative deployment. The decommissioning scope is governed by the contractual exit clauses that were negotiated at signature, and the cost profile depends heavily on the strength of those clauses. The most consequential clauses are the data extraction provisions, the transition assistance scope, the contractual notice periods, and the survival clauses that govern obligations persisting after the contract ends.

The data extraction provisions, in the SAP standard contract, often default to a basic extraction in a format that the buyer must process substantially to use in the successor environment. The negotiated extraction provisions typically include extraction in industry standard formats, extraction of the underlying database in a form usable for replatforming, and access to the SAP environment for an extended window beyond the contractual termination to support the extraction completion. The cost difference between the default and negotiated provisions, in the firm casebook, runs typically between $500,000 and $3 million depending on the buyer data scope.

The transition assistance scope governs the SAP managed services support that is available during the decommissioning window. The default scope typically ends at the contractual termination date with limited post termination support. The negotiated scope typically includes a defined post termination window with continued managed services at the existing rates and a defined transition team focused on supporting the buyer migration to the successor environment. The cost of acquiring transition assistance after the contract has ended, without the negotiated provisions, is often 2 to 3 times the cost of the equivalent assistance under the negotiated provisions.

Brownfield decommissioning at the maintenance horizon.

Brownfield decommissioning at the maintenance horizon is the scenario that the brownfield extension path eventually reaches, since extended maintenance does not extend indefinitely and the underlying technology stack eventually requires replacement. The decommissioning timing is more flexible than the RISE contractual termination because the brownfield exit can be timed to align with the buyer broader transformation roadmap, the budget cycle, and the readiness of the successor environment. The flexibility is itself a value of the brownfield path, since it allows the buyer to optimise the exit timing against operational and financial considerations.

The brownfield decommissioning scope includes the same five categories as RISE decommissioning but with a different cost distribution. The data extraction category is typically lower because the buyer controls the underlying database and can extract data without contractual constraint. The integration restructuring category is comparable because the integrations point at the brownfield environment in the same way they would point at RISE. The application decommissioning category is comparable across both models. The regulatory and audit obligations category is comparable, with the same retention requirements regardless of the deployment model.

The residual cost category differs materially. Under brownfield, the residual cost includes the hardware that supported the brownfield landscape, which often has remaining depreciable life that becomes a write off at decommissioning. The residual cost may also include the basis and operations team that supported brownfield, with the transition to the successor environment typically requiring extended support availability across the cutover window. The aggregate brownfield decommissioning cost, in the firm casebook, has typically run between 12 and 25 percent of the brownfield annual operating cost, which is comparable to or modestly below the RISE decommissioning percentage.

The timing distribution and present value impact.

The timing of the decommissioning materially affects the present value impact on the seven year TCO. The RISE decommissioning typically occurs at year seven of the engagement, with the cost concentrated in months 84 through 96 of the timeline. The brownfield decommissioning, where the buyer is using brownfield as the deployment for the seven year window and then transitioning, typically occurs at year seven or later depending on the buyer extension preferences. Both decommissioning events are heavily discounted in present value terms because they occur at the far end of the analysis horizon.

The discount profile means that decommissioning rarely shifts the deployment model choice on its own. A decommissioning cost of $5 million in year seven, at a 7 percent discount rate, has a present value of approximately $3.1 million. The same cost in year ten, where a brownfield extension might place it, has a present value of approximately $2.5 million. The difference is meaningful but not dominant in the broader TCO comparison. The decommissioning cost matters more as a reminder that the model has a finite life than as the deciding factor in the model selection.

The decommissioning cost matters more in the early termination scenario, where the buyer exits the deployment before the planned horizon. A RISE early termination in year three of a seven year contract typically incurs decommissioning cost in addition to any contractual penalty, with the present value of the combined exit cost reaching 30 to 60 percent of the remaining contractual commitment. The early termination scenario is rare but consequential when it occurs. The discipline of modelling the decommissioning cost into the TCO ensures the early termination scenario is at least considered in the decision rather than overlooked.

The clauses and contractual structures that reduce decommissioning cost.

The clauses that reduce RISE decommissioning cost are negotiated at signature and reviewed at each contractual touchpoint. The data extraction clauses define the extraction format, the timing of extraction availability, the access window post termination, and the support level during the extraction. The transition assistance clauses define the managed services scope available post termination, the rate structure for the post termination work, and the duration of the post termination support availability. The notice period clauses define the timing of the buyer notice of non renewal, with longer notice periods typically associated with more favourable transition support terms.

The survival clauses govern obligations that persist beyond the contractual termination, including confidentiality, intellectual property, audit rights, and any ongoing liability for the deployment period. The survival clauses are often drafted in the SAP standard form to extend SAP rights without symmetric extension of buyer protections. The negotiation target is to align the survival clauses symmetrically, with the same protections applying to both parties for the same survival period.

The brownfield decommissioning structures are typically internal rather than contractual, since the brownfield exit does not depend on a vendor relationship in the same way RISE does. The relevant structures include the data archival approach that determines whether historical data is retained in the decommissioned environment or migrated to an alternative archive, the team transition plan that governs how the basis and operations team is repositioned during the cutover, and the integration cutover plan that governs the systematic transition of each integration from brownfield to the successor environment. The structures are operational rather than contractual but the planning discipline is comparable.

The TCO modelling implications.

The TCO modelling implication is that decommissioning cost should appear as an explicit cost line in both the RISE and brownfield comparisons, modelled at the realistic timing for each deployment model. The RISE comparison includes the decommissioning cost at year seven or at the planned termination point, with the cost scaled to the negotiated exit clauses. The brownfield comparison includes the decommissioning cost at the planned brownfield exit point, with the cost scaled to the operational decommissioning approach the buyer would execute. The functional substitution comparisons each include the corresponding decommissioning costs for the substitute scopes at their planned exit points.

The modelling discipline produces a TCO comparison that is structurally complete across the full deployment life cycle. The comparison reflects the cost of running each deployment, the cost of exiting each deployment, and the present value adjustment that aligns the cost timing across deployment models. The comparison supports the decision on the basis of the full life cycle cost rather than the operating cost during the active deployment alone. Buyers who include decommissioning in the comparison consistently make different deployment decisions than buyers who omit it, particularly in scenarios where the deployment models are otherwise closely comparable on operating cost grounds.

The modelling discipline also supports the negotiation of the decommissioning clauses themselves. The buyer who has quantified the decommissioning cost has the basis to evaluate the SAP exit clauses against an economic benchmark rather than against a procedural standard. The negotiation target shifts from generic improvement of the standard clauses to specific commercial movement that aligns the clauses with the buyer modelled decommissioning cost expectation. The shift typically produces stronger negotiated outcomes than a generic negotiation posture would deliver.

Every deployment model eventually ends. The cost of the ending is part of the total cost of ownership, and modelling it into the comparison consistently changes deployment decisions that would otherwise be made on incomplete grounds.

Conclusion.

Decommissioning cost in RISE versus brownfield is the cost dimension that most TCO comparisons treat as an end of horizon exception rather than as a structural component of the deployment cost. The five decommissioning categories of data extraction, integration restructuring, application decommissioning, regulatory and audit obligations, and residual cost together typically reach 15 to 35 percent of the annual run rate of the deployment being exited. The RISE decommissioning is governed by the contractual exit clauses negotiated at signature, while the brownfield decommissioning is governed by the operational planning the buyer maintains internally. The timing distribution typically places decommissioning at the far end of the analysis horizon where present value discounting attenuates the impact, but the cost remains material and varies between deployment models in ways the comparison should reflect. The modelling discipline of including decommissioning as an explicit cost line, with realistic timing assumptions and negotiated clause assumptions for the RISE comparison, produces a TCO comparison that is structurally complete and supports the deployment decision on the basis of the full life cycle cost. The discipline is modest in effort and significant in the quality of the decision it supports.