Exclude Tables hardcoded during cloneRelated LinksList of hardcoded tables which will be excluded during clone is as follows:- Any tables with the attribute "no_replicate=true" will be excluded by default. *** Please do not change this attribute from OOB as it can have adverse effect on the functionality. Please raise your query to customer support if you have any follow-up questions. https://<instance_name>.service-now.com/sys_dictionary_list.do?sysparm_query=attributesLIKEno_replicate&sysparm_view= In addition to that there are a few tables which have instance specific details/data. ****There is a possibility that some of these tables will not be available on your instance and that is expected. sys_email_account, sys_ha_database, sys_cluster_control, sys_cluster_message, sys_cluster_state, sys_db_category_pool_mtom, sys_db_pool_node_status, sys_db_pool, sys_replication_heartbeat, sys_db_category, gateway_clone, gateway_config, gateway_group_connectivity, gateway_node_connectivity, gateway_table, gateway_table_group, sys_push_notif_app_install, sys_service_authentication, sys_service_endpoint, ais_connection, ais_index_queue_stats, ais_publish_history, ais_partition_health, ais_partition_health_response, ais_ingest_datasource_stats, ais_ingest_retry_stats, ais_ingest_table_stats, ais_ relevancy_autotrain_solution, ais_relevancy_solution_definition, ais_relevancy_training_execution, ais_relevancy_training_staging, s3_attachment_storage_config, sn_occ_lease_state, sys_instance_state, sys_kmf_key_metadata, sys_kmf_module_key, sys_kmf_instance_key, sys_kmf_certificate, sys_kmf_ephemeral_key, dare_key_metadata, dare_key_request, dare_key_quorum_request, sys_db_replicated_table, sys_kmf_external_key, ldap_server_config, ldap_ou_config, ldap_server_url, ua_defn_agg_data Above tables if present on the source instance will be excluded OOB during a clone. This KB have more information on the skipped notifications on the clone change:- Clone notifications: Following tables/views cannot be preserved/excluded, skipping : []