SAP Cloud Extension Policy and Credits

SAP's cloud extension policy lets a customer apply existing on-premise license and maintenance value toward an SAP cloud subscription, typically at a conversion ratio of 1:1 to 3:1 of annual maintenance to annual cloud spend, but the policy almost always requires surrendering the underlying perpetual licenses, which is where buyers lose value they never get back. The offer is framed as credit for what you already own. In reality it is a swap: a perpetual asset and its predictable 22 percent maintenance for a term subscription that resets at renewal. Whether the trade is favorable depends entirely on the conversion ratio, what you surrender, and the renewal terms attached.

What the cloud extension policy is

The cloud extension policy, sometimes presented as a contract conversion or a credit program, is SAP's mechanism for moving on-premise customers to cloud subscriptions without a full repurchase. Instead of buying cloud at list and continuing to pay on-premise maintenance, the customer redirects existing license and maintenance value toward the new cloud commitment. SAP applies a conversion ratio to determine how much cloud spend the surrendered on-premise value covers.

The mechanism overlaps with S/4HANA contract conversion credits, which apply specifically to the move from ECC to S/4HANA. The two programs are often combined in a single RISE proposal. Our S/4HANA conversion credits guide covers the conversion-specific math, and the cloud extension policy sits on top of it.

How the conversion ratios work

SAP expresses the credit as a ratio of surrendered annual maintenance to cloud subscription value. A 1:1 ratio means one dollar of surrendered annual maintenance covers one dollar of annual cloud subscription. A 3:1 ratio means one dollar of maintenance covers three dollars of cloud, a much more generous credit. The ratio offered depends on deal size, the cloud commitment term, and how strategically SAP views the account. Larger, longer commitments and full RISE migrations attract the higher ratios.

What you actually surrender

The credit looks like found money, but the customer surrenders three things. First, the perpetual license itself, an asset that could otherwise run indefinitely at maintenance cost or move to third-party support. Second, the option to drop or reduce maintenance, which our maintenance reduction guide shows can cut on-premise running cost sharply. Third, price predictability: maintenance grows slowly and is contractually capped in many agreements, while a cloud subscription resets at renewal to then-current rates, exposed to the annual increases tracked in our SAP price increase analysis.

When the extension makes sense

The cloud extension can be the right move when the customer is committed to S/4HANA Cloud or RISE regardless, when the conversion ratio reaches 2:1 or better, when renewal price protection is secured in writing, and when the surrendered on-premise estate was going to be retired anyway. In those cases the credit reduces the cost of a migration the customer was already going to make. It is the wrong move when the customer is being pushed to cloud against its roadmap, when the ratio is 1:1 or worse, or when stable on-premise workloads could continue cheaply at maintenance or third-party support.

Protecting value in the deal

Three protections matter most. Secure renewal price protection so the post-term subscription cannot reset to list. Negotiate the conversion ratio against a documented alternative, because a credible decision to stay on-premise is what moves SAP. And confirm exactly which licenses are surrendered and which are retained, since SAP proposals sometimes sweep in perpetual rights the customer intended to keep. These protections sit inside the broader commercial framework in our RISE versus GROW versus HEC guide and the mistakes to avoid in our SAP renewal mistakes guide.

The bottom line on cloud extension credits

SAP's cloud extension policy can genuinely reduce the cost of a migration the customer was going to make, or it can quietly surrender perpetual value worth more than the credit for a cloud move the customer was not ready for. The deciding factors are the conversion ratio, what is surrendered, the credit period, and the renewal price once the credit lapses. A customer that decouples the cloud decision from the credit offer, decides whether to move to cloud on the business case alone, and then negotiates the best possible credit on its own timeline, captures the value without the trap. A customer that lets the credit drive the timing hands SAP control of both the migration and the commercial terms. The on-premise estate is a strong fallback position, runnable for years at maintenance or third-party support, and that fallback is exactly what gives the customer the bargaining power to negotiate a favorable ratio and the renewal protection that makes the conversion worthwhile. Model the full term, secure the protections in writing, and never let the credit decide the roadmap.

