---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Migrating App Engine pipelines to ReleaseOps

# Migrating App Engine pipelines to ReleaseOps {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

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.
When you migrate to ReleaseOps, you enable ReleaseOps to handle the deployment process in the background without disrupting your existing App Engine pipeline. Developers submit applications in their development environments as before. But with migration enabled, a corresponding ReleaseOps deployment request is created at the time of application submission, which enables ReleaseOps to orchestrate the deployment process. To learn more about the deployment process, see [Deployment process in AEMC](https://servicenow-prod.fluidtopics.net/W5TltaEjUDgDTMIWOuYDfg "Learn about the deployment process in AEMC.").

## Benefits of migration {#migrating-ae-pipelines-to-releaseops-aemc__section_j2l_213_zgc}

Migrating an App Engine pipeline to ReleaseOps enables you to take advantage of ReleaseOps features without disrupting your existing App Engine pipeline or deployment process. This approach is helpful if you want to:

* Evaluate ReleaseOps before fully adopting it.
* Continue using the Application Repository for deployments.
* Deploy with ReleaseOps in environments where full support isn't available yet, such as App Engine Studio and Creator Studio.
{#migrating-ae-pipelines-to-releaseops-aemc__ul_dfd_sw2_fhc}

## Migration process overview {#migrating-ae-pipelines-to-releaseops-aemc__section_vjs_yw2_fhc}

To migrate to ReleaseOps, you must have ReleaseOps installed and configured on each instance in your App Engine pipeline. Once you have configured ReleaseOps and the system property to enable migration, developers initiate deployment as usual. However, with migration enabled, deployment is handled by ReleaseOps in the background. The following list outlines the entire process for migrating to ReleaseOps:

1. [Install ReleaseOps](https://servicenow-prod.fluidtopics.net/o0aeTK_yvBlWMqv5~2~WPA "Install ReleaseOps from the ServiceNow Store for the first time.") on each environment (instance) in your App Engine pipeline.
2. Complete ReleaseOps setup by [configuring a new ReleaseOps ecosystem](https://servicenow-prod.fluidtopics.net/fV7qoEivn2VmyxEBaHoaAw "Complete ReleaseOps manual setup to configure a new ReleaseOps ecosystem using the sample pipelines and playbooks.") and [configuring multi-instance management](https://servicenow-prod.fluidtopics.net/ZnoZS2z~p9EQTPN8wAYibw "Manage the multi-instance configurations to enable access across instances in your ReleaseOps ecosystem.").
3. [Configure the system property to enable migration to ReleaseOps](https://servicenow-prod.fluidtopics.net/kiyyDnPhKmh_PFynQQQmlA "Update the sn_deploy_pipeline.migrate_releaseops system property to enable deployments using ReleaseOps.").
4. [Map deployment request states](https://servicenow-prod.fluidtopics.net/sBTAJdfH18cP7oRQ_qmL8Q "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.") if you're using custom deployment request states in your ReleaseOps pipeline. Base system ReleaseOps deployment request states will automatically map onto the corresponding App Engine deployment request states.
5. If you want to add additional conditions to enable ReleaseOps migration, you can set up [custom conditions in Workflow Studio](https://servicenow-prod.fluidtopics.net/9407WKgyBlILnmGjcJnEqA "If you want to add additional conditions to enable ReleaseOps deployments, modify the Deployment Migration to ReleaseOps decision table."). For example, you might want only deployments for certain applications to migrate to ReleaseOps. So you can set up a condition that checks if the deployment request is from that specific application.
{#migrating-ae-pipelines-to-releaseops-aemc__ol_l5r_l13_zgc}

Once you have migrated to ReleaseOps, ReleaseOps handles the deployment process in the background. To learn more about the deployment process after migrating to ReleaseOps, see [Deployment process in AEMC](https://servicenow-prod.fluidtopics.net/W5TltaEjUDgDTMIWOuYDfg "Learn about the deployment process in AEMC.").