This version of the software is currently available only to customers in the Controlled Availability (CA) program.

Customize and system test phase for on-premises to on-premises migration

During the customize and system test phase, migrate your customizations from your production system, and create a backup of the target database with the migrated customizations. Then, unit test and remediate the customizations and migrate the first full set of data to your to-be-production system.

The target milestone for this phase is to successfully complete system testing. 

An overview of the tasks involved in this phase is provided in the following image:


TaskDescriptionReference information

7.

Migrate customizations

Migrate your customizations from your current production BMC Helix ITSM system.

Upgrade process for BMC Helix ITSM Open link (Steps 9 - 10)

Moving your customization to a new target system Open link

8.Import and reconcile the customizations

Import the customizations to the development system. This process includes migrating CMBD and workflow customizations and using three-way reconciliation to validate your customizations, including workflows and integrations, after migration.

9.Unit test and remediate the customizations

Unit test the migrated customizations and remediate them in the development system.

You may have to do multiple rounds of testing before all issues are fixed after the unit testing.

10.Create an export package with the fixes

Create an export package of the customizations and unit test fixes from the development system.

Running and reviewing migration jobs

11.Restore the Gold Build backup

Restore the latest Gold Build backup on the to-be-production server.

This image includes the out-of-the-box ITSM application, but with no migrated data.

Not applicable

12.Deploy the export package and take a backup

Deploy the export package with the workflow customizations into this image and take another backup of the system.

This is your third Gold Build backup. This image includes the out-of-the-box ITSM application and workflow customizations.

We recommend keeping the bulk data out of the gold build for as long as possible. For more information, see Managing the gold build image.

Running and reviewing migration jobs

13.Configure BMC Helix Data Manager for custom migration

Rediscover the to-be-production data dictionary with the full set of customizations by using BMC Helix Data Manager.

Download and update the migration pack to apply any customizations, filters, enrichments, and transformations required for the final migration. 

This includes:

  • Creating migration packs for your data
  • Identifying and fixing data mapping issues
  • Performing optional form analysis
  • Approval enrichment mappings
14.Run the clear-down migration pack and take a backup

Prepare your to-be-production system for data migration by running the clear-down migration pack on the system to delete any sample or unwanted data.

Preparing the system before migration

15.Perform a full data migration using Helix Data Manager for system testing

Perform an end-to-end migration of the production (source) copy to the to-be-production (target).

Export the production database, import it into the to-be-production system, and run all the post-migration scripts.

16.Test system and apply fixes

Perform a full application and integration testing of the to-be-production system to ensure this environment is tested thoroughly prior to go-live. Use documented tests to ensure that you test the full range of the application and integrations. You can reuse these test cases during the user acceptance testing phase.

  • Develop fixes for issues and create an export package of the updates.
  • Restore the Gold Build backup from Step 12 to the to-be-production system, deploy the export package with the fixes, and take a fresh Gold Build backup.
     
    Important:
    The restored Gold Build backup should include the fixes applied to the to-be-production system after the testing cycle.

  • Deploy the export package with the fixes, and then take a backup. 
  • We recommend that you repeat this process until your data is production-ready.

We strongly recommend that you record all issues and resolutions in a spreadsheet or fault tracking system. Track any data or workflow changes and copy the changes to the Gold Build backup.

Not applicable

Where to go from here

User acceptance tests for on-premises to on-premises migration

Was this page helpful? Yes No Submitting... Thank you

Comments