---
schema_version: "1"
id: e9ef43102ba7b98add7f35f5585b96d2484358bd998ca7d422846f36d7854aa8
title: Deploy Partial Experience Cloud Site Content with Change Sets
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/experience/264-0-0/networks_migrate_changesets_partial.md
canonical_url: https://help.salesforce.com/s/articleView?id=experience.networks_migrate_changesets_partial.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 9d3bd420f09c09f7ab4df518e4db69cd5d970f2b261b8d11a72bde4a6a49f08e
description: Use change sets to move individual Experience Cloud components and content between related orgs that have a deployment connection, such as your sandbox and production orgs. Create and test changes in your test environment, and then migrate only those changes to production when they’re ready.
products:
  - Experiences
release: "264"
---
# Deploy Partial Experience Cloud Site Content with Change Sets

Use change sets to move individual Experience Cloud components and content between related orgs that have a deployment connection, such as your sandbox and production orgs. Create and test changes in your test environment, and then migrate only those changes to production when they’re ready.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d32648e67">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d32648e67 ">To customize or publish an Experience Cloud site:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d32648e67 ">Create and Set Up Experiences</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d32648e67 ">To edit deployment connections and use inbound change sets:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d32648e67 ">
              <p>Deploy Change Sets AND Modify All Data</p>
              <p style="margin-bottom:0;">If a user requires access only to metadata
                for deployments, you can enable the Modify Metadata Through Metadata API Functions
                permission. This permission gives such users the access they need for deployments without
                providing access to org data. For details, see “Modify Metadata Through Metadata API
                Functions Permission” in <em>Salesforce Help</em>.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d32648e67 ">To use outbound change sets:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d32648e67 ">Create and Upload Change Sets, Create AppExchange Packages, AND Upload AppExchange
              Packages</td>

          </tr>
        </tbody>
      </table>

Partial deployment with change sets is available for enhanced LWR sites created in Winter ’23 and later.

You can use change sets to move partial content for Experience Builder sites using the Digital Experiences component type.

1. Create and test your site in your preferred test org, such as a sandbox.
2. From Setup in your test org, in the Quick Find box, enter Outbound Change Sets, and then select **Outbound Change Sets**.
3. Create a change set, and click **Add** in the Change Set Components section.
4. Select the **Digital Experience** component type.
5. Select the content that you want to deploy from the list of components, and then click **Add To Change Set**.
    
    ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/images/icon_tip.png)
    
    Tip
    
    - To identify which enhanced LWR site each listed component belongs to, use the Type column. The Type column uses the naming convention site/MySiteName.
    - To identify what content each listed component represents, use the Name column. The Name column uses the naming convention sfdc\_cms\_\_<contentType>/<contentName>. For example, the name sfdc\_cms\_\_brandingSet/Build\_Your\_Own\_LWR represents a branding set named Build Your Own LWR.
6. Click **Upload**, and select your target org, such as production.
    
    Make sure that the target org allows inbound connections. The inbound and outbound orgs must have a deployment connection.
7. From Setup, select **Inbound Change Sets**, and find the change set that you uploaded from your source org.
8. Validate and deploy the change set to make it available in the target org.
    
    ![Warning](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/images/icon_warning.png)
    
    Warning When you deploy an inbound change set, it overrides the corresponding site content in the target org.
9. Manually reconfigure any [unsupported items](https://help.salesforce.com/s/articleView?id=experience.networks_migrate_considerations.htm&release=264.0.0&type=5) in the target org site.
10. To make sure that everything works as expected, test your site. Then publish your changes to go live.