① Journal · Software AG
Software AG renewals follow recognizable patterns from the buyer side, most of them shaped by the breakup: Adabas and Natural now run as a standalone business, the focus on the legacy estate has sharpened, and audit exposure on old contracts has risen. Knowing the pattern is half the preparation. Here are five we see, and the lever on each.
Software AG renewals are not random. They follow the breakup of the business.
Across the Software AG renewals we sit on, almost every pattern traces back to the restructuring. After Silver Lake took control in 2023, the group separated its lines: webMethods and StreamSets went to IBM in 2024, and Adabas and Natural launched as a standalone business under Software GmbH in January 2025. The estate that matters for the mainframe, Adabas and Natural, now sits with an owner focused on a much smaller portfolio. At renewal the dominant move is a sharper focus on that estate, with repricing commonly tied to the long term, mission critical value of the data these systems hold. The renewal is decided by whether you value the estate on its real use or accept the vendor's framing of lock in.
The second recurring theme is audit exposure. Adabas and Natural estates are old, often decades into the same contract, and entitlement and deployment commonly drift apart across many hardware generations. That gap is exactly what an audit tests, and a standalone owner concentrating on a smaller catalog has every reason to look. Reconciling deployment against entitlement before any audit notice, rather than after, keeps a clean position rather than handing the vendor a compliance finding to use as renewal leverage. The buyer who proves compliance first negotiates the renewal on the merits. Read this with the Software AG publisher hub and our guide to negotiating audit settlements.
Software AG renewal patterns · what we commonly observe and the buyer side lever
| Pattern | What we observe | Buyer side lever |
|---|---|---|
| Standalone focus on A&N | Sharper attention on the Adabas and Natural estate post split | Value the estate on real use, not the lock in framing |
| Legacy audit exposure | Entitlement and deployment drifted apart over decades | Reconcile deployment to entitlement before any notice |
| Mission critical repricing | Uplift tied to the long term value of the data held | Price the renewal on usage, cap the multiyear uplift |
| Migration framed as impossible | Lock in presented as permanent, alternatives dismissed | Build a credible migration path as negotiating leverage |
| Term reset on old paper | Legacy protections at risk when the contract is restated | Hold the inherited caps and exit rights in writing |
These are patterns we commonly observe across Software AG renewals, not statements of Software AG policy. Your specific entitlement, pricing model, and contract terms govern; treat the patterns as the questions to walk in with, validated against your own deployment and contract data.
Adabas and Natural deployment drifts from entitlement over decades, and that gap is what an audit tests. Reconcile actual deployment against your contracted entitlement independently, close any gap on your terms, and document the compliance position before any notice arrives. A clean position negotiated in advance is leverage; a finding discovered during an audit is leverage handed to the vendor.
Prove compliance first, or fund the finding later.
Repricing is commonly tied to the mission critical value of the data, a framing that values the vendor's leverage rather than your usage. Value the estate on what you actually run, cap any multiyear uplift in writing, and tie escalators to a defined index. The data being critical to you is not a reason to fund an open ended increase.
Critical does not mean a blank check on the uplift.
Adabas and Natural lock in is real, but it is commonly presented as more permanent than it is. A credible migration or modernization path, scoped and costed in advance, changes the conversation even if you never use it. The point is not to leave; it is to remove the vendor's assumption that you cannot.
A credible exit you never use still moves the number.
④ Where the Software AG number is won
Software AG renewals turn on compliance and lock in. Prove one, break the other. Reconcile first, then negotiate on use.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
The breakup of the business. After Silver Lake took control in 2023, Adabas and Natural launched as a standalone under Software GmbH in January 2025, while webMethods went to IBM. At renewal we commonly see sharper focus on the legacy estate, repricing tied to mission critical value, and renewed audit attention. The renewal turns on holding your entitlement and proving compliance first.
Adabas and Natural estates are decades old, and entitlement and deployment commonly drift apart across hardware generations. That gap is what an audit tests, and a standalone owner on a smaller portfolio has every reason to look. Reconcile before any notice. See negotiating audit settlements.
Reconcile deployment against entitlement independently, document compliance before any notice, value the estate on real use, hold the legacy protections, cap the multiyear uplift, build a credible migration path as leverage, and start at least eighteen months out. See how vendors time renewal pressure.
Waiting for an audit notice instead of reconciling first, accepting the mission critical framing as a reason to fund an open ended uplift, and treating lock in as permanent. Our license negotiation service values the estate on use and our Software AG contract review reads the legacy terms for the exposure.
Related: Software AG publisher hub · Rocket Software renewal trends · vendor consolidation · Software AG contract review · license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →