Migration process for Remedy on-premises to BMC Helix Innovation Suite Cloud
Starting from version 21.x, the converged platform environments which are activated in Helix cloud consist of the following applications, which are now a part of BMC Helix Innovation Suite of products:
- BMC Helix ITSM
- Smart IT
- BMC Helix Digital Workplace
- BMC Helix Digital Workplace Catalog
- BMC Helix Dashboards
The migration of BMC Helix ITSM from an existing on-premises system to a BMC Helix Innovation Suite Cloud (BMC Helix ITSM SaaS) system involves several tasks that must be performed in phases. After BMC completes the provisioning of the development, QA, and production environments, the major tasks involved in the migration process include:
- Activation tasks
- Development activities, such as migrating of overlays and customizations and working on integrations
- Data migration
- User Acceptance Tests (UAT)
- Emulated cutover and going live
Supported migration paths
The following table lists the supported product versions from which you can migrate to the BMC Helix Innovation Suite of products:
Application | Source version |
---|---|
BMC Helix ITSM | 20.02 and later |
BMC Digital Workplace | 20.02 and later |
BMC Digital Workplace Catalog | 20.02 and later |
BMC Helix ITSM: Smart IT | 2.0 and later |
BMC Helix ITSM: Smart Reporting | 20.02 and later |
Best practice
We recommend you use the latest version of BMC Helix Data Manager.
For information about downloading the installation files, see Downloading the installation files .
Supported databases
You can migrate data from the following databases:
- PostgreSQL
- Microsoft SQL
- Oracle
Planning the migration
Complete the following tasks before the start of the migration process:
- Run license compliance assessment and checks
- Prepare documents required for planning your migration project
Run license compliance assessment and checks
BMC Helix SaaS environments are activated with bundled licenses, whereas BMC Helix on-premises environments are available with classic licenses. The License Conversion Utility has to be run to assess and convert People profile data licenses before and during the migration process.
Best practice
We recommend that you convert your existing people profile data from classic to bundled licenses before you go-live.
Running License assessment and conversion on BMC Helix systems during migration:
During migration, you must assess and convert the People profile data licenses multiple times. Run the utility in assessment mode and then in conversion mode to covert the People profile data licenses.
Make sure that you plan to run the License Conversion Utility on the development staging server during the following stages:
- During Planning stage (before migration):
Run the utility in Assessment mode to review your license compliance of your classic fixed, floating, licenses and to evaluate/determine the bundled licenses that you must purchase. - Run in Conversion mode:
- After you complete the initial BMC Helix Data Manager migration.
- After you complete a BMC Helix Data Manager delta data migration.
Steps to run the License conversion utility in Assessment mode:
- Download the License Conversion Utility from the BMC Electronic Product Distribution (EPD) site.
- Run the License Conversion Utility in assessment mode to evaluate the classic fixed, floating, and bundled licenses that you must purchase.
See Moving to the bundled license model by using the Bundled License Conversion Utility in Action Request System documentation.
The utility generates an Excel report about your license compliance and helps you to decide on the required bundled licenses you must purchase. - Purchase the relevant fixed and floating bundled licenses for BMC Helix Innovation Suite platform and application licenses.
Running License Conversion Utility on the new development environment:
Make sure that you run the License Conversion Utility on the new development environment during the following stages:
- After you complete the initial BMC Helix Data Manager migration (Stage 4: Initial data migration) on the development staging server
- When you restore the database to Gold Build Backup #1 (Stage 8: Perform prefinal data migration and validation)
- After you complete a BMC Helix Data Manager delta data migration. In this step, the utility runs for all available data but only converts data that has not yet been converted.
Prepare documents required for planning your migration project
Work with your BMC contacts to provide the planning documents to gather the required information and create a plan for your migration project. Use the documents to assess and define the scope of work for the migration. This information will help you plan your implementation and data migration activities.
Implementation planning documents—The Implementation planning questionnaire (*see SaaS permissions below) includes sections for you to add details of your existing environments and applications, integrations, configurations, custom plugins or java code, and custom AI jobs. The document also includes several script files for activities like reviewing workflow and field-level customizations. Use the updated document to understand the project requirements and define the scope of work for the migration.
Important
- Perform this activity for your existing on-premises system while the BMC team works on setting up your infrastructure.
- Download and install the BMC Helix Data Manager tool on your on-premises system.
For additional details about requesting your BMC Helix Data Manager download and installation details, see Stage 1: Activation and implementation plan: Install BMC Helix Data Manager, Developer Studio, and other client tools on the on-premises system.
Use the BMC Helix Data Manager tool to get accustomed to the migration process. All the data migration steps can be performed on your on-premises system, except the actual import of data, which requires transferring the exported data by copying it to the FTP location provided during the activation of the staging servers.
Based on the data assessment from the Implementation planning document, create the following plans:
Implementation plan—For development work that includes code updates, workflow customizations, integrations, configurations, custom plugins or java code, custom AI jobs, and any new development work.
Data migration plan—For form-level, table-level, and field-level data customizations.
To create the data migration plan:Evaluate your data volume and database size.
Investigate and document any custom forms or field updates to be added to the BMC Helix migration pack.
Project plan template—Use this document to define a project plan that includes the tasks needed for the different phases of your migration project. The plan should include the tasks:
You need to perform for the various stages.
To be performed by the BMC team.
To create support tickets and to track the implementation activity for those BMC tasks.
*SaaS permissions
As part of the implementation planning questionnaire, please note that your administrative permissions in on-premises will differ from the administrative permissions in SaaS.
- The on-premises "Administrator" permission is replaced by the structural administrator labelled as "Struct Admin" within the SaaS application.
- The on-premises "Sub Administrator" permission is replaced by the structural administrator labelled as "Struct SubAdmin" within the SaaS application.
The "Struct Admin" permission allows you to modify custom and overplayed objects in the Best Practices mode when using BMC Helix Developer Studio. You are unable to modify any coding in the Base Mode on SaaS.
Recommendations for integrations
On-premises integrations typically used service accounts with "Administrator" permissions. However, on SaaS, please use the application-specific permissions, such Incident or Change User, in addition to setting the client type of 34 - Web Service. For example, in a REST API, send a header X-AR-Client-Type with value 34.
Using the client type of 34 eliminates the following error:
Error Message: "User is currently connected from another machine or incompatible session."
Migration process overview
The following image provides an overview of the migration process:
Stage 1: Activation - Systems and tools
No. | Task | Action |
---|---|---|
1. | Activate required systems and BMC Helix installations. | BMC initiates the activations for the following systems and services required for your migrations after your ordering process is complete:
After the activation is complete, BMC sends you an email with the environment and access details for the products you purchased. Typically, the SLA for the activation request is seven to ten days. To view a sample of the email sent after activation of the environments, save and view the Activation Email. The email you receive includes the system details for your activated environments. Important:
|
2. | Install BMC Helix Data Manager, Developer Studio, and other client tools on the on-premises system. | While your BMC Helix environments are being activated, download and install the following tools on your on-premises staging server:
Important:
|
3. | Create realm entries and configure your SAML and Active Directory (AD) authentications. | Configuring SAML: We recommend that you create a realm for SAML authentication, and configure the general details for the realm. Obtain the necessary information from the IdP administrator and then configure SAML authentication. For more information, see Importing configuration from an identity provider and configuring SAML . |
Configuring Active Directory: After you configure BMC Helix SSO as a service provider and Active Data Federation Services (AD FS) as the remote identity provider (IdP) in BMC Helix SSO Admin Console, you can configure SAML for AD FS. For more information, see Configuring Active Directory Federation Services as a SAML identity provider . |
Stage 2: Activation - Lifecycle requests and staging servers
No. | Task | Action |
---|---|---|
4. | Lifecycle request: Create Configure the client gateway | Create a lifecycle request and support tickets to configure the client gateway required for the following scenarios:
For more information, see the following topics: |
5. | Request for development staging servers | The BMC OSS team provides a staging server template document to gather the details required to activate the staging servers; see the BMC Helix Data Manager Staging Server Request Form. After they receive the completed document, the BMC team works on the activation of the following items:
After the configuration is complete, the BMC team provides the required system and connectivity details via email. Important:
|
Stage 3: Development activities
Important
Package and deploy all configuration or environment changes or fixes applied on the development staging server during any phase of the migration to all your BMC Helix environments.
- Perform this activity after every database restore, unit testing, UAT, and your final UAT.
- If you do not apply these changes to all environments, create a request to reapply these changes after every database restore. Track these requests so that data from existing requests can be used as a reference for the changes to be applied.
No. | Task | Action |
---|---|---|
6. | Export and import customizations and overlays |
Important:
|
7. | Reconcile customizations |
|
8. | Perform custom development changes for the BMC Helix applications | Perform all custom development work done for:
|
9. | Configure third-party or other BMC applications integrations | You can integrate the BMC Helix ITSM system with your existing on-premises integrations that are supported in BMC Helix version 21.3. These integrations can include BMC TrueSight Operations Management, BMC Helix Discovery, and so on.
Important: You need to re-design third-party integrations that use integrations methods that are not supported. The supported integration methods include:
|
10. | Request database backup with customizations and integrations | Create a self-service lifecycle request to take a database backup with all the customizations and integrations. This backup is your Golden Backup #1 with the base data and customizations and integration information. For more information about creating self-service lifecycle requests, see Creating a lifecycle request for requesting services . Best Practice: We recommend that you create a package with all your customizations and fixes. |
Stage 4: Initial data migration
No. | Task | Action |
---|---|---|
11. | Configure BMC Helix Data Manager and prepare for migration | Complete the following tasks to configure your BMC Helix Data Manager on-premises and development staging server to prepare for migration:
|
12. | Execute the initial BMC Helix Data Manager data migration | Complete your initial data migration for the following applications by using BMC Helix Data Manager:
Important:
You are now ready to unit test your migration. |
13. | Run license assessment and conversion | Download and run the License Compliance Utility to convert the People profile data licenses. Important: Make sure you include this activity in your project plan. See Moving to the bundled license model by using the Bundled License Conversion Utility in Action Request System documentation. |
Stage 5: Perform unit testing and fixes
No. | Task | Action |
---|---|---|
14. | Perform unit testing and fixes | Before you begin the unit testing, make sure the following tasks are completed:
Complete the following steps to complete unit testing:
|
Stage 6: Delta Data Migration (Emulated cutover 1)
No. | Task | Action |
---|---|---|
15. | Perform delta data migration | Complete the following steps to perform a delta migration and apply unit test fixes:
Important:
|
16. | Run license conversion for delta data | Contact the BMC OSS team to create a support ticket to run the License Compliance Utility to perform an assessment and convert the new People profile data licenses. Important: The utility is run for all available data, and only People profile data that has not yet been converted is updated. |
Stage 7: User Acceptance Tests (UAT)
No. | Task | Action |
---|---|---|
17. | Perform UAT | Create a self-service lifecycle request to deploy Golden Backup #3 with the fixes to your BMC Helix QA and production environment. Important: It is recommended that you perform the following user acceptance tests:
Complete the tests and fix the issues found. |
18. | Complete UAT cycles, fixes, and sign-off | Fixing issues Use one of the following options to fix the issues that you find during your UAT cycles:
UAT sign-off Perform the required number of UAT cycles for the scenarios that apply to you, and make sure all blocker issues are resolved to get a successful UAT sign-off. Important:
|
Stage 8: Perform prefinal data migration and validation
No. | Task | Action |
---|---|---|
19. | Apply freeze restrictions | After the UAT sign-off, prepare for the final data migration and delta data migration (Emulated cutover). At this stage, enable freeze restrictions on your on-premises production system, if you were not able to freeze the activities in Step 7 of Stage 3: Development activities. For more information about freeze and restrictions, see the Change freeze requirements section in Planning your environment migration to SaaS . |
20. | Perform prefinal data migration and validation |
|
Stage 9: Emulated cutover 2
No. | Task | Action |
---|---|---|
21. | Perform a final Emulated cutover 2 |
Postmigration
The development staging server must remain in Quite mode during this go-live week and the database restore to the production environment should be done on go-live day, after the final data migration. We recommend that you do not have any further validations or testing in the BMC Helix production environment during this time. Important:
|
Stage 10: Go-live
No. | Task | Action |
---|---|---|
22. | Perform the final go-live delta data migration | Repeat the procedure described in Stage 9: Emulated cutover 2. |
23. | Go-live | Obtain the go-live reference template from your BMC contacts. Use this template to document all the tasks and details for the go-live activities. Going live includes the following activities:
Create the following tickets seven to ten days before going live:
Important to include in CRQ Please include specific instructions in the self-service lifecycle request for the BMC Change Team to point the database host to your long-term Development environment.
|
Comments
Please add the below text to the Step 7 of Stage 3 Development Activities as discussed with Murali, the text in double quotes is a hyperlink, please ensure the hyperlink is added and validated
---------------------------------------------------------------------------------------------------------------------- Apply freeze restrictions
At this stage, enable freeze restrictions on your on-premises production system
For more information about freeze and restrictions, see the Change freeze requirements section in "Planning your environment migration to SaaS."
Hello Ujjwala, Thank you for the comment. I have added the link as suggested.
Thanks, Dhanya
Log in or register to comment.