Sys IDs of OOTB roles are different in different instancesSummaryThe sys_id for the Example 'itil' role will not be consistent across every single ServiceNow instance.The assigned sys_id value for a record in an instance is dependent on how a record is loaded into an instance.For example, when you clone a production instance to a sub-production instance, the sys_id for the 'itil' role will remain consistent between those two instances, as the sub-production instance is a copy of the production instance.Situations, where the sys_id for a given record may not be consistent, includes zBooting an instance, activating plug-ins, or when the development team creates a brand new record for the 'itil' role as part of feature updates.When it comes to plug-in activation, the sys_id for the plugin itself varies across different instances, but the hard-coded XML files that are loaded to the instance as a result of plug-in activation will use consistent sys_ids.As part of best practices, we recommend cloning the production instance to sub-production instances so that sys_id values for base-level data can remain consistent across the ecosystem and that this inconsistency may be minimalized to only what is generated by source code per instance.Related LinksUpdate set transfers: https://docs.servicenow.com/csh?topicname=update-set-transfers.html&version=latest