You are here:
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
| Available in: Salesforce Classic and Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions |
| User Permissions Needed | |
|---|---|
| To customize or publish an Experience Cloud site: | Create and Set Up Experiences |
| To edit deployment connections and use inbound change sets: | Deploy Change Sets AND Modify All Data 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 Salesforce Help. |
| To use outbound change sets: | Create and Upload Change Sets, Create AppExchange Packages, AND Upload AppExchange Packages |
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.
- Create and test your site in your preferred test org, such as a sandbox.
- From Setup in your test org, in the Quick Find box, enter Outbound Change Sets, and then select Outbound Change Sets.
- Create a change set, and click Add in the Change Set Components section.
- Select the Digital Experience component type.
-
Select the content that you want to deploy from the list of components, and then click
Add To Change Set.
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.
-
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.
- From Setup, select Inbound Change Sets, and find the change set that you uploaded from your source org.
-
Validate and deploy the change set to make it available in the target org.
Warning When you deploy an inbound change set, it overrides the corresponding site content in the target org. - Manually reconfigure any unsupported items in the target org site.
- To make sure that everything works as expected, test your site. Then publish your changes to go live.
