Moving Cloud Provisioning and Governance content across environments

---
title: Moving Cloud Provisioning and Governance content across environments
description: 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.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/cloud-configuration-governance/move-content-intro.html
release: australia
product: Cloud Configuration Governance
classification: cloud-configuration-governance
topic_type: concept
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Cloud Provisioning and Governance administration guide, Cloud Provisioning and Governance, ITOM Cloud Accelerate, IT Operations Management]
---

# Moving Cloud Provisioning and Governance content across environments

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

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

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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/system-update-sets.md) .

## Content entity dependencies

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:

<table id="table_yk5_ypp_sgb"><thead><tr><th>

Content entity

</th><th>

Dependencies

</th></tr></thead><tbody><tr><td>

Blueprint

</td><td>

-   Resource blocks
-   Cloud APIs
-   MID scripts
-   Resource pools
-   Policies
-   Script includes
-   Cloud scripts

</td></tr><tr><td>

Resource blocks

</td><td>

-   Resource pools
-   Resource operation policies
-   Script includes
-   Cloud APIs
-   Dependant resource blocks
-   MID scripts

</td></tr><tr><td>

Cloud API

</td><td>

MID scripts

</td></tr></tbody>
</table>**Related topics**  


[Move a blueprint from one environment to another](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/cloud-configuration-governance/export-updateset-blueprint.md)

[Move a resource block from one environment to the other](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/cloud-configuration-governance/export-updateset-rblock.md)

[Move a cloud API from one environment to the other](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/cloud-configuration-governance/export-updateset-capi.md)