Software AG · Contract review

Read every clause before you sign.

A Software AG (Software GmbH) renewal lands as a quote with terms attached, and the terms decide the next five years more than the headline number does. We review the Adabas and Natural paper line by line, before signature, while the language is still open to change.

The number is negotiable. So are the clauses underneath it.

Software AG mainframe contracts for Adabas and Natural are typically capacity bound and decades deep, layered with amendments that few people on either side have read end to end. A renewal quote arrives with capacity definitions, true up triggers, uplift formulas, and assignment language already drafted in the vendor's favor. Signed unread, those clauses set the cost trajectory long after the negotiation is forgotten.

The ownership context sharpens the stakes. Since 2023 the business has been majority owned by Silver Lake, and in 2024 the webMethods and StreamSets lines, including EntireX, moved to IBM, leaving Adabas and Natural as a standalone Software AG business. Portfolio transitions of this kind are commonly followed by tighter commercial focus on the installed base, and contracts that still reference divested products carry assignment ambiguity that surfaces at the worst moment. Mixed estates should confirm which publisher stands behind each product; our EntireX licensing page covers the most common case.

If the renewal arrives alongside an audit notice, the two are one conversation, handled together with our Software AG audit defense work. If a migration is on the roadmap, the exit terms belong in this contract now.

№ 01

Map the entitlement against the estate

Every product, every license file, every amendment, set against what the estate actually runs. Lapsed products still being charged, overstated capacity, and double counted entitlements surface here, and each one is leverage before signature.

Know the paper better than the vendor.

№ 02

Pin down capacity and true up

How covered capacity is defined, how it is measured, and exactly what triggers an additional charge. Vague capacity language and automatic true up clauses get rewritten into precise, capped terms that cannot drift upward between renewals.

Ambiguity always favors the vendor.

№ 03

Challenge the uplift and the term

Annual uplift formulas, multi year lock ins, and renewal escalators are tested against what is contractually owed rather than what is quoted. Uplifts that were never agreed get struck, and the term is shaped to keep options open rather than close them.

A quote is a proposal, not a fact.

№ 04

Fix assignment and divestiture language

Assignment, novation, and product scope clauses are reviewed against the post divestiture reality, so entitlements point at the right publisher and a future portfolio move cannot strand your coverage or reopen exposure.

Portfolio splits create the gaps.

№ 05

Build in the exit before you need it

Portability, term flexibility, and explicit exit rights go into the contract now, while leverage exists. A renewal that quietly raises the cost of leaving Adabas or Natural is the vendor pricing your migration for you. We price it back.

Exit rights are cheapest at signature.

What changes with us in the room

A signed clause outlives every negotiation that produced it. So we read it first.

20to35%

Typical renewal reduction

500+

Engagements delivered since 2019

$180M+

Mainframe spend negotiated on the buyer side

Frequently asked questions

Q1

What should the review focus on first?

The capacity definition and the true up mechanism. Adabas and Natural agreements are typically capacity bound, so the review confirms exactly how covered capacity is defined, measured, and charged. Vague capacity language and automatic true up clauses are where cost escalates quietly, so they get pinned down before signature.

Q2

Does the IBM webMethods divestiture affect our contracts?

It can. webMethods and StreamSets, including EntireX, moved to IBM in 2024, while Adabas and Natural stayed with Software AG as a standalone business under Silver Lake. Contracts that bundle divested products with Adabas or Natural need their assignment and scope language reviewed, because splits commonly leave entitlements pointing at the wrong publisher.

Q3

Can a review reduce a renewal we were already quoted?

Often. A quoted renewal is a proposal, not a settled number. Reviewing entitlement against actual consumption commonly surfaces overstated capacity, lapsed products still being charged, and uplift clauses never contractually owed. Each is leverage to bring the number down while the terms are still open.

Q4

What terms protect a future migration?

Term flexibility, capped uplifts, portability, and explicit exit rights. Multi year renewals commonly lock the estate in place at terms that make a later migration more expensive. If modernization is anywhere on the roadmap, the protections go into the contract now, alongside the exit math.

Related: Software AG licensing hub · audit defense · renewal advisory · contract review service

Audit notice or renewal under 18 months out? We mobilize within 48 hours.

Get expert help

Software AG renewal on the table? Read it before you sign.

Get expert help