Assetize

Upgrade Desk · Platform migration

Maximo 7.6.1.x → MAS 9.2

IBM documents this as a migration from classic Maximo onto MAS 9.2, not an in-place upgrade. What IBM has stated about this move, what breaks, the landmines, what you gain and the plan — each with the page it comes from.

Take it with you: the whole page exports as an Excel workbook, a PDF or Markdown from the page, and the phased checklist exports the same way with your ticks. Also: fixes gained, security catch-up, the deprecation register and the readiness assessment.

Direct or staged

71 script-stated changes. The same list direct, via 9.0 or via 9.1.

7.6.1.3 → 9.2. Distinct changes, combined across each route. Delivery effort, testing, downtime and supported-route prerequisites are assessed separately. What IBM's own upgrade scripts state on this move, counted as distinct findings and as a union across the legs rather than a sum. Every leg is scripts only, so the legs and the direct move are the same kind of evidence (A1). A scripts-only finding is graded for review until the customer's own code, screen or configuration is found to name it, which is why this row counts what is stated rather than what is blocking. It counts which changes a route raises, not the effort to deliver them: a change met in two stages can need building, deploying and verifying in both. Risk, downtime windows, rollback safety and testing effort are assessed separately.

What IBM says about this move

The supported route

  • To upgrade to 9.1 you need either Maximo Manage or the foundation service, and a database that supports Manage.

    “When you upgrade to Maximo Application Suite 9.1, either Maximo Manage or the foundation service is required. To complete the upgrade, you must also provide a database that supports Maximo Manage.” — IBM Docs — Upgrading to Maximo Application Suite 9.1, read 2026-09-12

  • Before going 9.1 → 9.2, IBM tells you to review the password-migration changes; the required authentication data is migrated automatically during the upgrade.

    “Before you upgrade from Maximo Application Suite 9.1 to 9.2, review the changes to password migration. When you upgrade from Maximo Application Suite 9.1 to 9.2, the system automatically migrates this required data.” — IBM Docs — What's new in Maximo Application Suite 9.2 / Upgrade checklists, read 2026-09-12

  • During the 9.2 upgrade the administrative permission mode is locked; expect it to be set to cluster mode.

    “The administrative permission mode cannot be modified during the upgrade process.” — IBM Docs — Application and add-ons upgrade prerequisites, read 2026-09-12

OpenShift and platform

Database

  • Maximo Manage runs on IBM Db2, Db2 Warehouse, Microsoft SQL Server and Oracle Database. The suite's own Db2 instance is available from MAS 8.10.

    “Maximo Manage supports IBM Db2, IBM Db2 Warehouse, Microsoft SQL Server and Oracle Database.” — IBM Docs — Database configuration details for Maximo Manage, read 2026-09-12

  • Db2 12 is supported from MAS 9.2. The 11 → 12 move is opt-in, needs a Db2 Warehouse licence file and a full backup first, and is irreversible. Without the licence, Db2 12 runs on a 30-day trial that then takes production down.

    “Db2 12 is now supported in Maximo Application Suite 9.2. Upgrading from Db2 11 to 12 requires explicit opt-in activation and a valid IBM Db2 Warehouse license file. Without a valid license, Db2 12 operates under a 30-day trial license that causes production system outages.” — IBM Docs — What's new in Maximo Application Suite 9.2 / Upgrading Db2 from version 11 to 12, read 2026-09-12

  • Manage 9.2 no longer sets Oracle stored outlines at session start. If you relied on that, enable stored outlines on the Oracle side.

    “Removed support for using Oracle stored outlines at session startup. Previously, the use of alter session set use_stored_outlines = true was supported for connections to Oracle 7 or 8 databases.” — IBM Docs — What's new in Maximo Manage 9.2, read 2026-09-12

