Perform the following steps to migrate Splunk SOAR (On-premises) applications to Splunk SOAR (Cloud):

1. Convert all apps to use Python 3. See Convert apps from Python 2 to Python 3 in the Develop Apps for Splunk SOAR (On-premises) manual. You might have completed this step as part of the prerequisites for migration. See Prerequisites for migrating from Splunk SOAR (On-premises) to Splunk SOAR (Cloud).
2. Reinstall community applications. See Add and configure apps and assets to provide actions in Splunk SOAR (Cloud) in the Administer Splunk SOAR (Cloud) manual. Any community applications that are not Python 3 compliant must be converted to Python 3 prior to installation.
3. Configure certified Splunk SOAR (Cloud) applications. Certified Splunk SOAR (Cloud) applications that are Python 3 compliant are pre-installed and can be configured as they exist in your Splunk SOAR (On-premises) instance.
4. Convert and test custom apps for Python 3. See Convert apps from Python 2 to Python 3 in the Develop Apps for Splunk SOAR (On-premises) manual.
5. Ensure that custom applications don't have the same product_vendor and appid in the application configuration. This ensures that the application isn't overwritten by existing Splunk community or certified applications during upgrades or application updates. See Top level definition in the Develop Apps for Splunk SOAR (On-premises) manual.
6. If you have custom apps, be sure that all of the packages that those apps are dependent on are specified in the associated configuration JSON files as either wheel or PyPi dependencies. This might be required if you previously installed extra packages throughout the system using the phenv python pip install command, which is not possible in Splunk SOAR (Cloud) environments. See Specifying pip dependencies in the Develop Apps for Splunk SOAR manual.
7. If any of your playbooks or custom functions import libraries that were not provided by Splunk SOAR (on-premises), which were likely installed manually via the phenv python pip install command, you must either change those playbooks and custom functions to use only libraries provided by Splunk SOAR (Cloud), or create custom apps instead.