Review the Migration Reports (Vlocity Industries Managed Packages and Custom Data Model)

When you run the Omnistudio Migration Assistant in Migrate mode, it generates migration reports for Omniscripts, Flexcards, Data Mappers, Integration Procedures, Apex Classes, Omni Global Auto Numbers, FlexiPages, Experience Cloud Site Pages, Lightning Web Components, and Custom Labels. These migration reports highlight several key areas that require attention after migrating Omnistudio components.

The reports contain these migration statuses:

• Successfully migrated: The component is ready for migration without any manual updates.
• Skipped: The components are not migrated because these were marked as Needs manual intervention in the assessment report, and the identified issues were not manually resolved before migration. The Omnistudio Migration Assistant excluded these components from the migration process.
• Failed: These components are not migrated due to technical errors.
  

  Note If you have any components with Failed status, contact Salesforce Customer Support.

Review the Omnistudio migration reports for these Omnistudio components:

• Omniscripts Migration Report: Review the migration report for Angular Omniscripts and name changes. See Convert an Angular Omniscript to an LWC Omniscript.
• Flexcards Migration Report: Review the migration report for name changes, dependent Omniscripts, Integration Procedures, and Data Mappers in each Flexcard. Omnistudio Migration Assistant identifies this issue with Flexcards with dependencies on Angular Omniscripts.
• Data Mappers Migration Report: Review the migration report for name changes, duplicate names, custom functions, and Apex classes in the Data Mappers.
• Integration Procedures Migration Report: Review the migration report for name changes, duplicate names, and dependencies on other Integration Procedures, Data Mappers, and remote actions.
• Apex Classes Migration Report: Review the migration report for Apex classes that use remote actions with their file reference, comments, and errors. It also shows the file diff of changes made to the Apex classes by Omnistudio Migration Assistant during migration.
• Omni Global Auto Numbers Migration Report: Review the migration report for the list of all the migrated Omni global auto numbers in your org.
  

  Note Omnistudio Migration Assistant does not remove special characters from the Omni Global Auto Number names during migration.
• FlexiPages Migration Report: Review the migration report to verify that components that previously used <namespace>:vlocityLWCOmniWrapper are replaced with Omnistudio standard wrappers. For example, runtime_omnistudio:omniscript. Component attributes such as name, type, subtype, and language are also updated automatically.
• Experience Cloud Site Pages Migration Report: Review the migration report to verify that components that previously used <namespace>:vlocityLWCOmniWrapper are replaced with Omnistudio standard wrappers. Component attributes such as name, type, subtype, and language are also updated automatically.
• Lightning Web Components Migration Report: Review the migration report to verify that Lightning Web Components that previously used a <namespace> are now replaced with the c namespace during migration. Additionally, check the report for <runtimeNamespace>namespace</runtimeNamespace> tags that are removed from the *.js-meta.xml files post-migration.

  LWCs that fall under these categories are not migrated and are excluded from the migration report:

  • Auto-generated Omniscript LWCs containing Omniscript Auto-generated in js-meta.xml: When you have an Omniscript in a managed package, activating it creates a backend LWC automatically. These auto-generated LWCs are not migrated.
  • Auto-generated Flexcard LWCs prefixed with cf: When you have an Flexcard in a managed package, activating it creates a backend LWC automatically. Flexcard LWCs that are prefixed with cf are not migrated.
  • Omniscript component directory prefixed with Omniscript: Omniscript LWCs with this prefix are not migrated.
  • Language variant directories suffixed with MultiLanguage or English: LWCs in directories with these suffixes are not migrated.
  • Utility component directory containing Util: LWCs in a directory containing Util are not migrated.
  • lodash library directory containing lodash: LWC directory or metadata that references lodash is not migrated.
  • Definition files containing _def, definition, styleDefinition: Definition files that contain _def, definition, or styleDefinition are not migrated.
• Custom Labels Migration Report: For labels that pass successfully, it only displays the total count rather than listing each label individually.