OpenText acquired Micro Focus and folded its ITSM products, including Service Management Automation X (SMAX), into a portfolio that spans content, security and analytics. For an ITSM buyer the practical effect is a vendor whose account priorities are set above the product, which cuts both ways: there is bundling pressure and uplift risk, but there is also a retention motive and a migration agenda you can trade against. This sits inside the wider field of mid-market options in our 2026 mid-market ITSM platform cost comparison.
What changed for buyers under OpenText?
Three things matter at the table. First, account management is now run at portfolio level, so your ITSM renewal can be bundled with unrelated OpenText spend, which the vendor frames as a discount and which can equally obscure where your money goes. Second, the product roadmap and support posture are set by a larger organization with its own consolidation priorities. Third, OpenText wants estates on its current, supported deployment of SMAX, which gives you a migration decision to control rather than concede.
Why does concurrent licensing decide the size of the saving?
Legacy Micro Focus and OpenText SMAX agreements frequently use concurrent licensing: you license a number of simultaneous sessions rather than a number of named users. That is materially different from a named-seat model and it is where the reduction usually lives. The mechanics are set out in OpenText SMAX pricing and concurrent licensing explained.
Worked through: if you license 150 concurrent sessions but your measured peak concurrency over a representative period is 95, you are carrying roughly a third more concurrent capacity than you use. Concurrent models are bought on fear of hitting the ceiling, so they over-provision by design. The buyer-side task is to measure actual peak concurrency, not named-user counts, and target the gap. A named-user estate of 600 might run comfortably on 100 concurrent sessions, which is the whole point of the model and the whole opportunity in the renewal.
| Licensing model | What you pay for | Where the over-buy hides |
|---|---|---|
| Named user | Each assigned individual | Inactive and duplicate named accounts |
| Concurrent | Simultaneous active sessions | Concurrent ceiling set well above measured peak |
What are the levers, in order?
Run them in this sequence, because each one strengthens the next.
- Measure peak concurrency. Pull session data over a representative window and establish true peak, not the licensed ceiling. This is the evidence everything else rests on.
- Right-size the concurrent count. Target the measured peak plus a modest headroom buffer, and reclaim the difference at renewal.
- Unbundle the portfolio. Insist on a line-item ITSM price so a portfolio bundle cannot hide an ITSM uplift inside an unrelated discount.
- Stage a credible alternative. A costed move to another mid-market platform makes retention something OpenText has to earn. The discipline is in our competitive leverage service.
- Control the migration timing. If OpenText wants you on current SMAX, trade that move for price protection, migration assistance and a capped uplift rather than agreeing to it for nothing.
Our ITSM Competitive Leverage Playbook sets out how to build a credible alternative and use it to discipline a renewal with a consolidating vendor.
How do you measure peak concurrency credibly?
The concurrency baseline is the evidence the whole renewal rests on, so it has to be defensible, not a guess. Pull session or login data from the platform over a representative window, ideally one that captures your busiest period such as a month-end or a major change freeze, and identify the highest number of genuinely simultaneous sessions rather than the total number of users who logged in across the day. Named-user totals and concurrent peaks are different numbers, and conflating them is the error that leaves a concurrent contract over-provisioned for years.
Add a modest headroom buffer to the measured peak rather than to the licensed ceiling, because a concurrent model should be sized to real simultaneous demand plus a margin for growth, not to a worst-case figure no one has ever hit. The gap between that sized number and the licensed concurrent count is your reduction target, and because it is built from the platform's own data it is hard for the vendor to dispute. A baseline OpenText can argue with is not a baseline; a baseline drawn from session logs over your peak period is.
This is also a recurring discipline, not a one-time exercise. Concurrency drifts as ways of working change, so re-measuring before each renewal keeps the licensed count tracking real demand rather than the high-water mark set years earlier. The same logic applies whether you stay on SMAX or migrate, which is why the measurement should be in place before any deployment decision is made.
How do you turn the transition into price protection?
Convert OpenText's two motives into your terms. Because the vendor wants retention, ask for a multi-year price hold and a capped uplift in exchange for the commitment. Because the vendor wants you on its current deployment, ask for migration assistance and a transition period at protected pricing in exchange for moving. Frame both as trades, not requests. A buyer who migrates on the vendor's timeline for nothing has spent leverage and received an uplift; a buyer who migrates on agreed terms has bought protection with a decision they were going to make anyway.
We have run this pattern across consolidating vendors and $420M-plus of ITSM contract value since 2019, and the engagement runs through our contract negotiation service on fixed fee or gainshare.
Book a contract negotiation review.
We measure your concurrency, unbundle the OpenText portfolio price, and trade your migration timing for protection. Fixed fee or gainshare, no savings no fee.
Book a contract negotiation review →Frequently asked questions
- What changed when OpenText acquired Micro Focus?
- ITSM products including SMAX moved into a large portfolio, bringing portfolio-level account management, bundling pressure and a migration agenda. That creates both uplift risk and retention-driven leverage at renewal.
- How does concurrent licensing affect the renewal?
- Concurrent models license simultaneous sessions, not named users, and are usually over-provisioned. Measure peak concurrency against the licensed count and target the gap.
- What leverage do buyers hold during the transition?
- A measured concurrency baseline, a credible alternative, and control over migration timing. OpenText wants to retain and move the account, both of which can be traded for price, terms and migration assistance.