Migrating licensed modules
To accomplish this task, you must first download licensed modules from an on-premises instance of the application.
Note: The latest supported licensed modules
for migration is Infor Fashion PLM 15.1.9.3 Patch 3 release. You can only
migrate this version of licensed modules to 16.0.19 client version and up of
CloudSuite PLM for Fashion.
Licensed modules from lower versions of Infor Fashion PLM are supported but Infor recommends upgrading to the latest supported version before migrating.
These limitations apply when migrating Infor Fashion PLM licensed modules.
- User defined fields in additional information pane of style, material, and trim in Infor Fashion PLM are not migrated and are not automatically converted in CloudSuite PLM for Fashion.
- Due to the different implementation of features in CloudSuite PLM for Fashion, these items are not migrated:
- Style, material, trim, and request record comments
- System defined and custom report templates
- Language column values in the Translation section of each dictionary record
are migrated to CloudSuite PLM for Fashion. However, the actual
language value in CloudSuite PLM for Fashion may vary since languages
in Infor Fashion PLM are manually created, and are system defined in
CloudSuite PLM for Fashion.
For example, if English is the first language created in Infor Fashion PLM, the application gives it an ID of 001. In CloudSuite PLM for Fashion, the ID 001 is assigned to a different language, Afrikaans for example. Instead of displaying English as the translated language, Afrikaans is displayed by CloudSuite PLM for Fashion.
- Care symbols added to the Care tab of each material or trim record of Infor Fashion PLM are displayed with the care group and name values. When migrated in CloudSuite PLM for Fashion, the description is displayed instead of the name.