The Maximo 7.6.1.x timeline contains different kinds of milestones. A base-support end date, the end of a purchased extension, and conditions on using Maximo Asset Management (EAM) alongside Maximo Application Suite (MAS) do not answer the same question.
Start with the dates, then match them to your agreements. Use the migration workstreams to plan execution.
| Milestone | What to establish for your organization |
|---|---|
| September 30, 2025 | Regular base support ended for IBM Maximo Asset Management 7.6.1.x. Record what support agreement, if any, now covers your installation. |
| September 30, 2026 | The product-specific, separately purchased Extended Support term for eligible EAM 7.6.1.x customers ends. Treat this as a check of existing coverage, not a new planning horizon. |
| April 30, 2027 | IBM’s dual support ends for EAM 7.6.1.x under a MAS license obtained by trade-up. EAM use must stop once technical migration to Manage is complete, even if that occurs earlier. |
| September 30, 2030 | The published horizon for optional, separately purchased Sustained Support for eligible EAM 7.6.1.x customers. Availability and the customer’s contracted coverage must be established; the date is not an entitlement. |
The EAM 7.6.1.x extension dates describe product-specific, purchased offerings. They do not establish eligibility, ordering availability, or a guaranteed sequence of support. IBM EAM 7.6.1.x EOS announcement, IBM dual support statement
Don’t try to settle any of this from a support page. Contact your IBM sales representative, ask how these dates and any trade-up terms affect your current licensing contract, and get the answer in writing. The questions under each date below are the ones to bring to that conversation.
IBM ended regular base support for Maximo Asset Management 7.6.1.x on September 30, 2025. Its announcement includes Maximo for Life Sciences 7.6.1.x, product 5724-U23. IBM EOS announcement
Record the support position of the actual installation today: product, release, fix level, supplier, agreement, scope, and expiration. Do not substitute an organization’s general IBM relationship for confirmation of the product’s coverage.
Quality and IT should review the effects of that support position on intended use, security maintenance, incident response, recovery, and record access. The end-of-support event is an input to that assessment; it is not itself a compliance verdict.
Decision to record: Who owns the current support and risk assessment, and when will it next be reviewed?
For EAM 7.6.1.x specifically, IBM’s separately purchased Extended Support offering has a one-year term ending September 30, 2026. That product-specific term should not be confused with extension policies for MAS releases. IBM EOS announcement
If you already hold this coverage, identify open incidents, required supplier actions, and the arrangement that will follow it. Do not treat the expiring term as a newly available multi-year path. This page does not establish new ordering availability or eligibility.
The planning question is concrete: what agreement, controls, resources, and transition decision cover the period after your existing term ends? If the migration is not complete, document the interim operating plan and the unresolved dependencies.
Decision to record: What changes on October 1 for your installation, and who has accepted the plan?
For customers with a MAS license obtained by trade-up, IBM describes “dual support”: EAM 7.6.1.x and MAS may run in any combination up to the total MAS entitlements. That arrangement ends April 30, 2027. Once technical migration to Maximo Manage is complete, the customer must discontinue EAM use. Confirm how the agreement applies to your deployment before scheduling coexistence or cutover. IBM dual support statement
The technical migration completion point belongs in the plan alongside the calendar deadline. Do not assume an arbitrary parallel-operation period or read-only EAM instance remains permitted through April 2027 after that completion point.
Take the proposed coexistence, historical-access, and cutover design to the people responsible for the agreement. Record the applicable rights and constraints in writing, including the retirement point and any alternative record-access arrangement.
Decision to record: What event ends EAM use under your agreement, and how will the necessary historical records remain accessible afterward?
For eligible EAM 7.6.1.x customers, IBM describes optional, separately purchased Sustained Support for up to five years through September 30, 2030. This is a product-specific offering with conditions, not automatic continuation of the previous support arrangement. IBM EOS announcement
Establish whether the offering is available to you and obtain the governing terms before treating it as part of the plan. Review the services included, exclusions, response commitments, responsibilities, and expiration of the agreement you actually hold.
Paying for interim support buys time; it doesn’t make the decision. Set a decision date. Document the target state, the work the interim period will fund, and the criteria for changing course if assumptions fail. The published horizon does not determine how long continued operation is appropriate for your system.
Decision to record: What work and decision milestones are funded during the interim support period, and what is the exit plan?
| Path or status | Evidence needed for a decision |
|---|---|
| Existing EAM 7.6.1.x Extended Support | Your purchased coverage and the plan for the September 30, 2026 end of the product-specific term. |
| Move to MAS | Requirement demonstrations, release and deployment scope, entitlement calculation, migration plan, and ownership. |
| Investigate EAM 7.6.1.x Sustained Support | Confirmation that the optional purchased offering is available to you, written coverage, and a dated exit plan. |
| Investigate third-party maintenance | Contract-defined services and exclusions, dependencies, response commitments, and a separate software-rights assessment. |
| Move to another platform | The same requirements, records, assurance, commercial, and operating-model evidence requested of the IBM option. |
The table identifies questions to investigate. It does not certify eligibility or prescribe one choice for all life sciences organizations.
IBM’s MAS 9.0-and-later support policy provides at least three years of support from general availability. Under the MAS 9.0+ policy, following an announced lifecycle transition, Extended Support may be available for purchase for up to four additional years; Sustained Support may be available for purchase for an eligible product’s last version or release. These are conditional options, not an automatic sequence. Confirm the selected MAS release and its applicable policy. IBM MAS 9.0+ policy, IBM Extended Support Offering
Do not apply that MAS policy to EAM 7.6.1.x’s product-specific extension dates, or apply EAM’s dates to the target MAS release.
Create one decision record with five fields:
Keep unconfirmed assumptions visible. A date in a marketing guide cannot settle an entitlement question or authorize a quality decision.
Explore the Post-EOS Migration Guide for additional migration planning context.
This material is a planning framework, not legal or regulatory advice, an IBM entitlement determination, or a guarantee of compliance. Confirm contractual terms with IBM or the relevant supplier and approve the assurance approach through your quality system.
