Build phase for on-premises to on-premises migration

Set up the environments for migration and backup database for the baseline

Set up the infrastructure necessary to support the export of data from your production system.

Set up the environments with the upgraded versions of BMC Helix ITSM. Make sure that the systems have drive space large enough for your production database data.

After the systems are set up, take a database backup of the development system before any changes are made. This is the data provided out-of-the-box with the fresh installation of BMC Helix ITSM.

This backup is your first Gold Build backup.

Install and configure BMC Helix Data Manager

Install BMC Helix Data Manager on the virtual machine you requested during the project setup phase. 

Verify that the BMC Helix Data Manager server or any other file system you plan to use has drive space twice the size of your source database so that you have enough space for migration data export.

Preparing for upgrade

Installing

Prepare the file system for the import and export of data, including: 

1. Registering-source-and-target-systems
2. Running database integration to create a BMC Helix Data Manager user on both, the source and target systems
3. Discovering-data-dictionaries for both, current production (source) and the development (target) systems
4. Configuring your file system
5. Importing appropriate metadata
6. Copying the data migration pack templates to use newly discovered Data Dictionaries
7. Resolving form mapping issues
8. Running the clear-down script on the development system and taking a database backup.
   This backup is your second Gold Build backup.

Setting-up-BMC-Helix-Data-Manager-Workbench-for-migration

(Optional) Full export of OOTB data

Important:  Steps 3-6 are optional. Complete this process to set up a QA environment to test performance issues, train, and provide some data to test customizations. The procedure requires additional time to set up the QA environment.

To skip this process, continue to the Customize-and-system-test-phase-for-on-premises-to-on-premises-migration after step 2.

Take a full data export of all in-scope production data on your production server. 

This activity is useful for identifying any configuration or performance issues, training, and providing some data to test customizations. The duration here is critical and will help you plan the rest of the data migration activities. 

Important:

We recommend that you do a complete data export before you import data into the system. This data export can be used to revert to the last working data import.

Not applicable

(Optional) Import OOTB data

Import the exported data into your development environment and resolve any import errors that might occur. Then apply the typical post migration scripts and server name changes. 

Important:

We recommend that you run the form count reconciliation at this stage and review the results to ensure that you understand what data is excluded from the scope of migration.

Completing-postmigration-steps

(Optional) Update server references

Update the server references of the development environment data by using the BMC Helix Data Manager-based process to match the QA environment configuration.

Updating-server-references

(Optional) Migrate data

Migrate the development data to the QA environment by using BMC Helix Data Manager. 

Important: 

This data is for test purposes only and is not used in the migration process. 

Migrating-data