① Guide · Rocket Software
Your Micro Focus COBOL contract has a new owner. Rocket Software now holds Visual COBOL and Enterprise Server, and legacy paper renews on its terms. Here are the buyer levers before the first renewal sets the pattern.
Same COBOL. Same estate. A different name on the renewal.
On May 1, 2024, Rocket Software closed its $2.275 billion acquisition of OpenText's Application Modernization and Connectivity business, the portfolio that was formerly Micro Focus. The COBOL line that many enterprises depend on, Visual COBOL, Enterprise Server, and Enterprise Developer, now sits with Rocket. Agreements that may have been in place for decades will renew under Rocket Software terms, and buyers should expect contractual changes rather than a simple like for like extension.
The COBOL estate commonly mixes metrics, which is where the renewal complexity lives. Development tools such as Visual COBOL and Enterprise Developer typically license by seat, while the Enterprise Server runtime is frequently sized by cores, processor capacity, or deployment units depending on the agreement. The runtime metric is usually where cost concentrates, and an ownership change is exactly when entitlements get reinterpreted, since the new owner is reading old paper for the first time.
None of these patterns are unique to Rocket; they are the standard shape of any post acquisition renewal. The buyer side job is to make sure that harmonizing legacy Micro Focus paper onto Rocket's standard terms does not quietly expand scope, reclassify runtime, or reset a baseline in the vendor's favor.
The governing Micro Focus agreement, with its actual metrics, seat counts, and runtime definitions, is reconstructed before any renewal conversation. Rocket's standard terms are the proposal; your existing entitlement is the baseline they have to negotiate against.
Development seats and runtime entitlements are counted independently. Active developers are matched to seat entitlement; runtime is recalculated against the cores or capacity actually deployed, so the two are not allowed to overlap into a single inflated number.
Every change Rocket proposes when moving you onto its standard terms is checked for scope creep: reclassified runtime, rebundled products, new measurement rules. Harmonization should not be a quiet expansion of what you owe.
A documented view of the alternatives, recompilation paths, competing COBOL runtimes, or selective modernization, gives the renewal a credible floor. As with any deeply embedded estate, the alternative works as leverage even when you intend to stay.
The first renewal under Rocket is locked with capacity and core caps, uplift limits, and clear runtime definitions, because it becomes the template for every renewal that follows. Win the rules now, not just the number.
20 to 35% off the opening number. And a fair template for next time.
With the original paper reconstructed, seats and runtime separated, and the harmonization policed line by line, the first Rocket renewal stops being a take it or leave it migration onto new terms. Across our engagements, buyer side preparation commonly recovers 20 to 35 percent against the opening position, and it sets a clean baseline so the next renewal does not inherit a vendor friendly reset.
To run a live renewal, start with Rocket Software contract review and the Rocket Software hub. For the COBOL metric itself, the Enterprise COBOL licensing page covers the compiler family comparison, and using competitive alternatives as leverage covers how to make the modernization alternative believable.
Rocket Software, which closed its $2.275 billion acquisition of OpenText's Application Modernization and Connectivity business, formerly Micro Focus, on May 1, 2024. Visual COBOL, Enterprise Server, and Enterprise Developer now renew under Rocket.
Commonly a mix: development seats for Visual COBOL and Enterprise Developer, and runtime entitlements for Enterprise Server sized by cores, capacity, or deployment units. The runtime metric is usually where cost concentrates.
Harmonization of legacy paper onto Rocket terms, possible repackaging, and renewed scrutiny of runtime entitlements. The buyer job is to keep harmonization from quietly expanding scope or resetting a baseline.
12 to 18 months out, sooner if yours is among the first agreements to renew under Rocket. The seat and runtime baseline plus an alternatives view takes time, and the first renewal sets the pattern.