Deployment of Omnistudio Components Between Orgs

For your projects that use Omnistudio tools, and when you’re on Omnistudio standard runtime with standard objects, use Salesforce CLI to move the components and metadata from one org to another org.

Note If your org is on the standard runtime, Salesforce recommends that you turn on Clean Metadata Deployment. Clean Metadata Deployment lets you deploy Omnistudio components with the same tools and workflows you use for standard Salesforce metadata, including Salesforce CLI, change sets, and packaging. See Clean Metadata Deployment for Omnistudio.

To learn more about how to install and configure Salesforce CLI, see Salesforce CLI Developer Guide.

Use DevOps methods to create solutions with Omnistudio in a dev org. Then deploy those Omnistudio components to a test or integration org for testing purposes. Finally, deploy those components to your production org.

Note

Deployment of components between orgs and migration from Omnistudio for Managed Packages to Omnistudio are different processes. See Deploying Omnistudio Components Between Orgs or Migrating to Omnistudio Standard.

If you're using Omnistudio for Managed Packages, you must use different deployment tools. See Deploy Omnistudio for Managed Packages Components Between Orgs.

• Tool Considerations for Deploying Omnistudio Components
  Select the tool for deploying components based on what you’re deploying, the data model used in the source and target orgs, and the Omnistudio runtime used in the source and target orgs. The source and target orgs can be sandboxes, development orgs, or production orgs.
• Clean Metadata Deployment for Omnistudio
  Clean Metadata Deployment modernizes how you deploy Omnistudio components. When you turn it on, Omnistudio components behave like standard Salesforce metadata, so you deploy them with Salesforce CLI, DevOps Center, change sets, and packaging, alongside Lightning web components, flows, and Apex classes in a single pipeline.