Omnistudio Migration Prerequisites

General Prerequisites

Ensure your environment and org configuration meet the necessary technical baseline before beginning any migration.

• Org object check: Verify whether your org uses custom or standard objects. See Does Your Org Use Custom or Standard Objects?.

• Feature support: Confirm that all components you currently use in Omnistudio Managed Packages, including custom components are supported in Omnistudio Standard. See Supported Features.

• System requirements: Ensure your setup meets these minimum technical requirements:

  • An Octane 2.0 score of 20,000 or greater.

  • Network latency of 200 ms or less.

  • Download speed of 1 Mbps or greater.

  • At least 5 GB of RAM, with 2 GB available for Salesforce browser tabs.

  See Technical Requirements.

• Migration workflow review: Review the high-level migration phases in the Omnistudio Migration Workflow. See Migrate Omnistudio Components from Vlocity Industries Managed Packages and Custom Data Model to Omnistudio Standard Runtime, Migrate Omnistudio Components from Vlocity Industries Managed Package and Standard Data Model to Omnistudio Standard Runtime, and Migrate Omnistudio Components from Omnistudio Foundation Package and Standard Data Model to the Omnistudio Standard Runtime.

Tool and Configuration Setup

• Salesforce CLI: Install Salesforce CLI on your computer. If already installed, make sure you have the latest version. See Install Salesforce CLI.
• Node.js version: Make sure that your node.js version is 22.12.0 or later.
• Omnistudio licenses and permissions; Make sure you provision the Omnistudio license and assign the required permission set licenses. In both sandboxes, provision the Omnistudio license to make the Omnistudio standard objects available in the org. Then, assign the Omnistudio permission set licenses to grant users access to the objects. See Omnistudio Permission Sets.
• EnableParentCompile flag: To ensure metadata consistency, to avoid migration failures for nested components, and to avoid manual rework, add the EnableParentCompile flag in the Omni Interaction Configuration page, and set it to true:
  1. In Setup, find and select Omni Interaction Configuration.

  2. Click New Omni Interaction Configuration.

  3. Enter Label and Name = EnableParentCompile, and Value = true.

  4. Save your changes.

• Custom Label migration:
  • Enable Translation Language Settings in your org:
    1. Go to Setup, search and find Translation Language Settings, and click Enable.
    2. Click Add and select a language (for example, English) for the user.
    3. Search and find the user, and add them to the Selected List.
    4. Save your changes.
  • Increase the limit of your Custom Labels to 10000. The default limit is 5000.
• Flexcard custom LWC update: If your Flexcard contains a Custom LWC element with its attribute key field set to action in the key-value pair, rename the key and update all dependent references accordingly.

Implementation Prerequisites

The Omnistudio Migration Assistant supports these scenarios and some of these scenarios require manual updates before running the Omnistudio Migration Assistant in Migrate mode.

• Custom apps built with FlexiPages

• Custom Omniscripts

• Simple Flexcards (display-only, no interactions)

• Custom LWCs (requires manual updates when Omniscripts are embedded)

• Integration Procedures called from Omniscripts or Flexcards (requires namespace updates)

• Use of Data Mappers. See Supported Functions for Data Mapper and Integration Procedure.