Maximo 7.6 to MAS 9 Upgrade: What Changes for Your Data
Updated on · VAGANET EAM
In short. Moving from Maximo 7.6 to MAS 9 does not necessarily mean reloading your data: the standard path upgrades the existing database. The data workstream then covers users, customizations, integrations and attachments. A real data migration is only needed for a re-implementation, a consolidation or a change of system.
IBM Maximo Application Suite (MAS) replaces Maximo 7.6 with a containerized platform on Red Hat OpenShift, of which Maximo Manage is the core application. For the teams in charge of data, the key question is simple: what happens to our database, and what do we need to migrate?
Two paths: upgrade or re-implementation
| Database upgrade | Re-implementation | |
|---|---|---|
| Principle | The Maximo 7.6.1 database is upgraded when Manage is deployed | New Manage, data migrated from 7.6 or another system |
| Data | Kept, history included | Selected, cleansed, reloaded |
| Data effort | Low to moderate | Significant (mapping, cleansing, rehearsals) |
| When | Data model still fits | Model to be reviewed, consolidation, degraded data |
In both cases, start from an assessment of the database: volumes per object, added attributes, customizations, active integrations and the quality of reference data.
Preparing the database before an upgrade
- check the 7.6.1 patch level required by the target Manage version (see the compatibility matrix published by IBM);
- purge what is no longer used: logs, integration messages in error, old transactions;
- inventory added objects and attributes, Java classes and automation scripts;
- rehearse the upgrade on a copy of production and measure its duration.
Users and security
In MAS, identity is held by the suite and synchronized to Manage. 7.6 users must be linked to MAS users, provisioned through the administration console, the administration API or an LDAP or SAML directory. Manage security groups remain, but granting access rights to the suite's applications is a new point to scope. It is often the most underestimated batch of a migration.
Customizations and integrations
- Java classes: possible but built into the Manage image, which weighs on every update; replace them with automation scripts where possible.
- MIF integrations: object structures, enterprise services and endpoints are kept, but URLs, certificates and authentication methods change. External callers generally move to the API key (see the REST API guide).
- Reports: to be inventoried and retested in the new environment.
Attachments (doclinks)
In 7.6, attachments generally reside on a server file share. In MAS, they move to storage accessible to the containers (persistent volume or object storage). You need to copy the files and check that the paths recorded in Maximo point to the new location. Test opening a sample of attachments per object type after the copy.
When a data migration is needed
In a re-implementation, the workstream becomes a classic data migration: extraction from 7.6 (through the API, SQL queries or exports), mapping to the new model, cleansing, then loading in dependency order. The guides running a data migration project and data init and load order detail the approach. An advantage of a Maximo source: the object structures are the same on both sides, which simplifies the mapping of standard objects.
Data-side migration checklist
- Path chosen: upgrade or re-implementation, supported by the assessment.
- Database purged and upgrade rehearsal timed.
- Users linked to MAS, synchronization tested.
- Customizations inventoried, Java replaced where possible.
- Integrations reconfigured (URLs, certificates, API keys).
- Attachments copied and verified.
- Volume reconciliation before and after, object by object.
Frequently asked questions
Do you have to reload all the data to move from Maximo 7.6 to MAS 9?
No, not in the general case. IBM's standard path upgrades the existing Maximo 7.6.1 database to Manage, which keeps the data. A full data migration is mainly needed for a re-implementation (new data model), the consolidation of several instances or a change of CMMS.
What changes for users in MAS 9?
Identity is managed by the MAS suite and synchronized to Manage. Users must exist on the MAS side (administration console, API or LDAP or SAML directory), with their application rights. Plan a dedicated batch and test the synchronization before cutover.
Do custom Java customizations survive the move to MAS?
Custom Java classes remain possible, but they must be built into the Manage image, which makes every update heavier. Most projects take the opportunity to replace what can be replaced with automation scripts and configuration.
When should you re-implement rather than upgrade?
When the 7.6 data model no longer fits the organization (sites, hierarchies, classifications), when the data is too degraded to keep, or when several instances must merge. You then start from a new Manage and migrate the useful data.
Load your Maximo data without silent errors
MAS9 checks your files against each environment's configuration, resumes an interrupted load without duplicates, then reads Maximo back to prove every row arrived.
Discover MAS9