Before you migrate MDM SaaS assets between organizations, ensure that the target organization meets the prerequisites.
Complete the following prerequisite tasks:
•To import predefined assets, ensure that you set up the corresponding licensed business applications. Also, ensure that the org versions of the business applications in the import file and the target organization match.
Note: To determine the org versions of the business applications in the import file, extract the import file and open the exportMetadata.v2.json file. The exportMetadata.v2.json file contains the org versions of business applications.
The following image shows the org version of an organization:
•To import custom assets, ensure that you set up at least one licensed business application that matches the business application in the source organization. Also, ensure that at least one business application org version in the target organization matches the version in the import file.
•If the source and target organizations are on different PODs, ensure that you migrate assets after both the PODs are upgraded to the same build version.
•You have user accounts in the source and target organizations with roles that have export and import privileges, such as the Administrator role or a combination of Designer, MDM Designer user roles.
•You have the required permissions to migrate the assets and folders from the source to the target organization.
•Before you migrate authorization configurations to a target organization, ensure that you first migrate the business entities and relationships.
•If you back up MDM SaaS assets periodically, back up all the assets after the organization is upgraded to the latest build version. The assets that you backed up before the October 2024 release are no longer valid.
