Migration from Maximo SaaS Flex or On-Premises or TRIRIGA SaaS

Migration of Maximo/TRIRIGA SaaS to MAS SaaS

This section outlines the migration paths for transitioning existing applications to Maximo Application Suite as a Service (MAS SaaS). It includes three primary migration scenarios:

1. Migration from IBM Maximo EAM SaaS Flex offering
2. Migration from an on-premises or third-party cloud-hosted Maximo installation
3. Migration from TRIRIGA SaaS to Maximo Real Estate and Facilities (MREF) SaaS

While the core steps across these migration paths are similar, the responsibilities and execution details may vary depending on the source environment and the teams involved. This document primarily focuses on the MAS SaaS applications including Maximo Real Estate and Facilities. The following diagram provides a high-level overview of the migration paths to MAS SaaS, including the transition from TRIRIGA SaaS to MREF 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.

Assumptions

• The objective is to minimize the time required to migrate from TRIRIGA to MAS
• During the migration, clients should not be planning updates to their production instances
• To complete this exercise, it is assumed:
  • Production data will be used for testing
  • The planned number of migration attempts is 3 (1. Test 2. Complete evaluation 3.The final cutover)
• For extremely large databases (> 800GB), a custom version of lift and shift must be used. This presentation does not cover those instances and needs to be discussed separately.
• In any note below where Client is marked as accountable or responsible, these tasks may be delegated by the client to a 3rd party – IBM Consulting, IBM Expert Services or Business Partner.

Pre-Conditions (Manage)

There are several preconditions that need to be met to migrate to the new MAS SaaS offering:

1. A new Maximo Application Suite SaaS (MAS SaaS) contract is in place.

2. 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.

3. The source database export is DB2 (the supported DB2 version depends on the timing of the migration).

4. 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.

5. Customer has run Maximo v7.6 Integrity Checker on source database and resolved all errors prior to sending to IBM.

6. 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.

7. 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/

8. Database conversion tools won't address stored queries, relationships or reports. Ensure these are converted and tested on v7.6 before migrating to MAS.

9. TEXT Search is not supported in MAS. All fields should be converted from TEXT search to another value (WILDCARD, EXACT, or NONE).

10. Each user account can have only one (1) primary email address.

11. Each user account can have only one (1) primary phone number.

12. 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.

13. 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

14. Insure maxtable and maxintobjdetail are updated properly before sending the database to IBM. See link below for further information:

    https://www.ibm.com/support/pages/error-initializing-micservicebmxaa7733e-after-applying-fix-pack-7505

15. 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

Pre-Conditions (MREF SaaS)

• You must be on at least platform 4.5 or 5.0 and application 11.5 or higher (if you are an existing TRIRIGA SaaS (Flex) client, then a platform upgrade is part of your contract, however it must be scheduled if not already there). The upgrade cannot be part of the migration.
• You must be on DB2 or be converted to DB2
• You must review all integrations along with IBM to ensure there is no custom, non-standard connections (i.e. no integrations can be directed to the database).
• MAS SaaS and MREF must be installed and ready

Initial Set Up

Test 1

Test 1 executes all of the steps required to move a customer from the TRIRIGA SaaS or 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.

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).

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.

Post Live MAS-SaaS Activities

• After going live, backflows and final configurations of other test systems are completed and turned over to the client.
• Hyper-care for the following week to resolve any found issues.
• Final meeting to review the migration for improvement suggestions.
• The Project plan should allow for product defect remediation.
• The largest part of the project will be the testing component.
• Do not decommission the TRIRIGA SaaS sites immediately. Limit access to TRIRIGA SaaS so data can be compared, but new work should not be done on them.

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.

MREF Document manager