---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/application-development

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Configure the system property to enable migration to ReleaseOps

# Configure the system property to enable migration to ReleaseOps {#ariaid-title1}

* Release version: Australia
* 
* Updated October 22, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Update the sn_deploy_pipeline.migrate_releaseops system property to enable deployments using ReleaseOps.

## Before you begin

Role required: admin or app_engine_admin

You must have ReleaseOps installed and set up on your production and other pipeline environments to complete the following procedure. See [Migrating App Engine pipelines to ReleaseOps](https://www.servicenow.com/docs/IdaGlHgAgInWTdZp2YsOYg "Starting with version 28.2.1 of AEMC, you can migrate your existing App Engine pipelines to ReleaseOps. Learn more about the migration process and benefits of migrating to ReleaseOps.") for more information.

## Procedure

1. On your production instance, navigate to AllSystem PropertiesAll Properties.
2. In the search bar, enter <kbd class="ph userinput">sn_deploy_pipeline.migrate_releaseops</kbd> and select the Enter key.
3. Select the sn_deploy_pipeline.migrate_releaseops property from the list.  
   Note:  
   By default, the sn_deploy_pipeline.migrate_releaseops property value is set to false.
4. **Optional:** If you aren't in the correct application scope, select the link to open the record in the correct scope.
5. In the Value field, enter <kbd class="ph userinput">true</kbd>.  
6. Select Update or select and hold (or right-click) in the header and select Save to update the record.

## Result

You have set the sn_deploy_pipeline.migrate_releaseops system property to enable migration to ReleaseOps.

## What to do next

If you customized your ReleaseOps deployment request states, you must map the deployment request states onto the corresponding App Engine deployment request states. See [Map deployment request states](https://www.servicenow.com/docs/4s5O8uI~CEjzdppmp8fYTA "If your ReleaseOps deployment request has custom states, you must configure the Deployment Request State Map table so that your ReleaseOps deployment request states map to the correct App Engine states.") for more information.

*[\>]: and then