Maximo 7.6 to MAS 9 readiness checklist
34 checks to work through before you start the move to Maximo Application Suite 9. Anything you can't tick is a risk to put on your project plan. Here's what it covers.
Know what you have today · 7 checks
You can't plan a migration until you know exactly what you're migrating: versions, customisations, integrations, reports, data and users.
Licensing and access · 4 checks
MAS licenses by AppPoints rather than named product seats. Map each role to an access level and decide how people will sign in.
Platform and hosting · 4 checks
MAS runs on Red Hat OpenShift, a big change from a 7.6 application server. Decide where it will run, and who will run it.
Customisations and integrations · 3 checks
Where most of the effort and risk sits: what happens to each Java customisation, and how every interface is retested.
Mobile and the user experience · 3 checks
What your users and technicians will notice, from Maximo Mobile to moving start centres onto Operational Dashboards.
Data, testing and cutover · 5 checks
Clean data, a full rehearsal on a copy of production, role-based testing, and a cutover plan with a tested way back.
People and training · 4 checks
A technically perfect upgrade still fails if users can't do their jobs on day one.
AI worth planning for now · 4 checks
Reliability Strategies, problem code inferencing, similar work orders and the AI Assistant, and what they mean for the data you migrate.
Written by Martin Williams from 20+ years of Maximo training and implementation work. General guidance only: check each point against your own licence and environment.