You are here:
Migrate Omnistudio Components from Vlocity Industries Managed Package and Standard Data Model to Omnistudio Standard Runtime
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.
Omnistudio Migration Assistant: Tasks Automated vs Manual
| Tasks | Migration Automated Using Omnistudio Migration Assistant? | Automated or Manual? |
|---|---|---|
| Migrate calculation procedures and calculation matrices to the Business Rules Engine | No | Manual |
| Switch to the Standard Runtime | Yes | Automated |
| Switch to the Standard Designer | No | Manual |
| Deploy Custom Lightning Web Components | No | Manual |
| Update References to Omnistudio Components After Migration | Yes | Automated |
| Update Remote actions | Yes | Automated |
| Migrate Omni Global Auto Numbers | 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, you cannot migrate to the Omnistudio standard runtime.
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.
- Development sandbox:
- Prepare your org for the migration process.
- 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.
Note If your org is already on the standard data model with the Omnistudio Metadata API setting enabled, the Omnistudio Migration Assistant does not assess and generate assessment reports for the Omnistudio components such as Data Mappers, Omniscripts, Integration Procedures, Flexcards, and Omni Global Auto Numbers. In this scenario, the Omnistudio Migration Assistant assesses only custom labels and the related objects such Apex, class, LWCs, and FlexiPages to resolve namespace and reference dependencies. - Review the assessment reports generated for the components.
- 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:
- Prepare and deploy your validated components from the development sandbox.
- 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:
- Prepare and deploy the final validated components.
- After a successful validation, follow your organization’s release processes to roll out changes safely.
Who’s the Target Audience of this Document?
This document applies to customers who are migrating Omnistudio components such as Flexcards, Omniscripts, Data Mappers, and Integration Procedures from standard data model and Vlocity Industries managed package runtime to the Omnistudio standard runtime. This document also applies to customers who are migrating related objects such as Omni Global Auto Numbers, Apex classes, FlexiPages, Experience Cloud site pages, Lightning web components (LWCs), and custom labels.
See Does Your Org Use Custom or Standard Objects?, Which Version of Omnistudio Do I have?, and Difference Between Omnistudio and Omnistudio for Managed Packages.
- Migration Phase 1: Development Sandbox (Vlocity Industries Managed Package and Standard Data Model)
In Phase 1, prepare your development and testing sandboxes, upgrade to the required managed package versions, and provision licenses. Migrate calculation logic to 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 Omnistudio standard runtime. Finally, validate the migration by reviewing reports, updating integrations, and testing business workflows in your sandboxes. - Migration Phase 2: Testing Sandbox (Vlocity Industries Managed Package and Standard Data Model)
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. - Migration Phase 3: Production Environment (Vlocity Industries Managed Package and Standard Data Model)
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.
