We recommend creating, customizing, and testing your Experience Cloud site in a test
environment, such as a sandbox, before deploying it to your production org. When testing is
complete, you can use change sets or Metadata API to migrate your site from one org to another.
Deciding whether to use change sets or MD API depends on several factors. Some things to consider
are the complexity of the changes that you’re migrating, your level of comfort with developer
tools, and the application lifecycle management (ALM) model that you’re using.
Required Editions
| Available in: both Salesforce Classic and
Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and
Developer Editions
|
To learn more about the ALM models and development options available to you, check out Determine Which Application Lifecycle
Management Model Is Right for You on Trailhead.
Lightning Bolt Solutions aren’t suitable for deploying Experience Cloud sites between your
orgs. Use a Lightning Bolt Solution to share or sell a solution on AppExchange or implement a
site with a turnkey solution or new look.
Change Sets
If you’re more comfortable working with point-and-click tools, change sets are your deployment
friend. A change set represents a set of customizations in your org (or metadata components)
that you can deploy to a connected org.
You can manage your application using declarative tools. You don’t have to use a command-line
interface or a version control system to meet your customization needs. You use the Setup menu
to create changes in a development environment. You then migrate the changes between
environments as you work through the ALM steps.
Your release artifact is a set of metadata changes relative to what’s in the production org.
What gets released is only metadata that has been added or changed—if it doesn’t change, it’s
not in the release.
Metadata API
If you’re up to speed on Metadata API and more comfortable in the world of code, use Metadata
API to deploy changes programmatically. You can retrieve, deploy, create, update, and delete
customization information for your org, such as Experience Cloud sites, custom object
definitions, and page layouts.
Using Metadata API is ideal when your changes are complex or when you need a more rigorous
change management process and an audit process (or version control system) to manage multiple
work streams.
As with the change set process, the release artifact that you create is a set of metadata
changes relative to your production org.
- Deploy Your Experience Cloud Site with Change Sets
Use change sets to move all or part of your Experience Cloud site between related orgs that have a deployment connection. You can use the Network component type to move any full Experience Cloud site. Or, you can use the Digital Experience component type to move partial site content for enhanced LWR sites.
- Deploy Your Experience Cloud Site with the Metadata API
Use Metadata API to move your Experience Cloud site from one Salesforce org to another. Set up and test your site in your test environment, and then retrieve the site’s data and deploy it to your production org.
