You are here:
About the Migration Process
The migration process uses the Omnistudio Migration Assistant to move components such as Flexcards, Omniscripts, Data Mappers, Integration Procedures, custom labels, Omni Global Auto Numbers, and related objects such as Apex classes, FlexiPages, Experience Cloud site pages, Lightning web components (LWCs), and custom labels from managed package runtime and Omnistudio Foundation package to the Omnistudio standard runtime. This makes sure that the components from industry packages such as Insurance (INS), Communications, Media, and Energy (CME), and Public Sector (PS) match the standard runtime, easing maintenance and upgrades.
This process supports migration from:
- Vlocity Industries managed package runtime and custom data model to the Omnistudio standard runtime and standard data model.
- Vlocity Industries managed package runtime and standard data model to the Omnistudio standard runtime.
- Omnistudio Foundation package runtime and standard data model to the Omnistudio standard runtime.
This ensures that components align with the standard runtime for easier maintenance and upgrades.
After the migration process is complete, all your applications and workflows that were built on the managed package runtime and Omnistudio Foundation package continue to work on the standard runtime.
Important If your org has Vlocity managed packages (vlocity_ins, vlocity_ps, and
vlocity_cme) or Omnistudio Foundation packages, don’t uninstall them.
This is an overview of the steps for migrating to the Omnistudio standard runtime:
- Check your Cloud compatibility:
- Contact your Salesforce Account Executive to verify your Cloud compatibility:
- Confirm whether your Industry Cloud supports the Omnistudio standard runtime.
- Review and confirm that the features you require are supported in the Omnistudio standard runtime.
- Upgrade to the Vlocity Industries managed package version Winter ‘26 or later.
- Contact your Salesforce Account Executive to verify your Cloud compatibility:
- Plan and complete your migration process in phases to avoid business disruptions. The
Omnistudio Migration Assistant runs in Assess mode to help you assess the migration
readiness of your components, and then in Migrate mode to perform the actual migration.
- Prepare
- Set up environments and licenses.
- Select your workflows for migration, validate it, and record it so that you can compare it post migration to make sure the migration worked as expected.
- AssessImportant 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, and Flexcards. 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.
- Run the Omnistudio Migration Assistant in Assess mode.
- Review the assessment reports and fix any identified issues.
- MigrateImportant Before you run the Omnistudio Migration Assistant in Migrate mode, make sure you run it in Assess mode, review the assessment reports, and resolve any issues.
- Run Omnistudio Migration Assistant in Migrate mode to perform the actual migration of workflows.
- Review the migration reports.
- Validate your flows to make sure that they are working correctly.
- Deploy the migrated workflows to your production environment.
- Switch to the Omnistudio standard runtime and standard designers.
- Prepare
Important The Omnistudio migration process only migrates Omnistudio components. It
does not migrate records from your Vlocity Industries managed package data model (for example:
policies, accounts, or cases) or any user data displayed or managed through those Omnistudio
components.
Omnistudio Migration Assistant Supported Scenarios and Readiness
This table describes the supported starting configurations for Omnistudio and explains how the Migration Assistant prepares your org for the standard runtime by migrating components, enabling required settings, and removing managed package dependencies.
| Before Migration | Migration Actions Performed | Package Dependencies Removed | Experience Sites and FlexiPages Updates | After Migration |
|---|---|---|---|---|
| Custom Data Model + Industries managed package + Omnistudio Metadata API manually enabled | Assesses and migrates these components that are on custom data model and Vlocity Industries managed package runtime (vlocity_cmt, vlocity_ins, and vlocity_ps) to standard data model and Omnistudio standard runtime: Flexcards, Omniscripts, Data Mappers, Integration Procedures, custom labels, Omni Global Auto Numbers, and related objects such as Apex classes, FlexiPages, Experience Cloud site pages, and Lightning web components (LWCs). | Removes managed package dependencies from:
|
Replaces Vlocity wrappers with Omnistudio standard wrappers. | Standard data model + Omnistudio standard runtime |
| Standard Data Model + Industries managed package + Omnistudio Metadata API disabled | Assesses and migrates these components that are on standard data model and Vlocity Industries managed package runtime (vlocity_cmt, vlocity_ins, and vlocity_ps) to Omnistudio standard runtime and enables the Omnistudio Metadata setting: Flexcards, Omniscripts, Data Mappers, Integration Procedures, custom labels, Omni Global Auto Numbers, and related objects such as Apex classes, FlexiPages, Experience Cloud site pages, and Lightning web components (LWCs). | Removes managed package dependencies from:
|
Replaces Vlocity wrappers with Omnistudio wrappers and updates the references automatically for Omnistudio standard wrappers. | Omnistudio standard runtime + the Omnistudio Metadata setting enabled. |
| Standard Data Model + Industries managed package + Omnistudio Metadata API enabled | Assesses and migrates these components that are on standard data model and Vlocity Industries managed package runtime (vlocity_cmt, vlocity_ins, and vlocity_ps) to Omnistudio standard runtime: Flexcards, Omniscripts, Data Mappers, Integration Procedures, custom labels, Omni Global Auto Numbers, and related objects such as Apex classes, FlexiPages, Experience Cloud site pages, and Lightning web components (LWCs). | Removes managed package dependencies from:
|
Replaces Vlocity wrappers with Omnistudio wrappers and updates the references automatically for Omnistudio standard wrappers. | Omnistudio standard runtime |
| Standard Data Model+Foundation Package+Metadata API disabled | Assesses and migrates components on the standard data model and Omnistudio Foundation package to the Omnistudio standard runtime and enables the Omnistudio Metadata setting. The Omnistudio Migration Assistant automates record renaming to meet alphanumeric requirements and updates all internal references. It also modifies Custom Functions by updating namespace syntax and converting unsupported logic such as REPLACE into the required FUNCTION format. This includes Flexcards, Omniscripts, Data Mappers, Integration Procedures, and related objects such as Apex classes and Experience Cloud sites. | Removes managed package dependencies from:
 Note Unlike other scenarios, Global Auto Numbers are not supported because the
corresponding custom entity does not exist in the Omnistudio namespace. |
Updates the references automatically for Omnistudio standard wrappers. | Omnistudio standard runtime + the Omnistudio Metadata setting enabled. |
| Standard Data Model+Foundation Package+Metadata API enabled | Assesses and migrates components on the standard data model and Omnistudio Foundation package to the Omnistudio standard runtime. The Omnistudio Migration Assistant automates record renaming to meet alphanumeric requirements and updates all internal references. It also modifies Custom Functions by updating namespace syntax and converting unsupported logic such as REPLACE into the required FUNCTION format. This includes Flexcards, Omniscripts, Data Mappers, Integration Procedures, and related objects such as Apex classes and Experience Cloud sites. | Removes managed package dependencies from:
Note Unlike other scenarios, Global Auto Numbers are not supported because the
corresponding custom entity does not exist in the Omnistudio namespace. |
Updates the references automatically for Omnistudio standard wrappers. | Omnistudio standard runtime |
Hjalp denne artikkelen med å løse problemet ditt?
La oss få vite det slik at vi kan forbedre!
