Regular base support for IBM Maximo Asset Management 7.6.1.x ended on 30 September 2025. This is now an operating decision rather than preparation for a future deadline. Organisations need to review their actual support agreement, system condition and next steps.
IBM identifies separately purchased Extended Support and Sustained Support options alongside migration to Maximo Application Suite. Scope, duration and eligibility require contractual verification. The end of base support does not mean that every customer has no support options. Source: IBM announcement, checked on 6 November 2026.
Establish the actual system baseline
Record the version, extensions, customisations, integrations and infrastructure. Ask IT and procurement to verify the services included in the existing agreement and the handling of security issues or new defects. Assign an owner to each unresolved question.
IBM's additional offerings are not interchangeable with the former base support service. Obtain confirmation for your specific installation rather than relying on an old product presentation.
Evaluate three routes against the same requirements
- Continued operation for a defined period: document support scope, security measures, recovery arrangements and a decision date.
- Migration to Maximo Application Suite: evaluate functions, target infrastructure, licensing, migration and training together. Determine which customisations can be retained.
- Migration to another system: identify the workflows and data that are actually needed. A CMMS may fit a focus on daily maintenance without reproducing every capability of a broader EAM.
Test migration with representative data
Include the asset hierarchy, open orders, maintenance plans, spare parts and documents. Agree which history must remain accessible in the target and what can remain in a usable archive. Compare counts, relationships and content samples before and after the trial import.
Plan ownership, final data transfer and a recovery route if the transition fails. A claim of migration without data loss is meaningful only when the scope and acceptance criteria are explicit.
Where ELARA may fit
ELARA may be relevant for teams organising daily work orders, asset information and preventive maintenance. Test the fit against your workflows. This does not promise a ready made Maximo connector or a fixed percentage saving.
Compare offers over the same period, including implementation, data migration, integrations and ongoing operation. Discuss your requirements and a possible pilot with ELARA.
