Contribute in GitHub:
Edit online
Migration from Maximo SaaS Flex or On-Premises
Migration of Maximo to MAS SaaS
This section covers migration of an existing Maximo application, either on the IBM Maximo EAM SaaS Flex offering or a client-managed installation, to Maximo Application Suite as a Service (MAS SaaS). This document focuses on the MAS Manage (Maximo EAM) application. There are two paths that can be followed:
- Migration of client from the IBM Maximo EAM SaaS Flex offering
- Migration of client from an on-premises or 3rd party cloud provider
The steps are similar for both, but the responsibilities vary as to which team is responsible for some of the tasks. This diagram represents a high-level overview of the migration path to MAS SaaS:
Planning
The planning stage is driven by the customer and covers the internal processes and approvals needed for the migration project. This step requires collaboration with IBM to understand the complexity of the migration, timeframes, level of effort, and personnel needed to perform the migration. In this step the customer determines if they have the necessary expertise and capacity internally to perform the migration or engage IBM GBS, IBM Expert Services or a Business Partner to perform this work.
Pre-Conditions
There are several preconditions that need to be met to migrate to the new MAS SaaS offering:
-
A new Maximo Application Suite SaaS (MAS SaaS) contract is in place.
-
The source version of Maximo must be v7.6.1.2 or greater. For SaaS Flex (IBM hosted) clients, the technical upgrade is performed by the IBM SRE Team as part of the SaaS Flex offering per normal upgrade procedures. For on-premises clients, the technical upgrade is the responsibility of the client or business partner.
-
The source database export is DB2 (the supported DB2 version depends on the timing of the migration).
-
The MAS database timezone for each instance will be set to UTC when provisioned as default. Customers moving from on-premises have to request IBM via a case and provisioning form to make sure timezones on all their environments are set to same as their on-premises environment. This has to be performed before the migration starts.
-
Customer has run Maximo v7.6 Integrity Checker on source database and resolved all errors prior to sending to IBM.
-
All items to be migrated are identified. For SaaS Flex (IBM hosted) clients this is a shared responsibility; for on-premises the customer is responsible.
-
All custom java classes are remediated and removed. Java classes can be replaced with automation scripts. See link for further information:
https://ibm-maximo-dev.github.io/maximo-autoscript-documentation/introduction/whatisautoscript/
-
Database conversion tools won't address stored queries, relationships or reports. Ensure these are converted and tested on v7.6 before migrating to MAS.
-
TEXT Search is not supported in MAS. All fields should be converted from TEXT search to another value (WILDCARD, EXACT, or NONE).
-
Each user account can have only one (1) primary email address.
-
Each user account can have only one (1) primary phone number.
-
The user account added for the mxe.int.dfltuser property must have complete user application and related object access inside Manage for user syncronization to work after migration.
-
Maximo Object Structure Tables and Data Dictionary Tables must be aligned before sending the database to IBM. See link below for further information:
https://www.ibm.com/support/pages/bmxaa7733e-error-loading-object-structure-or-generating-schema
-
Insure maxtable and maxintobjdetail are updated properly before sending the database to IBM. See link below for further information:
-
MaxSequence should be aligned before sending database to IBM. See link below for further information:
https://www.ibm.com/support/pages/integrity-checker-sequence-not-setup-correctly
Initial Set Up
The initial set up includes several components including:
Creation of the target MAS SaaS environment (1 Non-Production and 1 Production environment are recommended) Identification of all components that need to be migrated (database, code, attachments) Final documentation of the integrations and any initial set-up that can be done (including VPNs).
The goal of this step is to ensure all components are in place so the first test can begin.
| Task | IBM | Client (or Designate) |
|---|---|---|
| Deploy MAS environment(s) in selected data center | X | |
| Install applications | X | |
| Perform initial configuration | X | |
| Identify SaaS Flex site for data to use in initial test | X | |
| Identify all components that need to be migrated (attachments, custom reports) | X | |
| Begin VPN set up (optional) | X | X |
| Remediation of JAVA class files to Automation Script(s) | X | |
| Configure any integrations in MAS | X |
Test 1
Test 1 executes all of the steps required to move a customer from the SaaS Flex (or on-premises) implementation to the MAS SaaS offering. Data is exported from the source system, transferred to the MAS SaaS location and loaded into the new Non-Production database instance. Configuration is completed for integrations and any technical remediation performed for the technology differences. Next the client tests to ensure all business flows are performing as expected. Issues identified are then resolved until the testing is complete. A second Test 2 is optional but may be required.
| Task | IBM | Client (or Designate) |
|---|---|---|
| Export data from SaaS Flex and transfer to MAS SaaS Non-Production environment | X | |
| Remediate technical changes in MAS through Maxadmin | X | |
| Test, troubleshoot and resolve any user syncronization issues | X | X |
| Remediate technical changes in MAS at OS Level | X | |
| Deploy attachments | X | |
| Import database | X | |
| Finalize any changes needed | X | |
| Ensure any integrations | X | |
| Test changes | X | |
| Remediate errors | Secondary | Primary |
Test 2
Test 2 is identical to Test 1 above. It is optional but may be required.
Dry Run
This is similar to tests 1 and 2, but the target is the Production environment. The focus is ensuring all steps are documented and accurate timings are taken for the final migration of production. This is a dress rehearsal for the go live as well as to ensure all issues identified in the first test have been resolved. This test should take place close to the final cut-over date (within a few weeks).
| Task | IBM | Client (or Designate) |
|---|---|---|
| Export data from SaaS Flex and transfer to MAS SaaS Production | X | |
| Remediate technical changes in MAS through Maxadmin | X | |
| Remediate technical changes in MAS at OS Level | X | |
| Import database | X | |
| Finalize any changes needed | X | |
| Finalize integrations | X | |
| Test changes | X | |
| Remediate errors | Secondary | Primary |
| Ensure timings for all steps recorded | X | X |
Live on MAS-SaaS
The final execution of the steps in the scheduled migration window. Once complete, the customer is now live on the SaaS service offering.
| Task | IBM | Client (or Designate) |
|---|---|---|
| Export data from SaaS Flex and transfer to MAS SaaS Production | X | |
| Remediate technical changes in MAS through Maxadmin | X | |
| Remediate technical changes in MAS at OS Level | X | |
| Deploy attachments | X | |
| Import database | X | |
| Finalize any changes needed | X | |
| Finalize integrations | X | |
| Test changes | X | |
| Go live | X |
Post Live MAS-SaaS Activities
This is the support for customers after the go live. Any new issue is investigated and resolved and then the client moves to steady state.
Roles and Responsibilities
Both IBM and the client have critical roles in the successful transition to the Maximo Application Suite SaaS offering. These responsibilities are summarized in the attached spreadsheet below (MAS SaaS Migration Swimlanes). At a high level, IBM is responsible for the technical components of the migration and the client is responsible for ensuring business processes are working, custom and unique features of their implementation are identified, and updates to integrations are accounted for in the plan.
If the source database is being converted from another platform (for example Oracle or MS SQL) it is the customer's responsibility to perform validation of the converted DB2 database and correct any issues identified before providing to the SRE team for import into the target MAS SaaS environment.
IBM and the customer share the responsibility to ensure the appropriate personnel are available to meet the agreed project plan.
Database Export
The IBM SRE team requires a DB2 export of the source production database using db2move/db2look. The database export file should be uploaded to your IBM Cloud COS bucket. The bucket detail and its connection detail will be sent via the welcome letter.
Bucket name: masms-XX-X-XXX-XXXXX-"InstanceName"-XX-XXX-cust-files
Doclink and Attachment Files
Doclink and attachment files should be uploaded to the following IBM Cloud COS bucket. Please upload your doclinks directory with all required subfolders. The structure of these files and directories will be maintained when copied to the Manage server location.
Bucket name: masms-XX-X-XXX-XXXXX-"InstanceName"-XX-XXX-cust-files
Note:
The DOCINFO path within the Manage database will need to be updated to /doclinks/"folderStructure"/... It is the customer's responsibility to change all the references. The IBM SRE team prefers customers to carry out this database change and then take the database export so that the database IBM will restore will have this change already.