You are here:
Deploy A Full Experience Cloud Site with Change Sets
Use change sets to move your Experience Cloud site between related orgs that have a deployment connection, such as your sandbox and production orgs. Create, customize, and test your site in your test environment and then migrate the site to production when testing is complete.
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  Note If a
user requires access only to metadata for deployments, you can turn on the Modify
Metadata Through Metadata API Functions permission. This permission gives such
users the access that 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 |
You can use change sets to move full Experience Builder and Salesforce Tabs + Visualforce sites using the Network component type.
- Create and test your site in your preferred test org, such as sandbox.
- From Setup in your test org, enter Outbound Change Sets in the Quick Find box, and then select Outbound Change Sets.
- Create a change set, and click Add in the Change Set Components section.
- Select the Network component type, choose your site, and then click Add to Change Set.
-
To add dependent items, click View/Add Dependencies. We
recommend selecting all the dependencies listed.
Tip- For navigation menus that link to standard objects, custom list views aren’t included as dependencies. Manually add the custom list view to your change list.
- Manually add new or modified profiles or permission sets referenced in Administration | Members.
- The list of dependencies has two Site.com items—MySiteName and MySiteName1. MySiteName holds the various Visualforce pages that you can set in Administration in Experience Workspaces. MySiteName1 includes the pages from Experience Builder.
-
Click Upload and select your target org, such as
production.
Note Make sure that your target org allows inbound connections. The inbound and outbound orgs must have a deployment connection. Change sets deploy to an org, not to a site that you pick. The destination site is represented by the Network component that you added to the change set. To deploy the same staged site to multiple production orgs, upload and deploy the change set separately to each connected target org.
- 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 overwrites the site in the target org. - Manually reconfigure any unsupported items in the target org site.
- Add data for your site, and test it to make sure that everything works as expected. Then publish your changes to go live.
Did this article solve your issue?
Let us know so we can improve!
