IFS Data Migration supports to move data from and to IFS Cloud. Technical Limitations and Architectural decisions taken when implementing this can make it impossible to associate in all instances.
Note: This page lists a number of situations that is important to be aware of in order to work efficiently with Data Migration tool. There are actually more situations that can be considered as a limitation than listed here.
CLOB type columns will not be supported in Data Migration Tool. Only capable of handling up to the max limit of VARCHAR2.
Custom Enumerations with default values
Due to a design limitation, it will not migrate data for a custom enumeration with default values using the procedure, INSERT\_BY\_METHOD\_NEW. As a workaround, kindly use both DB and client values for this. Further.csv files which are opened using Microsoft Excel will cause the "True" and "False" values to be uppercased. If the client values for the enumerations are Pascal case True and False, (Ex: FndBoolean) it will cause issues when migrating. Please use a Conversion List and convert this to the correct case.
The Job ID should only contain characters, numbers and "\_". Currently, this validation is not available. Therefore, including other characters like spaces or "-" in the Job ID creates errors when executing migration jobs which requires creating dynamic procedures (Ex: CREATE\_TABLE\_FROM\_FILE, EXCEL\_MIGRATION with custom fields).