--- schema_version: "1" id: b884ed71106e792fc8c6181563671bc7313cd77b30fe66e3ad2b843085b2ce57 title: Migrate Omnistudio Components from Vlocity Industries Managed Packages and Custom Data Model to Omnistudio Standard Runtime collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_migrate_omnistudio_custom_objects_to_standard_objects.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_omnistudio_custom_objects_to_standard_objects.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 6507212a690174e6bd0bd479d1541a21270eeb2e1589d2bada23da8e8a02ea84 description: 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. products: - Omnistudio release: "264" --- # Migrate Omnistudio Components from Vlocity Industries Managed Packages and Custom Data Model to Omnistudio Standard Runtime 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. ## Omnistudio Migration Assistant: Automated vs Manual Tasks | Tasks | Migration Automated Using Omnistudio Migration Assistant? | Automated or Manual? | | --- | --- | --- | | [Enable Omnistudio metadata API support](https://help.salesforce.com/s/articleView?id=xcloud.os_enable_omnistudio_metadata_api_support.htm&type=5&language=en_US) | No | Manual | | [Convert or Rebuild Angular Components](https://help.salesforce.com/s/articleView?id=xcloud.os_convert_an_angular_omniscript_to_an_lwc_omniscript.htm&type=5&language=en_US) | No | Manual | | [Migrate calculation procedures and calculation matrices to the Business Rules Engine](https://help.salesforce.com/s/articleView?id=ind.migrating_calc_matrix_calc_procd.htm&type=5&language=en_US) | No | Manual | | Convert to Standard Data Model | Yes | Automated | | Switch to the Standard Runtime | Yes | Automated | | [Deploy Custom Lightning Web Components](https://help.salesforce.com/s/articleView?id=xcloud.os_enable_standard_omnistudio_runtime.htm&type=5&language=en_US) | No | Manual | | [Switch to the Standard Designer](https://help.salesforce.com/s/articleView?id=xcloud.os_enable_standard_omnistudio_designer.htm&type=5&language=en_US) | No | Manual | | Updates to Omnistudio Custom Functions | Yes | Automated | | Update References to Omnistudio Components After Migration | Yes | Automated | | Update Remote actions | Yes | Automated | | Migrate Omni Global Auto Numbers | Yes | Automated | | Migrate Omniscript saved sessions (Save and Resume) | Yes | Automated | | Migrate Custom Labels | Yes | Automated | | Migrate Custom LWCs | Yes | Automated | | Update Lightning Pages | Yes | Automated | | Update Community Pages | Yes | Automated | ## Limitations - Data Mapper versioning: If your org has multiple versions of a Data Mapper, migration to the standard data model and Omnistudio standard runtime is not supported. - Industries Configure, Price, Quote (CPQ): The Omnistudio Migration Assistant does not support the migration of Industries CPQ out-of-the-box application. - Hybrid CPQ: The Omnistudio Migration Assistant does not support the migration of Hybrid CPQ built on Angular framework. - Omni Interaction Config settings: If these settings are present in your org, Omnistudio Migration Assistant does not support migration: `EnableLegacyOmniScriptDesignerForLWC=true` and `ShowLegacyOmniStudioUi=true`. - Communications, Media, and Energy (CME): The Omnistudio Migration Assistant is currently applicable for CME customers who have custom applications that do not use or extend the out-of-the-box (OOTB) UI. ## Omnistudio Migration Workflow For a smooth and controlled migration, follow the Omnistudio migration workflow across development, testing, and production sandboxes. See [Sandboxes for Omnistudio Migration](https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_prepare_sandbox_orgs.htm&language=en_US&type=5). ![oma\_migration\_workflow](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/omnistudio_for_managed_packages/images/os_oma_migration_workflow.png) - Development sandbox: 1. Prepare your org for the migration process. 2. Run the Omnistudio Migration Assistant in the Assess mode to assess your Omnistudio components such as Omniscripts, Flexcards, Data Mappers, Integration Procedures, Apex Classes, Omni Global Auto Numbers, FlexiPages, Experience Cloud Site Pages, Lightning Web Components, and Custom Labels. 3. Review the assessment reports generated for the components. 4. Run the Omnistudio Migration Assistant in the Migrate mode to migrate the components and validate the results before moving them to your testing sandbox. This step helps detect early issues in a controlled environment. - Testing sandbox: 1. Prepare and deploy your validated components from the development sandbox. 2. Run thorough validation tests to confirm the components are ready for migration. This step helps refine changes before migrating the components to the production environment. - Production environment: 1. Prepare and deploy the final validated components. 2. After a successful validation, follow your organization’s release processes to roll out changes safely. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png) Note Omnistudio Build Tool and OmniOut are tools that are not part of the Omnistudio managed package and do not require migration. 1. **[Migration Phase 1: Development Sandbox (Vlocity Industries Managed Packages and Custom Data Model)](https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_omnistudio_phase1.htm&release=264.0.0&type=5)** In phase 1, prepare your development and testing sandboxes by upgrading to the required managed package versions, provisioning necessary licenses, and enabling the Omnistudio Metadata API setting. Convert or rebuild any unsupported Angular components and migrate calculation logic to the Business Rules Engine. Next, run the Omnistudio Migration Assistant in Assess mode to identify issues and confirm readiness. After resolving any manual interventions, run the tool in Migrate mode to move components and related objects to the standard runtime. Finally, validate the migration by reviewing reports, updating integrations, and testing business workflows in your sandboxes. 2. **[Migration Phase 2: Testing Sandbox (Vlocity Industries Managed Packages and Custom Data Model)](https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_omnistudio_phase2.htm&release=264.0.0&type=5)** Deploy the changes you made in the development sandbox to the testing sandbox. Test them in your business workflows. After you complete phase 2, your changes are ready for deployment to production. 3. **[Migration Phase 3: Production Environment (Vlocity Industries Managed Packages and Custom Data Model)](https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_omnistudio_phase3.htm&release=264.0.0&type=5)** Use your existing production deployment process to prepare your production environment and deploy the changes you tested in the testing sandbox. Test your business workflows. After you complete phase 3, follow your release process to push the migration changes to your production org.