Pushing CMDB data from Instance 1 to Instance 2

[varunkumar11863]

We have a requirement to push CMDB data available in Instance 1 (PROD instance) to Instance 2 (another PROD instance).

While it is possible using various options like APIs, Service Bridge (soon) etc., question would it lead to license cost on Instance 2 as well? We only need subset of data (e.g. VMs, DBs, etc.) which are actually licensable categories. We didn't get clear answer as Sales team confirmed if we use ITOM related table, it will be charged. What if we create custom table and extend the attributes needed? Has anyone done this before ensuring it didn't duplicate the cost?

There are other options like enabling Discovery on Instance 2, let's that something we cannot do.

Thanks for your time.

[Maik Skoddow]

Hi @varunkumar11863 

Copying raw CMDB data from Instance 1 to Instance 2 in itself does not automatically incur additional license costs on Instance 2. However, the situation becomes more complex when the data involves tables that are part of licensed products such as ITOM Visibility, ITOM Discovery, or Service Mapping.

Many of the CI classes you may want to replicate—such as Virtual Machines, Databases, Load Balancers, etc.—reside in scoped applications or plugin-based tables that are tied to specific licensed features. If these tables do not exist on Instance 2 (because the corresponding plugins/products are not activated), you would either need to:

1. License and activate the same products on Instance 2 – which would result in additional licensing costs, or

2. Store the data in custom tables – this could help you avoid triggering license implications, but may come with functional trade-offs. For example, the data would no longer be part of the core CMDB hierarchy and wouldn't benefit from built-in platform capabilities like Dependency Views, CMDB Query Builder, or CI Class Manager. It could also impact future integrations or ITOM use cases.

In general, if the data being stored maps to ITOM-licensable classes - even if imported manually or via API - this could still be subject to licensing considerations, especially if those classes are part of your license entitlement metrics (e.g. IP-based licensing, node count, etc.).

Recommendation:
Engage with your ServiceNow account team or licensing specialist to clarify licensing impact based on your specific use case, especially regarding the use of custom tables versus extending the CMDB model. Each licensing agreement can vary slightly, and it's important to validate assumptions before proceeding.

Maik

[varunkumar11863]

Hello Maik,

Thank you for your response. If we create custom VM table and save the data, would it be considered as non-compliant and can lead to ServiceNow recommending moving data to OB VM table (eventually leading to license implications)?

[Maik Skoddow]

Hi @varunkumar11863 

did you read my previously answer carefully? I think everything is said!

Maik