Timing the conversion against your roadmap

The cloud extension policy is most valuable to a customer that was going to move to S/4HANA Cloud regardless, and most dangerous to a customer being pushed to cloud ahead of its own roadmap. The timing question is therefore the first one to settle: is this migration something the business has decided to do for its own reasons, or is it something SAP is encouraging through the credit and the implied audit pressure behind it. A credit that accelerates a migration the customer had already committed to is genuine value. A credit that talks a customer into a migration it was not ready for, surrendering perpetual assets for a subscription it did not need yet, is an expensive mistake dressed as a saving.

For customers not yet ready to commit, the on-premise estate remains a strong position. SAP has extended mainstream maintenance for ECC and S/4HANA on-premise well into the next decade, which means a customer can run its owned licenses for years, reduce maintenance cost through the levers in our maintenance reduction guide, and convert to cloud later from a position of choice rather than pressure. The credit will still be available when the customer is ready, and the conversion ratio is often better when the customer is clearly able to walk away.

The discipline, then, is to decouple the cloud decision from the credit offer. Decide whether and when to move to cloud on the merits of the business case, then negotiate the best possible credit for that move on its own timeline. A customer that lets the credit drive the cloud decision has reversed the order and handed SAP control of both. The complete commercial picture, including how the credit interacts with conversion incentives, sits in our S/4HANA conversion credits guide.

How the policy sits inside a RISE deal

Cloud extension credits rarely arrive as a standalone offer. They appear inside a larger RISE with SAP proposal, bundled with S/4HANA Cloud, managed infrastructure, and a multi-year subscription commitment. Inside that bundle the credit is presented as the reward for committing, which makes it hard to evaluate in isolation. The discipline is to separate the credit from the bundle and value it independently: what on-premise assets and maintenance am I surrendering, what credit am I receiving against the subscription, and what is the net cost of the whole arrangement over its full term compared with staying on-premise. Only after that separation can a customer tell whether the credit is genuine value or a discount on an overpriced commitment. The RISE structure itself is covered in our RISE versus GROW versus HEC guide.

SAP's incentive in the bundle is to maximize the committed subscription value and the term, because that is what its cloud bookings target rewards. The customer's incentive is the opposite: the smallest commitment that meets the need, the shortest defensible term, and the strongest renewal protection. The conversion ratio is where these incentives meet, which is why it is the most contested number in the deal.

A worked conversion

Consider a customer paying $440,000 per year in maintenance on a $2,000,000 on-premise S/4HANA estate it owns outright. SAP offers a RISE migration with a cloud extension credit at a 2:1 ratio, meaning the surrendered $440,000 of annual maintenance covers $880,000 of annual cloud subscription. If the RISE subscription is quoted at $1,100,000 per year, the credit covers most of it for the credit period, and the customer pays the difference. The questions that decide whether this is a good deal: how long does the credit apply, what happens to the price when it lapses, and what was the customer giving up by surrendering a perpetual estate it could have run for years at $440,000 maintenance or moved to third-party support at roughly half that.

The conversion checklist

Before accepting a cloud extension, confirm five things. Exactly which licenses are surrendered and which are retained. The conversion ratio, benchmarked against comparable deals. The credit period and what happens to price when it ends. Renewal price protection in writing. And the alternative cost of keeping the on-premise estate, including the third-party support option from our maintenance reduction guide. A customer that walks into the conversation with a credible decision to stay on-premise holds the advantage, because the cloud extension only works for SAP if the customer says yes. That walk-away position is what moves the ratio and secures the protections.

The full SAP commercial picture sits in our complete SAP licensing guide. For a modeled conversion against your retained on-premise value, the SAP vendor practice and our software licensing advisory service run the trade before you sign.