IBM MAS Support Changes Take Effect April 2026

IBM has confirmed that support arrangements for multiple Maximo Application Suite (MAS) releases will change on 30 April 2026. This affects every organization running MAS 8.7 through 8.11 and has implications for upgrade planning, budgeting, and operational risk. With the deadline now weeks away, asset management teams need a clear picture of what is changing and what their options are.

What Is Changing on 30 April 2026

The IBM MAS support transitions split into two groups, and the distinction matters.

MAS 8.7, 8.8, and 8.9 reach end of support on 30 April 2026. IBM will not offer Extended Support for these releases. After that date, there are no patches, no security fixes, and no defect resolution available from IBM. Organizations still running these versions will be operating without a safety net.

MAS 8.10 and 8.11 transition from full support to IBM Extended Support on the same date. Extended Support is a paid program that provides a reduced level of coverage: product usage support, existing code patches, and critical defect fixes. It does not include proactive security fixes or new functionality. This buys time, but it is not a long-term position.

IBM communicated these changes on 20 March 2026, giving affected customers just over five weeks of formal notice before the transitions take effect. In practice, this timeline was anticipated by the published lifecycle policies, but many organizations had not acted on the earlier signals.

Where Maximo 7.6.1 Fits

The April 2026 MAS transitions compound an existing pressure. Standard support for Maximo 7.6.1 ended on 30 September 2025. Extended Support is available for purchase through 30 September 2026, with Sustained Support (further reduced coverage) available through 2030.

Organizations that deferred their migration from classic Maximo to MAS now face a narrowing window. The extended support option for 7.6.1 expires in six months, and every quarter of delay reduces the time available for a structured transition. Those still on 7.6.1 should already have a migration plan in progress.

The MAS 9.x Support Model

The support changes for MAS 8.x coincide with IBM’s revised lifecycle policy for MAS 9.0 and later releases. Understanding the new model is essential for anyone planning their target version.

MAS 9.0 and subsequent releases follow IBM’s Support Cycle-3 policy:

Base Support: three years of full product support from general availability, including defect fixes, security updates, and non-defect technical support.
Initial Extended Support: one additional year (purchased separately), covering product usage, existing code patches, and critical defect fixes.
Ongoing Extended Support: up to three further years (purchased separately), with coverage limited to product usage and existing code patches only.

For MAS 9.0, which became generally available in June 2024, this means base support runs through approximately June 2027, with extended options available through 2031.

The new model also standardises versioning across all MAS applications. Maximo Manage, Health, Monitor, Predict, and the other suite components now share the same version number within a release. This eliminates the complex cross-referencing that was required under MAS 8.x, where Maximo Manage could be on a different version number from the parent MAS release.

IBM has moved to a single major release per year, replacing the more frequent cadence of the MAS 8.x era. A Feature Channel provides early access to upcoming capabilities in non-production environments between releases.

What This Means in Practice

The operational implications depend on which version you are running today.

MAS 8.7, 8.8, or 8.9

These versions have no extended support path. The only viable route is upgrading to MAS 9.x (or at minimum, to MAS 8.10 or 8.11 as an interim step, though those versions are themselves now on Extended Support). Remaining on an unsupported release exposes the organization to unpatched security vulnerabilities and makes it difficult to engage IBM for defect resolution.

MAS 8.10 or 8.11

Extended Support purchases time, but at a cost, both financially and in terms of the reduced service level. Organizations in this position should treat Extended Support as a bridge, not a destination. The target should be MAS 9.x, with planning starting now if it has not already.

Classic Maximo 7.6.1

The September 2026 Extended Support deadline for 7.6.1 is the hard constraint. Sustained Support beyond that date provides only minimal coverage. A migration to MAS is not optional: it is a question of when and how, not whether.

Planning the Move

Regardless of the starting version, the transition to MAS 9.x involves several workstreams that benefit from early assessment:

Customisation audit. Identify Automation Scripts, custom MBOs, UI configurations, and report modifications that will need to be validated or reworked. Organizations with heavy customization face the longest lead times.
Integration inventory. Catalogue every external system that communicates with Maximo (ERP, GIS, SCADA, IoT platforms, business intelligence tools). Each integration needs a verified connection path in the new environment. Cleanly designed integration contracts and object structures simplify this significantly.
OpenShift readiness. MAS runs on Red Hat OpenShift, whether on-premises, on a public cloud provider, or through managed hosting. If your infrastructure team has not provisioned and operated an OpenShift cluster before, factor in the learning curve and procurement lead time.
Data migration and validation. Moving from classic Maximo to MAS involves migrating the database and validating that business logic, security groups, and workflow configurations function correctly in the new environment. This is methodical work that cannot be compressed safely.
User adoption. The Graphite UI in MAS is a different experience from the Classic UI. Frontline users, planners, and supervisors all need time to learn the new interface. Organizations that underinvest in change management during migrations consistently see productivity dips that erode the business case.

Do Not Wait for the Deadline

The April 2026 support transitions are not a surprise, but they are a forcing function. Organizations that have been deferring upgrade decisions now face concrete deadlines with real consequences: unpatched vulnerabilities, lost access to defect resolution, and increasing distance from the supported version baseline.

The most common mistake is treating a support deadline as the start of an upgrade project rather than its completion target. Migration to MAS 9.x, done properly, involves months of assessment, environment provisioning, testing, and cutover planning. Starting that process after support has lapsed means operating without coverage during the most complex phase of the transition.

If your organization is on any MAS 8.x release or classic Maximo 7.6.1, the time to assess your position is now, not when the support agreement expires.