---
schema_version: "1"
id: 3ae247980a290466481989dee2f4c283e753288ed9aaa635c6aa22dfc8e61426
title: Post-Migration Manual Tasks
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_migrate_post_migrate_manual_tasks.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_post_migrate_manual_tasks.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 4237820fd78c96c3109838536764b0d2cf0cf69e46fc14a3c1e3c267bbf0f6f0
description: "Perform these manual tasks after migration to resolve the issues:"
products:
  - Omnistudio
release: "264"
---
# Post-Migration Manual Tasks

Perform these manual tasks after migration to resolve the issues:

- Custom stylesheets with package namespace: If you’ve any custom stylesheets with package namespace included in your stylesheet elements:
    - Remove the package namespace from your stylesheets and replace it with `runtime_omnistudio, runtime_omnistudio_flexcard, runtime_omnistudio_omniscript, or runtime_omnistudio_common`.
    - If there are any changes to the HTML tags, which are used in custom stylesheets, change those tags to match standard runtime, accordingly.
- Integration Procedure handling empty Arrays when using `setValues` with Data Mapper: After migrating to the Omnistudio standard runtime, Integration Procedures that use the `setValues` action to pass data into a Data Mapper may show this runtime error: `No Input objects sent`. This error occurs when the `setValues` element passes an empty array to the Data Mapper input.
    
    Complete these steps to resolve the issue:
    
    1. From Setup, search and find **Integration Procedures**.
    2. Open the affected Integration Procedure and locate the element where the Data Mapper input is referenced.
    3. Open the element properties panel.
    4. Deselect the **Terminate when step fails** checkbox.
    5. Save and activate the Integration Procedure.
    6. Validate whether the Integration Procedure executes successfully without errors.
- Namespace mismatch after migrating Omnistudio components: When you migrate the Omnistudio components using the Omnistudio Migration Assistant, the auto-generated Lightning web components (LWCs) created for Flexcards or Omniscripts are not migrated. Depending on your source package, these auto-generated LWCs continue to reference their original namespace:
    
    - Vlocity Industries managed packages with custom data model or standard data model: Auto-generated LWCs continue to reference the vlocity managed package namespace.
    - Omnistudio Foundation package with standard data model: Auto-generated LWCs continue to reference the omnistudio namespace.
    
    If the custom LWCs are embedded within these auto-generated Omniscript or Flexcard LWCs, the custom components are migrated to the `c` namespace, creating a namespace mismatch. This mismatch causes cross-reference errors when you open or deploy the migrated components.
    
    Use one of these methods to resolve the issue:
    
    Enable the Lightning Web Security setting:
    
    1. In Setup, find and select **Session Settings**.
    2. Select the **Use Lightning Web Security for Lightning web components and Aura components** checkbox.
    3. Save your changes.
    
    Embed your Flexcard inside the standard wrapper:
    
    1. If a Flexcard is referenced on an Experience Cloud site page or record pages as custom LWC, replace the custom LWC with the Flexcard standard wrapper.
    2. If a Flexcard is referenced in an LWC on an Aura page as custom LWC, replace the custom LWC with `<namespace>:flexcardStandardRuntimeWrapper`. See [Activate and Publish a Flexcard](https://help.salesforce.com/s/articleView?id=xcloud.os_activateconfigureand_publish_flexcards_24744.htm&type=5&language=en_US).
- InteractionWrapper Lightning web component missing: After the namespace update, the deployment fails because the unmanaged package definition for the InteractionWrapper Lightning web component is not present in the org.
    
    To resolve the issue:
    
    1. Locate the `package.xml` file in your current working directory. This file is created when you run the Omnistudio Migration Assistant.
    2. Exclude the `InteractionWrapper` Lightning web component from the `package.xml` file.
    3. Redeploy the metadata using the Salesforce CLI.