--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Convert manual services to application services using API # Convert manual services to application services using API {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Convert manual services to application services using API In the Australia release, manual services are deprecated and replaced by application services to enhance Event Management's ability to monitor service performance and detect health issues. Existing manual services must be converted to application services using a JavaScript API. This conversion retains the original service attributes and configuration items (CIs), but requires prior testing of any automation related to manual services. Show full answer Show less ## Key Details and Process * The conversion moves manual service records from the **Manual Services \[cmdbciservicemanual\]** table to the **Mapped Application Service \[cmdbciservicediscovered\]** table by changing the record class. * Original attributes such as name, owner, and operational status are preserved in the new application service. * Configuration items associated with the manual service remain linked after conversion, with the system updating CI changes and applying impact rules. * The maximum number of CI connections added during conversion is controlled by the **sa.service.maxciservicepopulation** system property, defaulting to 1,000. Increasing this value can cause performance issues. * It is recommended to convert services in small batches (\~10 at a time) to better manage and troubleshoot conversion errors. ## Important Constraints and Considerations * Certain CI types are not supported in application services and must be removed before conversion: * cmdbciendpoint * cmdbcitranslationrule * cmdbciconfigfile * cmdbciqualifier * cmdbciapplicationcluster * If your instance uses domain separation, conversion fails if CIs from multiple domains exist in the same manual service. Only CIs from the application service's domain are retained post-conversion. * Manual services are static post-conversion. To update them with the latest CMDB state, either repopulate the original manual services or run an update with the CMDB changes option after conversion. ## API Usage The JavaScript API **BusinessServiceManager.migrateManualToApplicationService(String serviceid)** converts a manual service to an application service. * **Parameter:** `serviceid` - the sysid of the manual service to convert. * **Returns:** Boolean indicating success (`true`) or failure (`false`). **Example:** var bsManager = new SNC.BusinessServiceManager();var res = bsManager.migrateManualToApplicationService("451047c6c0a8016400de0ae6df9b9d76"); ## Practical Implications for ServiceNow Customers ServiceNow customers should plan to convert all manual services to application services using the provided API to maintain compatibility with Event Management features. Prior to conversion, ensure any automation related to manual services is fully tested. Remove unsupported CI types and verify domain separation constraints to avoid conversion failures. Use the system property to control CI connection limits during conversion and process services in manageable batches for easier troubleshooting. You can use a JavaScript API to convert existing manual services to application services. Event Management can use application services to monitor service performance and identify health issues. Manual services are no longer supported and this service type, as well as discovered services, have been replaced by application services. Any existing manual services must be converted to application services. Ensure that any automation of manual services (such as business rules or scheduled jobs) have been built and tested before converting to application services. Note: Manual services are static and retain their original structure after conversion to application services. To update imported manual services with the existing CMDB state, either populate the original manual services to ensure that all CIs are assigned to the correct service, or run the update with CMDB changes option after the conversion. During the conversion process: * The manual service record is moved from the Manual Services \[cmdb_ci_service_manual\] table to the Mapped Application Service \[cmdb_ci_service_discovered\] table by changing the record class. * All the original manual service attributes, such as, name, owner, and operational status, are retained in the application services. * The configuration items (CIs) of the manual service are retained in the application services after the conversion. * The system queries the CMDB for the latest CI changes and applies CI impact rules. {#convert-manual-to-application-service__ul_os3_3t3_tcb} The maximum number of CI connections added to application services during this operation is controlled by the [sa.service.max_ci_service_population](https://www.servicenow.com/docs/access?context=components-installed-app-services&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) property. By default, the value is 1,000 (one thousand connections). Increasing the number of CI connections may cause performance issues. To adjust the maximum number of added CI connections, add the sa.service.max_ci_service_population property, as described in [Add a system property](https://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&version=australia&pubname=australia-platform-administration&ft:locale=en-US). Attempting to process more CIs than the value specified in the sa.service.max_ci_service_population property causes the operation to fail. Run the conversion process in small chunks of approximately 10 at a time. This makes it easier to pinpoint the problematic service if a conversion problem occurs. Application services do not support these CI types: * cmdb_ci_endpoint * cmdb_ci_translation_rule * cmdb_ci_config_file * cmdb_ci_qualifier * cmdb_ci_application_cluster {#convert-manual-to-application-service__ul_jqt_ftx_mdb} If the preceding CI types are used in the manual service that you want to convert, the conversion fails. CIs of this type should be removed before conversion. They can be replaced by adding new CIs to the application services after conversion. If your ServiceNow instance uses domain separation, the conversion fails if CIs from multiple domains are in the same service. Replace or remove relevant CIs before conversion. The converted application services contains only CIs assigned to the same domain as the application services. The JavaScript API is: BusinessServiceManager.migrateManualToApplicationService(String service_id) {#convert-manual-to-application-service__table_dml_r31_4t__entry__3} | Name | Type | Description | |-|-|-| | service_id | String | sys_id of the manual service to be converted | [Table 1. Parameters] {#convert-manual-to-application-service__table_dml_r31_4t} {#convert-manual-to-application-service__table_eml_r31_4t__entry__2} | Type | Description | |-|-| | Boolean | `true` for a successful conversion, `false` for a conversion that failed | [Table 2. Returns] {#convert-manual-to-application-service__table_eml_r31_4t} Where the `sys_id` of an existing manual service is 451047c6c0a8016400de0ae6df9b9d76, run the following API to convert it to an application services: var bsManager = new SNC.BusinessServiceManager(); var res = bsManager.migrateManualToApplicationService("451047c6c0a8016400de0ae6df9b9d76"); **Related topics** * [BusinessServiceManager - Global](https://www.servicenow.com/docs/access?context=BusinessServiceManagerAPI&version=australia&pubname=australia-api-reference&ft:locale=en-US)