Experience Cloud Developer Guide

Get Up to Speed with Experience Builder Sites
Develop Experience Builder Sites: The Basics
Brand Your Aura Site
Develop Secure Sites: Authenticated and Guest Users
Develop Secure Sites: CSP, LWS, and Lightning Locker
Analyze and Improve Experience Builder Site Performance
Add Pardot Tracking to Your Experience Builder Site
Use a CMS with Your Experience Builder Site
Report on Deflections: The Deflection Signals Framework
Deploy an Experience Cloud Site from Sandbox to Production
Deploy Your Experience Cloud Site with Change Sets
Deploy A Full Experience Cloud Site with Change Sets
Deploy Partial Experience Cloud Site Content with Change Sets
Considerations for Deploying Experience Cloud Sites with Change Sets
Deploy Your Experience Cloud Site with the Metadata API
ExperienceBundle for Experience Builder Sites
Avoid Deployment Issues When Moving to Enhanced LWR Sites
Considerations for Deploying Authenticated LWR Sites
PDF

Newer Version Available

This content describes an older version of this product. View Latest

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.
Available in: Salesforce Classic (not available in all orgs) 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.

Note
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.

  1. Create and test your site in your preferred test org, such as sandbox.
  2. From Setup in your test org, enter Outbound Change Sets in the Quick Find box, and then select Outbound Change Sets.
  3. Create a change set, and click Add in the Change Set Components section.
  4. Select the Network component type, choose your site, and then click Add to Change Set.
  5. To add dependent items, click View/Add Dependencies. We recommend selecting all the dependencies listed.
    • 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.

    Tip

  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.

    When you deploy an inbound change set, it overwrites the site in the target org.

    Warning

  9. Manually reconfigure any unsupported items in the target org site.
  10. Add data for your site, and test it to make sure that everything works as expected. Then publish your changes to go live.