Export-import multiple Tag-based services between instancesSummaryThis is a workaround procedure to migrate multiple Tag-based services between instances. The procedure known as "Export service definitions" doesn't support Tag-based services as they rely on unsupported manual endpoints.ReleaseRelevant for releases: Orlando, Paris, Quebec.InstructionsExport the following tables as XML: svc_tag_categoriessvc_tag_namessvc_by_tags_service_familiessvc_by_tags_service_family_categories_m2mcmdb_ci_service_by_tags The table cmdb_ci_key_value should be populated on the target instance with key-value tags for the CIs. This information will be used to re-populate the migrated Tag-based services on the target instance.The migration procedure only transfers service definitions (which categories, families, and tags to use). Import the tables on the target instance in the following order: svc_tag_categoriessvc_tag_namessvc_by_tags_service_familiessvc_by_tags_service_family_categories_m2mcmdb_ci_service_by_tags Run the following background script to add services to the service model, and to find & populate the CIs according to the service definitions var mUtils = new ServiceMappingUtils();var populator = new SNC.ServicePopulatorRunner('SCHEDULED');var gr = new GlideRecord('cmdb_ci_service_by_tags');gr.query();while(gr.next()) { mUtils.resetModel(gr); populator.run(gr);}