---
schema_version: "1"
id: 3c94d6eb5db2112309302eb250a3e0d635d8ba21acaffc8b47376b6f41cbfe0b
title: Update References to Use the Salesforce Standard Data Model
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_migrate_omnistudio_object_migration_post_migration_tasks.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_omnistudio_object_migration_post_migration_tasks.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e45494711b084b21274877697276ef23fcc9101940be6b270ef892a8f9b396f6
description: Perform cleanup tasks to ensure that your migrated content functions as expected.
products:
  - Omnistudio
release: "264"
---
# Update References to Use the Salesforce Standard Data Model

Perform cleanup tasks to ensure that your migrated content functions as expected.

- **[Set the Omnistudio Designers to Use the Standard Data Model](https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_change_the_sobject_data_model_after_migration.htm&release=264.0.0&type=5)**  
    As part of the migration from managed package runtime to Omnistudio standard runtime, execute an Apex class to set the Omnistudio designers to use the standard data model instead of the custom data model.
- **[Updates to Omnistudio Custom Functions](https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_update_omnistudio_custom_functions_after_migration.htm&release=264.0.0&type=5)**  
    If you're on the managed package runtime with standard data model, Omnistudio automatically converts all custom functions in the user-defined syntax to the standard syntax when you switch to the Omnistudio standard runtime. For the custom data model, first use Omnistudio Migration Assistant (Pilot) to convert your records to the standard data model, then switch to the standard runtime to automatically convert the custom functions.
- **[Update Omniscript Custom Lightning Web Components and Omniscript Elements Overridden with Customized Components](https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_omniscript_elements_with_overridden_components.htm&release=264.0.0&type=5)**  
    Migrate all custom Lightning web components that extend the omniscriptBaseMixin component or use a standalone component and all customized Omniscript elements that have overridden components from the managed package runtime to the standard runtime. This is a manual step.
- **[Update Components Deployed on Lightning Pages](https://help.salesforce.com/s/articleView?id=xcloud.os_update_comps_deploy_lightning_page.htm&release=264.0.0&type=5)**  
    To ensure that your components deployed on Lightning pages work as expected after you migrate from Omnistudio for Managed Packages to Omnistudio, check your Lightning page for all Omniscripts and Flexcards using the Vlocity LWC Wrapper or any custom Lightning web components (LWC), and replace those with the standard components.
- **[Update Components Deployed on Experience Cloud Site or Community Pages](https://help.salesforce.com/s/articleView?id=xcloud.os_update_comps_exp_community_page.htm&release=264.0.0&type=5)**  
    To ensure that your components deployed on Experience Cloud sites or Community pages work as expected after you migrate from Omnistudio for Managed Packages to Omnistudio, replace all Omniscripts and Flexcards using the Vlocity LWC Wrapper or any custom Lightning web components (LWC) with the standard components.
- **[Update References to Omnistudio Components After Migration](https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_update_references_to_dataraptors_from_apex_after_migration.htm&release=264.0.0&type=5)**  
    In the standard object data model, Data Mapper names, Flexcard names, and Omniscript and Integration Procedure types and subtypes can contain only alphanumeric characters.
- **[Update Remote Actions](https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_update_integration_procedure_remote_actions_after_migration.htm&release=264.0.0&type=5)**  
    To ensure that remote actions work as expected after you migrate from Omnistudio for Managed Packages to Omnistudio, update any Apex classes used in remote actions with the correct syntax.