- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2019 11:05 PM
My organisation is investigating a migration from another toolset to ServiceNow, and we are looking at the CSDM information / whitepapers / etc which have been posted.
Our existing CMDB is reasonably mature and we are looking at the CSDM with interest, but wondering whether CSDM is something we need to consider early in our ServiceNow journey, or if we can deploy a traditional CMDB with a view to expand into the capabilities defined within CSDM once we are Live in the ServiceNow toolset?
Are there any aspects we should keep in mind if we go down a traditional CMDB path which would make our expansion at a later time more straight forward?
Really appreciate the forums thoughts, experiences and advice.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2019 05:52 AM
I would say that you should consider CSDM from the beginning. As you migrate into SN CMDB, you should migrate your data over to the CSDM format. However, you don't need to populate all the data suggested by CSDM. So where you have data, put it where CSDM suggests. If you dont have the data, then it remains unpopulated at this time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2019 01:52 AM
I agree with SNFan. Considering the schema of the CMDB, you will have different fields available depending on the class you choose, so migrating from your existing tool to ServiceNow without considering CSDM may give you more trouble than you save by not considering it.
So if I were starting from scratch in ServiceNow, I would most likely always go for the recommended utilization, i.e. CSDM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-26-2019 12:32 PM
