What is impact of migrate Business Service from CMDB CI Services to a new class?

Shantharao
Kilo Sage

Hi All,

What is the impact of migrating Business Service from CMDB CI Services to a new class?
How can we convert, what are the best practices for moving CIs from one class to another class?
What is the risk and impact analysis we should notify the client?

Thanks for your help

2 REPLIES 2

Ashok Sasidhara
Tera Sage
Tera Sage

Following are some of the best practices:

1. For the records which are business services as per CSDM definition, you should plan to migrate only to the Business service (cmdb_ci_service_business) class. All the attributes are same as it is a child of cmdb_ci_service and also there are no additional attributes specific to this class. 

2. For the records which are technical services as per CSDM definition, the data should be migrated to Technical service (cmdb_ci_service_technical) class. In this case also, all the attributes are same as it is a child of cmdb_ci_service and also there are no additional attributes specific to this class. 

3. For records which are identified as application services, there are certain additional attributes specific to application service (and it's child classes) in addition to the attributes inherited from the parent cmdb_ci_service. You should look at the following process of converting business service to application service:

https://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/service-mapping/conce...

4. Also consider the CSDM migration steps mentioned in the following URL wherever applicable:

https://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/csdm-implementation/task/mi...

 

Also in general, you need to consider the following best practices for any CI class migration:

i) The attributes are properly mapped from the current class to the new class

ii) All the existing CI relationships are preserved

iii) Audit history, related list, activities etc. should be preserved

iv) All the existing references in task records like incidents, problems, changes etc. should be preserved

v) Link with asset records (if applicable) should not be affected and the linked asset records shouldn't get modified

vi) Consider adding tags to the applicable records before and after migration for the purpose of tracking

Arul5
Tera Contributor

Hi,
I have a thought, but I am not sure whether its correct or not.

 

Since the new business service class (cmdb_ci_service_business) has exact same fields / Attributes as the service class (cmdb_ci_service), what happens if we change the class value from old  to new through script?
By following the above step will result in migrating the records to new Business Service class (i.e cmdb_ci_service_business).

 

Please correct me if I am wrong. 

 

Thanks 

Arul