Customize and system test phase

7. Export customizations

The customer's workflow customizations that are in scope of the migration to the cloud are exported from one of the on-premises systems.

8. Import and reconcile customizations

The workflow customizations that are in scope of the migration to the cloud are imported into the onboarding system. You can use three-way reconciliation and other analytical tools to manage the successful deployment of these customizations.

During this phase, the QA system with the out-of-the-box ITSM application and all customer data is a useful reference for the behavior of a non-customized system.

9. Migrate additional data to support unit testing

The onboarding system previously had the out-of-the-box on- premises data imported into it. This data is useful for unit testing. It might also be necessary to import additional data for custom forms or fields to validate correct application behavior. To migrate this data, use BMC Helix Data Manager.

10. Unit test and remediate customizations

The project team unit tests the migrated customizations and remediates them in the development environment.

11. Package code changes and update gold baseline

The package of customizations and unit test fixes are exported and then the gold baseline image is restored. This gold baseline has the out-of-the-box ITSM application but with no migrated data.

The workflow customizations are deployed into this image and another gold backup is taken.

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.

12. Configure BMC Helix Data Manager for custom migration

BMC Helix Data Manager is used to discover the new data dictionary with the full set of customizations. This discovery is exported and imported into the on-premises instance, and a fully custom migration pack is created, enabling migration from the on-premises ITSM system to the customized BMC Helix ITSM system.

13. Full custom application export for system testing

14. Full custom application import for system testing

The on-premises database is updated with a fresh database backup from the production system. Then, a full data migration (including all custom fields and forms in scope of the migration) is performed. The export is done from the on-premises system. The files are FTP transferred to the cloud and then imported into the onboarding system. Perform this migration immediately prior to the start of system testing to ensure that time-sensitive data testing can be performed.

Server references in the data should be set appropriately for the to-be production system.

15. Server reference updates and database backup for to-be- production

The server references are updated by using the BMC Helix Data Manager based process to match the production environment configuration. Then, the project team backs up the onboarding database.

16. Restore custom application database

The BMC Helix Operations team restores the onboarding database backup to the production database.

To request any type of data movement from one environment to another, follow the BMC OnDemand Change Management policy. Use the Request a Change option from within the i.onbmc.com support portal.

17. System testing

The internal project team performs full application and integration testing of the system. This testing is done prior to exposing the system to the customer to validate that the system is working correctly. This testing is performed in 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.

You can develop fixes for issues directly in the production or onboarding system and then promote the fixes to the to-be-production system.

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 database image.

18. Restore gold backup and deploy system test fixes

The gold image database backup is restored back to the onboarding system and all data and workflow changes performed during the system testing phase are implemented in the gold image. After all changes are deployed, a new database backup with all of these fixes is taken.