Loading
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Deploying Omnistudio Components Between Orgs or Migrating from Omnistudio for Managed Packages (Managed Package)

          Deploying Omnistudio Components Between Orgs or Migrating from Omnistudio for Managed Packages (Managed Package)

          For the managed package runtime, deployment means moving Omnistudio components from one org to another, whether you use Omnistudio for Managed Packages or Omnistudio. Migration means migrating your data from the Omnistudio for Managed Packages custom data model to the Salesforce standard data model and switching to the Salesforce standard runtime. Omnistudio migration includes migration of Omnistudio metadata only.

          Managed Package app icon This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

          Note
          Note When you upgrade Omnistudio, you install the latest version of the managed package. Upgrading is unrelated to migration from Omnistudio for Managed Packages to Omnistudio.
          To Do This Go Here

          Move Omnistudio components from a sandbox or dev org to another such as a production org

          Sometimes called devops or continuous integration, continuous delivery/deployment

          Deploying Omnistudio Components Between Orgs
          Use Omnistudio with the standard data model and the Salesforce standard runtime, by migrating from Omnistudio for Managed Packages to Omnistudio.
          Note
          Note Migration includes Omnistudio metadata only. If you migrated and you have data from other clouds or calculation matrices, you must separately migrate those components along with Omnistudio metadata. Angular Omniscripts must be rebuilt as Lightning web components.
          • Deployment of Omnistudio for Managed Packages Components Between Orgs (Managed Package)
            For the managed package runtime, for your projects that use Omnistudio for Managed Packages, move the components and metadata from one org to another by using the Build Tool (formerly known as Vlocity Build Tool or VBT) or IDX Workbench. For simple use cases, you can move objects between orgs by exporting and importing data packs.
          • Data Deployment with the Omnistudio Build Tool (Managed Package)
            For the managed package runtime, the Omnistudio Build Tool (formerly Vlocity Build Tool or VBT) is a Node.js command-line automation tool that packages and deploys Salesforce data packs in a source-control-friendly format. The tool creates a YAML (YAML Ain’t Markup Language) manifest that describes a deployment project. The Build Tool enables continuous integration of Omnistudio metadata to source control.
          • IDX Workbench Desktop Application (Managed Package)
            For the managed package runtime, IDX Workbench is a desktop application that you use to deploy Omnistudio data packs and Salesforce metadata. Its user interface is built on top of the Omnistudio Build Tool. The application is available for Mac and Linux.
          • Data Deployment with Data Packs (Managed Package)
            For the managed package runtime, a data pack is a collection of components and related functionality that are packaged for deployment between orgs. For example, you can use data packs to deploy functionality from a sandbox environment to a production environment.
           
          Loading
          Salesforce Help | Article