Consolidation process
Consolidation is the process of merging one or more BMC Helix ITSM systems together. Consolidations of BMC Helix ITSM systems are complex projects involving data transformation and merging of large data sets. This process is technically complex and logistically challenging. However, a successful consolidation can result in significant cost savings and operational benefits.
- Analysis of differences in the data models
- Development and unit testing of the data migration and transformation configuration
- Technical validation of the accuracy and effectiveness of data migration
- Validation of the application behavior for the users being migrated into the target system and the existing users
- Emulation of the cutover process
- Support testing
- Migration to production
The following steps provide a high-level reference for an initial full end-to-end migration. Different steps might be necessary if you are running a Copy and Upgrade migration, running delta data migrations, or making changes to the data set as part of the upgrade (for example, adding new SRDs). If you are not experienced with BMC Helix Data Manager, contact your BMC account manager to discuss options for training or professional services.
- Migrate customizations from source to target system:
- Migrate CMDB extensions and run CMDB Sync UI if there are field extensions.
- Migrate overlays and customizations in Best Practice mode.
- Review and reconcile special data sets.
- Import the template migration packs. (See also Migration-packs-that-support-upgrades.)
- Set up BMC Helix Data Manager Workbench for migration.
- Discover form counts, application data, and server references on source and target systems.
- Copy the migration packs for your source and target systems:
- Environment Upgrade
- Global Data
- Clear Down
- Prepare your target system for data import:
- Clear down SLM sample data.
- Configure baseline data configuration.
- Run a Delete job to back up and delete sample and unrequired data (does not include custom forms unless you add them to the Clear Down migration pack).
- Back up the target database to create a "Gold" baseline.
- Tailor the migration packs for your customized systems:
- Add custom forms.
- Resolve field mapping issues.
- Configure data enrichment mappings.
- Review, compare, and configure optional form data from the discovered application data.
- Migrate global and company data using the tailored migration packs.
- Perform postmigration actions in the target system:
- Build SLA targets and agreements.
- Build approval chains.
- Configure entitlements.
- Update multitenancy permissions.
- Trigger an FTS rebuild.
- Configure and update server references.
- Discover form counts on the target and compare form counts on the source and target to validate the data migration. Data reconciliation is an essential step for any data migration. Contact BMC Support for details on any discrepancies you cannot resolve.
A consolidation project is likely to include a range of other activities not described here, such as training, communications, integration management, stakeholder management, auditing, and compliance. This documentation is not intended as a guide to all activities within a consolidation project and focuses on the technical aspects of this process.
The following diagram shows Gantt-style representation of the sequence and relationship between these activities. The relative duration of these tasks is not reflected in this diagram. The lapsed time and effort will depend on your local installation.
This diagram illustrates when the bulk of the work for that activity takes place, for example, some of the preparation work for data migration will take place much earlier.
The Infrastructure Preparation and Manage Customizations activities typically overlap because you can start managing the BMC Helix ITSM customizations before all components of the infrastructure are complete.
The Consolidation Analysis activity represents the analysis of the systems to be merged to identify data configuration and application workflow that must be synchronized as part of the consolidation. The output from the Consolidation Analysis is important for the correct estimation of effort and identification of impacted users and required resources to support the consolidation project
Reducing the number of multitenant BMC Helix ITSM systems
Customers who manage ITSM as a service on multitenant BMC Helix ITSM systems often have more than one multitenant system for various reasons including geographical performance or legal constraints. By merging multitenant environments to create fewer multitenant environments, business can reduce hardware and software costs and improve operational efficiency.
Typical approaches are to:
- Move companies from an existing multitenant ITSM system to an existing, in-use multitenant system.
- Move companies from two or more multitenant ITSM systems to a new, clean BMC Helix ITSM system.
Any consolidation operation can cause some level of disruption for the customers of a multitenant system. Combining the consolidation of multitenant systems with an ITSM application upgrade can offer clear business benefit to the customer, and this is a common component of these types of consolidations.
Moving a customer from an on-premises ITSM system into an existing multitenant system
Onboarding a customer from an existing on-premises ITSM system into a multitenancy system managed by a different company is effectively a consolidation of the two BMC Helix ITSM environments. Multitenant BMC Helix ITSM systems typically have a high level of control around the shared application data. On-premises customers usually make free use of the shared data configuration in ITSM. Onboarding a customer into a multitenant system usually involves analysis and transformation of the data to ensure there is no impact to existing customers.
Merging two businesses using BMC Helix ITSM
When two companies (or business units within the same company) merge their operations, significant reductions in costs can be achieved by consolidating the BMC Helix ITSM systems. This operation is likely to involve high levels of data transformation as the use of BMC Helix ITSM in the two businesses is likely to have a number of differences with no shared data discipline in either system.