EOL: Enterprise Release Management - Upgrade Path for existing customersEnterprise Release Management (ERM) application (plugin - com.snc.enterprise_release_management) being shipped with ITBM product line is approaching end of life from Orlando release. ServiceNow will provide support for this application until Quebec release and no new enhancement requests or new features would be entertained for this from Orlando release. This article will provide the existing customers of this product with options for way forward. Q: What it means "End of Life from Orlando Release onwards"? A: No new enhancement requests or feature requests for this application would be accepted henceforth. Customers will not receive any future versions of this application. Q: What will happen if Enterprise Release Management plugin (com.snc.enterprise_release_management) is activated on my instance and I'm not using it? A: Nothing. If you wish to deactivate this plug during the next upgrade, you may wish to do so. Q: What should I do, if Enterprise Release Management plugin (com.snc.enterprise_release_management) is not activated on my instance but I want to use release management functionality in future? A: Servicenow will provide release management capabilities through Release Management application (plugin - com.snc.release_management_v2). This is an existing application which provides capabilities similar to Enterprise Release Management. All ITBM customers who were entitled for Enterprise Release Management are entitled for Release Management as well. There are no licensing implications in using Release Management. Q: What will happen if Enterprise Release Management plugin (com.snc.enterprise_release_management) is activated on my instance and I'm using it? A: You are provided with below options for way forward. Option 1: Continue to use the ERM for existing releases being managed through it and start using Release Management for all new Releases. In this case, you will not migrate any data from ERM over to Release Management. Option 2: Migrate existing Releases (both enterprise and product releases) being managed through ERM to Release Management by suitably modifying the sample migration scripts being provided with this document. The script will help you migrate data from ERM to Release Management application.For all future releases, use the Release Management application.We have seen minimal usage of Deployment Management entities (pipelines, builds, commits, repositories, CI servers). If you are using these entities, you can continue to use them within Enterprise Release Management. Sample Script for data migration Download the update set attached with this article.Import, preview and commit the update set in a test instanceThis update set creates a scheduled job by name - 'Enterprise Release Management to Release Management V2 Migration'This scheduled job can be run to convert All enterprise releases (with associated entities,phase and task) to releases in Release Management. Table mapping details are given below. All product releases (with associated entities such as stories, epics, problems, defects etc.) to releases in Release Management. Table mapping details are given below. Please note both enterprise release and product release are mapped to release entity in Release Management application The script include, 'ErmToRmV2Migration', which is run as part of the scheduled job, is a sample script This script needs to be reviewed and modified to suit to your requirementsThis provides a field to field mapping between ERM tables and Release Management tables. Please review these mappings and add additional or custom fields that you would have added.This script also provide mapping between states of ERM and Release Management tables. Please review and modify based on your requirement. Please also note, in the scheduled job, you can provide specific enterprise releases or product releases that you want to migrate. If you don't provide any parameters, it would migrate all enterprise releases and product releases in to release entities in Release Management. If you run this job multiple times without the parameters, duplicate release entities may be created. To provide specific enterprise and product releases, apply right filter in the list view, copy the query condition and provide it as parameter in the variables, 'encodedQueryForEnterpriseReleases', 'encodedQueryForEnterpriseProductReleases' given the scheduled job. For example - encodedQueryForEnterpriseReleases = 'priority=3' Please make sure you run the scheduled job in a test instance first, verify the data migrated before running it in the production instance. Table mapping For enterprise release Enterprise Release Management table Release Management table sn_erm_enterprise_releaserm_releasesn_erm_enterprise_release_phaserm_release_phasesn_erm_enterprise_release_taskrm_task For product release Enterprise Release Management table Release Management table sn_erm_product_releaserm_releasesn_erm_m2m_product_release_taskrm_m2m_release_task