Why MAS is more than an upgrade
Maximo Application Suite runs on Red Hat OpenShift, uses AppPoints licensing and changes how customisations are packaged and deployed. Treat the move as a platform migration with its own plan, not a routine version upgrade.
1. Inventory what you have
- Current Maximo version, add-ons and industry solutions
- Custom Java classes, automation scripts and application designer changes
- Integrations: endpoints, protocols, volumes and owners
- Reports (BIRT, Cognos or others) and who uses them
- Users, security groups and how they authenticate
2. Decide the target
- Where MAS will run: on premises or in the cloud (for example AWS)
- Which MAS applications you need now and later
- Identity integration (for example Azure AD) and single sign-on
- Environments: development, test, pre-production and production
3. Plan licensing early
AppPoints are consumed by the users and applications you enable. Map user types and usage before sizing, so the licence and infrastructure plan match how people actually work. Confirm the details with IBM or your reseller.
4. Rationalise customisations
- Retire customisations that standard features now cover
- Move suitable Java logic to automation scripts or configuration
- Document anything that must stay, with an owner
5. Migrate data and integrations
- Clean data before you move it, not after
- Rebuild or re-point integrations and test error handling
- Reconcile record counts and key values between old and new
6. Test, cut over and support
- Run user acceptance testing with real scenarios
- Rehearse the cut-over and the rollback
- Plan hypercare support for the first weeks after go-live
How Go2ways helps
We have delivered end-to-end Maximo Application Suite implementations on AWS, including configuration, data migration, integration and reports. We can assess your current Maximo and give you a migration plan with effort and risks.