CSDM migration

[Suman21]

Hi,

We are in process of migrating the CSDM 1.0 to CSDM 4.0.

For this we are migrating the CI's  from old table to new table in below way

Legacy Table                                           ---------> CSDM New Table

Application Service (cmdb_ci_service) -------> cmdb_ci_service_auto

Technical Service (cmdb_ci_service) ----------> cmdb_ci_service_technical

Business Service (cmdb_ci_service) ----------> cmdb_ci_service_business

In legacy table (cmdb_ci_service) we used  Service Classification to segregate the Application, Technical , Business service CI's.

Now we are using the "Convert to Application Service" Tab to move new table.

Same for Technical Service "convert to Technical Service" and Business Service  "Convert to Business Service"

However, we identified that by simple using the "Class" field  on the List view, we can move the CI's to new table.

Said that we are not sure if it a good practice to move the CI's in that way (using List view to change class)

or do we need to follow the "Convert to Application Service" tabs.

Which one is recommended way to migrate the CI's to new class.

[Rub_n Ruiz Tris]

Hello,

I recommend to use the “Convert to...” options provided by ServiceNow. These conversion actions are designed to handle not only the class change but also the necessary updates to relationships, attributes, and data integrity validations required by the CSDM 4.0 model.

Simply changing the Class field from the list view may technically move the CI to a new table, but it bypasses important logic and validations. This can result in incomplete or inconsistent data. 

Maybe this video from ServiceNow on the subject will help with it: https://www.youtube.com/watch?v=3uQM7DAE6Xk

Hope that Helps!

Please mark this response correct by clicking on "Accept as Solution" and/or mark it as "Helpful" (kudos) if it helps.