Licence-to-Cloud Transitions and the Revenue Dip

Upfront Licence Revenue Becomes Ratable Cloud Revenue

A perpetual software licence is recognised largely when it is sold. A cloud subscription for the same workload is recognised over the life of the contract. Move a customer from the first to the second and the economics can be healthy while reported revenue and near-term margin fall. The dip is an accounting shape, not proof that demand disappeared.

The recovery comes when the ratable cloud base is large enough that each year’s recognition exceeds the licence revenue given up. How long that takes depends on the conversion ratio: how much annual cloud revenue replaces each unit of licence or support given up.

SAP as the Worked Case

SAP is the licence-to-cloud name in this set. FY2025 figures are IFRS, in euros.

Licence has already shrunk to a thin slice of the mix, while cloud is more than half of revenue and still growing at 23%. The transition is visible in the mix table more than in a single growth rate.

Why Margin Dipped in FY2024

FY2024 operating margin of 13.6% (€4,665M / €34,176M) was the year restructuring charges hit. FY2025 operating margin recovered to 26.1%. Reading those two years as a smooth cloud-transition curve would overstate how mechanical the margin path is; restructuring sat inside the trough. The mix shift still matters: ratable cloud replaces high-margin upfront licence recognition, and cost programmes land unevenly across years.

Current cloud backlog of €21.05B is the near-term contracted cloud stock. It grew 16% and sits beside total RPO of €90.5B with about 39% due within a year. Those RPO and current-share figures are the contracted view of the same shift.

Microsoft as Context, Not a Twin

Microsoft already reports Microsoft Cloud at $214.4B for FY2026, or 64.6% of revenue. Remaining performance obligations are $684B, with about 30% current. That is a scaled cloud mix. It is useful as a destination shape: cloud as the majority of revenue, with capital intensity and RPO duration as the live questions rather than licence replacement.

SAP’s research profile keeps the cloud, licence and backlog lines together so the transition reads as one system.

What to Watch in Any Licence-to-Cloud Model

1. Licence and support revenue falling as cloud rises; track both, not cloud alone.
2. The conversion ratio implied by cloud gained per unit of licence or support given up.
3. Operating margin in the years restructuring or reinvestment overlap the mix shift.
4. Current cloud backlog and current RPO share as near-term contracted checks.
5. Whether revenue for a year sits below the pre-transition base before the ratable stack catches up.

The dip is expected mechanics when recognition changes timing. The analytical work is measuring how deep and how long, from the filer’s own mix and backlog, rather than treating every soft revenue year as lost demand.