Manage and Migrate Assets > Migrating projects and assets > Prerequisites for migrating assets

Prerequisites for migrating assets

Before you migrate MDM SaaS assets from one organization to another, ensure that you meet the following prerequisites:

•Set up all the licensed business applications in the target organization.
•The import file and the target organization have the same org version.

Note: To determine the org version of 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:

Org version and build version numbers for Business 360 Console, Customer 360, Supplier 360, and Product 360 are October 2024.

•The source and target organizations must be upgraded to the October 2024 build version.
•If the source and target organizations are on different PODs, ensure that you migrate assets after both the PODs are upgraded to the October 2024 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.
•If you back up MDM SaaS assets periodically, back up all the assets after the organization is upgraded to the October 2024 build version. The assets that you backed up before the October 2024 release are no longer valid.