The following table summarizes the prerequisites for using Content Transfer Tool.
Please review all the considerations listed below:
|Considerations||What is Currently Supported|
|AEM Version||Content Transfer Tool can be run on AEM 6.3 or higher versions only. To be able to use Content Transfer Tool with AEM 6.2 or older versions, an in-place upgrade of the content repository to AEM 6.5 is required. It is not required to upgrade the code to AEM 6.5 for this.|
|Size of Segment Store||An existing repository that has less than 55 million JCR nodes and up to 83 GB (online compacted size) on Author and 31 GB on Publish are currently supported. Create a support ticket with Adobe Customer Care to discuss options for segment store size above these limits.|
|Total Size of Content Repository
(segment store + data store)
|Content Transfer Tool is designed to transfer content up to 10 TB for File Data Store type of data store. Anything higher than 10 TB is not currently supported. Create a support ticket with Adobe Customer Care to discuss options for content larger than 10 TB.
For Amazon S3 and Azure Data Store types of data store, an optional pre-copy step can be used to significantly speed up the content transfer process and supports greater than 10TB size of data store.
|Total Index Size||Total index size of 25GB maximum is currently supported. Create a support ticket with Adobe Customer Care to discuss options for index size above this limit.|
|Node Name Length||Length of a node name must be 150 bytes or less. Node names longer than 150 bytes must be shortened to be <= 150 bytes in order to be supported by the Document node store in AEM as a Cloud Service. Ingestions will fail if these long node names are not fixed.|
|Content in Immutable Paths||Content Transfer Tool cannot be used to migrate content in immutable paths. To transfer content from
|Node property value in MongoDB||Node property values stored in MongoDB cannot exceed 16MB. This is enforced by MongoDB. Ingestions will fail if there are property values larger than this limit. Before running an extraction, run this oak-run script. Review all large property values and validate if they are needed. The ones that exceed 16MB will need to be converted to Binary values.|
Once you have reviewed the prerequisites and have determined whether you can use the Content Transfer Tool in your migration project, refer to Guidelines and Best Practices for using Content Transfer Tool.