Java and customisations

  • Manage 9.1 runs on Java 17: recompile your customisation archives when you upgrade to it.

    “If you are upgrading to Maximo Manage 9.1, which supports Java 17, recompile customization archives.” — IBM Docs — Upgrading Maximo Manage checklist, read 2026-09-12

  • Manage 9.2 and Optimizer support Java 25. If you carry custom Java, plan a second recompile-and-test pass for 9.2, not just the Java 17 one.

    “Maximo Manage and Maximo Optimizer now support Java 25.” — IBM Docs — What's new in Maximo Manage 9.2, read 2026-09-12

  • Customisations travel as customisation archives (Java classes, XML files); IBM's checklist expects them created or updated before the upgrade.

    “Create or update customization archives to store specific changes, such as Java classes, XML files.” — IBM Docs — Upgrading Maximo Manage checklist, read 2026-09-12

Users, authentication and APIs

  • In 9.2 user and group data lives in the Manage relational database and user synchronisation is removed for every application except Maximo Real Estate and Facilities.

    “User and group data for user authentication is stored in the Maximo Manage relational database. User synchronization is removed for all applications except Maximo Real Estate and Facilities.” — IBM Docs — What's new in Maximo Application Suite 9.2, read 2026-09-12

  • The user-creation, workspace-assignment and role-assignment APIs deprecated in 9.1 are removed in 9.2. Update integrations and scripts before you upgrade. Setting initial roles is gone in 9.2.

    “User and group management APIs that were deprecated in Maximo Application Suite 9.1 are now removed in 9.2. If your integrations or scripts use the deprecated APIs, update them to use the new APIs before you upgrade to 9.2. Starting in Maximo Application Suite 9.2, the ability to set initial roles is no longer available.” — IBM Docs — User management APIs in Maximo Application Suite 9.1 and later, read 2026-09-12

  • After moving from Maximo 7.6 to MAS 9.x with Okta SSO, users need a separate e-signature password: LDAP synchronisation no longer covers e-signatures.

    “After upgrading from Maximo 7.6 to Maximo Application Suite (MAS) 9.x, users are required to create a new, separate password for electronic signatures (e-signatures). Users must manage two different sets of credentials: one for logging into MAS via Okta and another for performing electronic signatures within Maximo Manage.” — IBM Support — Separate e-signature password required in Maximo Manage after upgrading to MAS 9.x (24 June 2026), read 2026-09-12

Applications and add-ons

  • Maximo Anywhere and Work Centers are not in the suite from MAS 8.9; Maximo Mobile and the role-based apps replace them. Full detail on the Maximo Mobile desk (assetize.com.au/mobile).

    “Beginning with version 8.9, GA Q4 2022, Work Centers and Anywhere Mobile applications are removed from Maximo Application Suite (MAS).” — IBM Support — Work Centers and Anywhere Mobile applications to be removed from Maximo Application Suite (18 Oct 2022), read 2026-09-12

  • From Maximo Mobile 9.1 the Windows app is only in the Microsoft Store; shared-device setups must configure local authentication for offline login.

    “Starting in Maximo Mobile 9.1, the IBM® Maximo Mobile app for Windows is available only from the Microsoft store.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • Maximo Collaborate is deprecated as an add-on in 9.2, and the role-based menu section is removed.

    “Maximo Collaborate is deprecated as an add-on in Maximo Application Suite. The role-based menu section is removed for a cleaner menu structure.” — IBM Docs — What's new in Maximo Application Suite 9.2, read 2026-09-12

  • From 9.1 Maximo Health is an add-on inside Manage, not a stand-alone suite application; Maximo Assist is renamed Maximo Collaborate automatically on upgrade.

    “Maximo Health is no longer available as a stand-alone suite application but remains an add-on in Maximo Manage. Starting in Maximo Application Suite 9.1, IBM Maximo Assist is now named IBM Maximo Collaborate. If Maximo Assist is deployed in Maximo Application Suite 9.0 or earlier and you upgrade to Maximo Application Suite 9.1, the name is automatically changed.” — IBM Docs — What's new in Maximo Application Suite 9.1, read 2026-09-12

  • Before upgrading to 9.0, remove Maximo Inventory Optimization as an externally configured application; from 9.0 it is reached by its own URL.

    “Maximo Inventory Optimization is no longer available to be added as an externally configured application and must be removed.” — IBM Docs — Application and add-ons upgrade prerequisites (Upgrading to 9.0), read 2026-09-12

  • Before upgrading to 8.11, deactivate and delete IBM Parts Identifier; it is no longer available.

    “IBM Parts Identifier is no longer available and must be deactivated and deleted.” — IBM Docs — Application and add-ons upgrade prerequisites (Upgrading to 8.11), read 2026-09-12

  • Which applications and add-ons exist at each suite release is tabulated on IBM's compatibility matrix; an application that is no longer available must be deactivated and deleted before the upgrade completes.

    “Before upgrading, you must consider whether applications and add-ons are available for upgrade. If they are no longer available, you must deactivate and delete them.” — IBM Docs — Compatibility matrix / Upgrading IBM Maximo Application Suite versions, read 2026-09-12

