Skip to Content

Default language.

Upgrade process overview

BMC provides out-of-the-box toolkits that can help you upgrade TrueSight Operations Management to BMC Helix Operations Management. Migrating data from TrueSight Operations Management to BMC Helix Operations Management is an essential part of the upgrade process.

To experience an easy migration process, refer to the following guidelines:

  • Analyze the data to be migrated, especially the following data:
    • Cell KB migration details
    • Known issues in migration
  • Identify what doesn't need to be migrated
  • Determine how each rule will be converted
  • Identify challenges and create a mitigation strategy
  • Review the plan and set expectations

Go through this topic to understand the steps that are involved in the data migration.

Related topics

Migrating Remedy on-premises to BMC Helix Service Management on-premises

Deploying in the BMC Helix IT Operations Management deployment documentation

 

Process flow

Refer to the following migration process. You can perform the tasks shown in the following image after you obtain the migration utility. For more information about obtaining the utility, see Where can I find the tools/utilities to assist in migration from TrueSight Operations Management (TSOM) to BMC Helix Operations Management (BHOM)?.

itom_migration_process_16jan26.png

The following table explains the migration process.

Stage

Step

1 - Analyze the TrueSight Operations Management environment and create an upgrade plan

  1. Run the TrueSight Operations Management health check tool.
    To obtain the health-check tool, see TrueSight Operations Management Health Check Tool .

    Sample output of the health-check tool

    hct_sample.png

  2. Analyze the environment.
    1. Identify the data that would be easier to recreate rather than migrate.
      Use the Upgrade-evaluation-questionnaire to evaluate your environment.
    2. Identify the tasks that must be done before the migration.
    3. Evaluate SaaS versus on-premises deployment.
      For information about SaaS versus on-premises evaluation, see SaaS versus On-premises version of BMC Helix Operations Management - an evaluation.

  3. Create an upgrade plan based on your evaluation.
    The upgrade plan will contain information about the data that you want to migrate to BMC Helix Operations Management.
    For an on-premises deployment, see Planning in the BMC Helix IT Operations Management deployment documentation

2 - Deploy the product

  • For an on-premises deployment, see Deploying in the BMC Helix IT Operations Management deployment documentation. 

  • For a SaaS deployment, see Onboarding-overview.

3 - Run migration tools

  1. Policy migrator tool: Migrate CMA policies in TrueSight Operations Management to BMC Helix Operations Management.
  2. Event migration utility: Migrate event policies from TrueSight Operations Management to BMC Helix Operations Management.

4 - Validate in the QA or non-production environment

  1. Validate the migrated data by performing the following tasks:
    1. Define the timelines and owners of each migration task.
    2. Keep the acceptance criteria and checklist ready.
    3. Depending on the experience of validation in the QA environment, change the migration plan.
  2. Test the migrated data.

5 - Implement in the production environment

  1. (On-premises deployment) Install or (SaaS) launch BMC Helix Operations Management in the production environment.
  2. Go live with the product.

 

 

 

 

 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Helix Operations Management 25.1