--- schema_version: "1" id: 37e2b1a7aa974e938293d695c1501d4944e1597fce3e69893c1bfafd7b363f34 title: Omnistudio Migration Prerequisites collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_migrate_oma_prereq.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_oma_prereq.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 33188808c320a795158c40bd3c2300e5ca27ee5644701ec666f50efed45a9da1 description: Before you start any Omnistudio migration, review these setup requirements and preparatory steps. These checks ensure your org is ready for a successful migration and help you identify any manual updates needed before running the Omnistudio Migration Assistant. products: - Omnistudio release: "264" --- # Omnistudio Migration Prerequisites Before you start any Omnistudio migration, review these setup requirements and preparatory steps. These checks ensure your org is ready for a successful migration and help you identify any manual updates needed before running the Omnistudio Migration Assistant. ## 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?](https://help.salesforce.com/s/articleView?id=xcloud.os_does_your_org_use_custom_or_standard_objects.htm&type=5&language=en_US). - Feature support: Confirm that all components you currently use in Omnistudio Managed Packages, including custom components are supported in Omnistudio Standard. See [Supported Features](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_and_omnistudio_for_vlocity_products_and_features_support.htm&type=5&language=en_US). - 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](https://help.salesforce.com/s/articleView?id=xcloud.technical_requirements.htm&type=5&language=en_US). - 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](https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_omnistudio_custom_objects_to_standard_objects.htm&release=264.0.0&type=5 "The Omnistudio migration process migrates components such as Flexcards, Omniscripts, Data Mappers, Integration Procedures, Omni Global Auto Numbers, Apex classes, FlexiPages, Experience Cloud site pages, Lightning web components (LWCs), and custom labels from the Vlocity Industries managed package runtime (custom data model) to the Omnistudio standard runtime (standard data model). Moving to the Omnistudio standard runtime involves migrating components from the custom data model used in Vlocity Industries managed packages to the standard data model. The Vlocity Industries managed packages include Insurance (INS), Communications, Media, and Energy (CME), and Public Sector (PS). The migration is performed using the Omnistudio Migration Assistant, which automates and guides you through the process for a smooth transition."), [Migrate Omnistudio Components from Vlocity Industries Managed Package and Standard Data Model to Omnistudio Standard Runtime](https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_omnistudio_standard_data_model_to_standard_runtime.htm&release=264.0.0&type=5 "The Omnistudio migration process helps migrate components such as Flexcards, Omniscripts, Data Mappers, Integration Procedures, Omni Global Auto Numbers, Apex classes, FlexiPages, Experience Cloud pages, Lightning web components (LWCs), and custom labels from the Vlocity Industries Managed Packages and standard data model to the Omnistudio standard runtime. The migration is performed using the Omnistudio Migration Assistant, which automates and streamlines the process to ensure a seamless transition to the standard runtime environment."), and [Migrate Omnistudio Components from Omnistudio Foundation Package and Standard Data Model to the Omnistudio Standard Runtime](https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_omnistudio_foundation_std_dm_to_std_runtime.htm&release=264.0.0&type=5 "The Omnistudio migration process helps migrate components such as Flexcards, Omniscripts, Data Mappers, Integration Procedures, Apex classes, FlexiPages, Experience Cloud pages, Lightning web components (LWCs), and custom labels from the standard data model and Omnistudio foundation package to the Omnistudio standard runtime with Omnistudio Metadata setting enabled. The migration is performed using the Omnistudio Migration Assistant, which automates and streamlines the process to ensure a seamless transition to the standard runtime environment."). ## 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](https://developer.salesforce.com/docs/atlas.en-us.252.0.sfdx_setup.meta/sfdx_setup/sfdx_setup_install_cli.htm). - Node.js version: Make sure that your [node.js](https://nodejs.org/en/download) 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](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_permission_sets_licenses.htm&language=en_US&type=5). - `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](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_data_mapper_and_integration_procedure_functions.htm&type=5&language=en_US). - **[Pre-Migration Steps to Complete Your Migration](https://help.salesforce.com/s/articleView?id=xcloud.os_pre_migration_steps_oma.htm&release=264.0.0&type=5)** Before you start the migration by using the Omnistudio Migration Assistant, complete these manual steps.