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

Methods for consolidating systems


Across the range of business scenarios, there are two logical methods for implementing a consolidation: import and merge.

Import

The data from one system is imported into another system.

worddav3f3d1948dd63330503c3136f998dd937.png

Merge

Two or more systems are logically merged into a third system that has been created specifically for this purpose.

worddavf2b5122044c74a0f30ef8904d39737b5.png
While a merge operation results in two or more systems being combined into a third system, you should perform this operation serially rather than in parallel. While it is technically possible to merge two or more systems simultaneously into another system, this results in an exponential increase in logistical complexity and a high level of interdependence between these operations. It is considerably more challenging to achieve a successful result by performing parallel consolidations.

For that reason, while the logical result of a merge consolidation is that two or more systems are combined, in practical terms, this would be performed as a distinct migration for each source system by following the steps outlined below.

Step 1

Import Original System A into New System. This a relatively straightforward operation as no data or users are in the target system. The process is similar to the Staged Upgrade process.

worddave9377771a1d71bc6a7ef35a5e46b16eb.png

Step 2

Import Original System B into New System. This is relatively complex because the target system is in use and has live data in place. This process requires specific methods that support the importing of data into an in-use production system.
 This process applies to each subsequent BMC Helix ITSM system that is merged into the target.

worddav78e9761d9e1437313c6cf949aaf26f81.png

The Merge consolidation method typically offers has several advantages over an Import consolidation:

  • The new system can be created with a clean installation of ITSM, ensuring only known data and customizations are included. This configuration can be prepared to be compatible with all the systems that will be consolidated.
  • The new system can be a higher version of ITSM than the originating systems, enabling the consolidation to be combined with an upgrade. This offers the user community an advantage in exchange for their support through the consolidation process.
  • Only selected data from the originating systems is included in the consolidated system, ensuring data integrity.
  • Only known customizations needed for the source systems are implemented.
  • Shared data is preconfigured to support the customers who will be merged into it.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*