---
schema_version: "1"
id: f6bcb0a955bd49f45ca78aa692e158117c3f594c646e8cf025708850601a0e59
title: About the Migration Process
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_migrate_about_migration.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_about_migration.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2f44f5601326b8f59475bb691fef225d7459003644657970253d6bcbd3400e57
description: 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.
products:
  - Omnistudio
release: "264"
---
# 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](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_important.png)

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:

1. Check your Cloud compatibility:
    1. 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.
    2. Upgrade to the Vlocity Industries managed package version Winter ‘26 or later.
2. 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.
    1. Prepare
        1. Set up environments and licenses.
        2. 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.
    2. Assess
        
        ![Important](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_important.png)
        
        Important 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.
        
        1. Run the Omnistudio Migration Assistant in Assess mode.
        2. Review the assessment reports and fix any identified issues.
    3. Migrate
        
        ![Important](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_important.png)
        
        Important 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.
        
        1. Run Omnistudio Migration Assistant in Migrate mode to perform the actual migration of workflows.
        2. Review the migration reports.
    4. Validate your flows to make sure that they are working correctly.
    5. Deploy the migrated workflows to your production environment.
    6. Switch to the Omnistudio standard runtime and standard designers.

![Important](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_important.png)

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.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:20%">
          <col style="width:20%">
          <col style="width:20%">
          <col style="width:20%">
          <col style="width:20%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d110330e156"><strong>Before Migration</strong></th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d110330e160"><strong>Migration Actions Performed</strong></th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d110330e164"><strong>Package Dependencies Removed</strong></th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d110330e168"><strong>Experience Sites and FlexiPages Updates</strong></th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d110330e172"><strong>After Migration</strong></th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Before Migration" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e156 ">Custom Data Model + Industries managed package + Omnistudio Metadata API
              manually enabled</td>

            <td data-label="Migration Actions Performed" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e160 ">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).</td>

            <td data-label="Package Dependencies Removed" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e164 ">
              <p>Removes managed package dependencies from:</p>
              <ul>
                <li>Custom Labels</li>

                <li>Global Autonumbers</li>

                <li>LWCs</li>

                <li>Apex classes</li>

              </ul>
            </td>

            <td data-label="Experience Sites and FlexiPages Updates" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e168 ">Replaces Vlocity wrappers with Omnistudio standard wrappers.</td>

            <td data-label="After Migration" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e172 ">Standard data model + Omnistudio standard runtime</td>

          </tr>
          <tr class="">
            <td data-label="Before Migration" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e156 ">Standard Data Model + Industries managed package + Omnistudio Metadata API
              disabled</td>

            <td data-label="Migration Actions Performed" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e160 ">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 <strong>Omnistudio
                Metadata</strong> 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).</td>

            <td data-label="Package Dependencies Removed" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e164 ">
              <p>Removes managed package dependencies from:</p>
              <ul>
                <li>Custom Labels</li>

                <li>Global Autonumbers</li>

                <li>LWCs</li>

                <li>Apex classes</li>

              </ul>
            </td>

            <td data-label="Experience Sites and FlexiPages Updates" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e168 ">Replaces Vlocity wrappers with Omnistudio wrappers and updates the references
              automatically for Omnistudio standard wrappers.</td>

            <td data-label="After Migration" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e172 ">Omnistudio standard runtime + the <strong class="uicontrol">Omnistudio Metadata</strong>
              setting enabled.</td>

          </tr>
          <tr class="">
            <td data-label="Before Migration" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e156 ">Standard Data Model + Industries managed package + Omnistudio Metadata API
              enabled</td>

            <td data-label="Migration Actions Performed" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e160 ">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).</td>

            <td data-label="Package Dependencies Removed" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e164 ">
              <p>Removes managed package dependencies from:</p>
              <ul>
                <li>Custom Labels</li>

                <li>Global Autonumbers</li>

                <li>LWCs</li>

                <li>Apex classes</li>

              </ul>
            </td>

            <td data-label="Experience Sites and FlexiPages Updates" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e168 ">Replaces Vlocity wrappers with Omnistudio wrappers and updates the references
              automatically for Omnistudio standard wrappers.</td>

            <td data-label="After Migration" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e172 ">Omnistudio standard runtime</td>

          </tr>
          <tr class="">
            <td data-label="Before Migration" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e156 ">Standard Data Model+Foundation Package+Metadata API disabled</td>

            <td data-label="Migration Actions Performed" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e160 ">Assesses and migrates components on the standard data model and Omnistudio
              Foundation package to the Omnistudio standard runtime and enables the <strong>Omnistudio
                Metadata</strong> 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.</td>

            <td data-label="Package Dependencies Removed" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e164 ">
              <p>Removes managed package dependencies from:</p>
              <ul>
                <li>Custom Labels</li>

                <li>LWCs</li>

                <li>Apex classes</li>

              </ul>
              <div>
                <div class="slds-box slds-box_x-small slds-theme_shade slds-m-top_medium slds-m-bottom_medium">
                  <div class="slds-media slds-media_responsive">
                    <div class="slds-media__figure"><span class="slds-icon_container slds-icon_container_circle slds-icon-note-note"><img style="margin-bottom:0;" src="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" alt="Note"></span></div>
                    <div class="slds-media__body" style="padding-top:.5rem;padding-bottom:.5rem;"><span class="slds-text-title_caps">Note</span> Unlike other scenarios, Global Auto Numbers are not supported because the
                      corresponding custom entity does not exist in the Omnistudio namespace.</div>
                  </div>
                </div>
              </div>
            </td>

            <td data-label="Experience Sites and FlexiPages Updates" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e168 ">Updates the references automatically for Omnistudio standard wrappers.</td>

            <td data-label="After Migration" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e172 ">Omnistudio standard runtime + the <strong class="uicontrol">Omnistudio Metadata</strong>
              setting enabled.</td>

          </tr>
          <tr class="">
            <td data-label="Before Migration" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e156 ">Standard Data Model+Foundation Package+Metadata API enabled</td>

            <td data-label="Migration Actions Performed" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e160 ">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.</td>

            <td data-label="Package Dependencies Removed" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e164 ">
              <p>Removes managed package dependencies from:</p>
              <ul>
                <li>Custom Labels</li>

                <li>LWCs</li>

                <li>Apex classes</li>

              </ul>
              <div>
                <div class="slds-box slds-box_x-small slds-theme_shade slds-m-top_medium slds-m-bottom_medium">
                  <div class="slds-media slds-media_responsive">
                    <div class="slds-media__figure"><span class="slds-icon_container slds-icon_container_circle slds-icon-note-note"><img style="margin-bottom:0;" src="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" alt="Note"></span></div>
                    <div class="slds-media__body" style="padding-top:.5rem;padding-bottom:.5rem;"><span class="slds-text-title_caps">Note</span> Unlike other scenarios, Global Auto Numbers are not supported because the
                      corresponding custom entity does not exist in the Omnistudio namespace.</div>
                  </div>
                </div>
              </div>
            </td>

            <td data-label="Experience Sites and FlexiPages Updates" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e168 ">Updates the references automatically for Omnistudio standard wrappers.</td>

            <td data-label="After Migration" class="slds-cell-wrap" style="vertical-align:top;" headers="d110330e172 ">Omnistudio standard runtime</td>

          </tr>
        </tbody>
      </table>