---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Moving Cloud Provisioning and Governance content across environments

# Moving Cloud Provisioning and Governance content across environments {#ariaid-title1}

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

You can move the content in the Cloud Provisioning and Governance application
from one environment to the other. For example, develop an application in an environment and
then move the application and all its dependencies to another environment for testing or
production.

## Content entities that can be moved {#move-content-intro__section_nbq_lpp_sgb}

The Cloud Provisioning and Governance application consists of code, resources,
content, and configurations.  
You can move the following content entities across environments:

* Blueprints
* Resource blocks
* Cloud APIs
{#move-content-intro__ul_j4y_wzb_sdb}

Use the update sets to move the content entities. Update sets, which are XML files,
group all the content into named sets and then moves these sets, as a unit, to other
systems for testing or deployment. For information on how system update sets work,
see
[System update sets](https://www.servicenow.com/docs/access?context=system-update-sets&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US)
.

## Content entity dependencies {#move-content-intro__section_rl3_mpp_sgb}

Each of the content entities has some direct dependencies that are automatically
moved with the content to the new environment.  
The direct dependencies for each of these content entities are: {#move-content-intro__table_yk5_ypp_sgb__entry__2}

| Content entity | Dependencies |
|-|-|
| Blueprint | * Resource blocks * Cloud APIs * MID scripts * Resource pools * Policies * Script includes * Cloud scripts {#move-content-intro__ul_nnh_1qp_sgb} |
| Resource blocks | * Resource pools * Resource operation policies * Script includes * Cloud APIs * Dependant resource blocks * MID scripts {#move-content-intro__ul_wwx_wmk_tgb} |
| Cloud API | MID scripts |
[ ]

{#move-content-intro__table_yk5_ypp_sgb}
**Related tasks**   

* [Move a blueprint from one environment to another](https://servicenow-prod.fluidtopics.net/yDu0uN3u2qZimfqzofbwzw "Use update sets to move a blueprint and its dependencies from one environment to another. Update sets let you group a blueprint and its dependencies into a named set and then move them as a unit to other systems for testing or deployment. For example, you can move a blueprint from a development environment to a production environment.")
* [Move a resource block from one environment to the other](https://servicenow-prod.fluidtopics.net/lEAYwOBUkO6mdCGshiZsTA "Use update sets to effortlessly transfer resource blocks and their dependencies between environments. Group them into a named set, facilitating seamless movement for testing or deployment. Simplify processes such as transferring a resource block from development to production, ensuring efficient and organized transitions across different systems.")
* [Move a cloud API from one environment to the other](https://servicenow-prod.fluidtopics.net/vj7DpjNEexRRMDcFBuECUA "Use update sets to move a cloud API from one environment to another. Update sets let you group a cloud API and its dependencies into a named set and then move them as a unit to other systems for testing or deployment. For example, you can move a cloud API from a development environment to a production environment.")