Reports

Classic Maximo to Manage

  • Classic to Manage is a suite install plus a migration, not an in-place upgrade: install MAS, configure and encrypt the database, deploy the Manage operator, activate, then migrate and verify. Run the Integrity Checker first; customisations move as customisation archives.

    “You must install Maximo Application Suite when you upgrade from Maximo Asset Management. Before you can deploy IBM Maximo Manage, you must configure your database and determine how your database is encrypted. Run the Integrity Checker utility to check for database errors before you start the upgrade process. You prepare connectors and migrate customizations by using customization archives.” — IBM Docs — Upgrading from Maximo Asset Management to IBM Maximo Manage, read 2026-09-12

  • The 9.1 upgrade path explicitly covers Maximo Asset Management 7.6.1.3 or earlier to Manage; the cron, mea, report and ui bundles are updated and the foundation service added.

    “Upgrades are supported from Maximo Asset Management 7.6.1.3 or earlier to Maximo Manage. The cron, mea, report, and ui server bundles for Maximo Manage are updated. The foundation service is also added.” — IBM Docs — Upgrading to Maximo Application Suite 9.1, read 2026-09-12

  • IBM itself says every migration is different; there is no single fixed runbook to copy.

    “All Maximo Manage implementations are unique, and the migration process is different for every deployment.” — IBM Docs — Upgrading from Maximo Asset Management to IBM Maximo Manage, read 2026-09-12

From the field

  • Mehdi Salah (IBM Champion, 7 October 2025) on 9.1 migrations: audit versions, customisations, integrations and data volumes first; package every custom artefact into the MAS archive format; execute every script, report, API and ERP integration on the target and fix what breaks; start early.

    “Conduct a thorough audit of each client's existing Maximo environment: versions, customizations, integrations (ERP, IoT, analytics), data volumes, and technical dependencies. Package all custom artifacts (scripts, web.xml, Java classes, integrations) into the MAS 9.1 archive format. Execute all scripts, reports, APIs, and ERP integrations. Intensify monitoring for the first week.” — IBM Community — Migration to IBM Maximo Application Suite 9.1: Strategy, Lessons Learned, and Practical Guide (practitioner, not IBM documentation), read 2026-09-12

Still specific to your system

  • Whether your exact 7.6.1 level goes direct to 9.2 or must stage through an intermediate release.
  • Minimum OpenShift and database versions for the target release.
  • Required levels of every industry solution and add-on you deploy — each ships its own compatibility line.
  • AppPoint consumption at the target, with the applications you will actually enable.
  • Migration tooling versions for content migration.

The rest of the move

Breaks to absorb and landmines come from the reviewed comparison archive, the 9.x change log, the gotcha library and Change Watch; the deadline clock from the lifecycle table. They render on this page and in every export. The same composition answers the upgrade_plan tool on the MCP server.