Last updated: 28 Sep 2022
This tool has limitations on which content can be migrated and which not. Some limitations are set by the availability of suitable APIs, while other limitations are defined by security constraints.
Below is an overview of all limitations of this migration tool.
Generic limitations of SAP Integration Suite on Multi Cloud are also documented in SAP Note 2752867.
| Limitation | Reason | Solution |
|---|---|---|
| Version history can not be migrated | No suitable API to export history | |
| Draft items can not be migrated | No suitable API to export draft items | Save item as new version first |
| Custom Groovy and Javascript code is analyzed for usage of Environment Variables, which may generate alerts in the tool but the custom code is not modified/corrected | Can not automatically correct custom code | Manually review the alerts and make appropriate changes. See SAP Help page |
| Limitation | Reason | Solution |
|---|---|---|
| User Credentials of type 'Default' and 'Successfactors' can be migrated but will be created without the correct password/secret. User Credentials of type 'open connectors' can not be migrated | Security reasons | Set password/secret manually after migration |
| Only OAuth credentials of type 'Client Credentials' can be migrated, not 'SAML Bearer Assertion' or 'Authorization Code' | Security reasons | Re-create the item manually |
| Only Keystore entries of type 'Certificate' can be migrated, not 'Key Pair', 'SSH Key' or 'Keystore'. Also entries indicated with 'Maintained by SAP' can not be migrated | Security reasons | Re-create the item manually |
| Secure Parameters can not be migrated | No suitable API available | Re-create the item manually |
| Known Hosts can not be migrated | No suitable API available | Re-create the item manually |
| PGP Keyrings can not be migrated | No suitable API available | Re-create the item manually |
| Delivered in v1.2.0 |
| Limitation | Reason | Solution |
|---|---|---|
| Delivered in v1.3.0 | ||
| Delivered in v1.1.0 | ||
| JDBC Material can not be migrated | No suitable API available | |
| Message Store can not be migrated | No suitable API available | |
| JMS Queue Entries can not be migrated | Not necessary | Empty queue on Neo tenant before migration |
| Limitation | Reason | Solution |
|---|---|---|
| Custom Adapters can not be migrated | No suitable API available | Re-create the item manually |
| Partner Directory can not be migrated | No suitable API available | Re-create the item manually |
| Idempotent Repository for XI, AS2, SFTP and FTP adapters | No suitable API available |