The Content Transfer Tool can be downloaded as a zip file from the Software Distribution Portal. You can install the package via Package Manager on your source Adobe Experience Manager (AEM) instance. Make sure to download the latest version. For more details on the latest version, refer to Release Notes.
Download the Content Transfer Tool, from Software Distribution portal.
A connection error can also occur if a migration set has been deleted from Cloud Acceleration Manager.
The source AEM instance may be running behind a firewall where it can only reach certain hosts which have been added to an Allow List. In order to successfully run an extraction, the following endpoints will need to be accessible from the instance that is running AEM:
To test connectivity to the target AEM as a Cloud Service environment, issue the following cURL command from the shell of the source instance (replace
curl -i https://author-p<program_id>-e<environment_id>.adobeaemcloud.com/api/migration/migrationSet -H "Authorization: Bearer <migration_token>"
HTTP/2 200 is received, a connection to AEM as a Cloud Service was successful.
Understanding SSL/TLS connection problems can sometimes be difficult. To toubleshoot connection issues during an extraction process, you can enable SSL logging via the System Console of the source AEM environment by following these steps:
Navigate to the Adobe Experience Manager Web Console on your source instance, by going to Tools - Operations - Web Console or directly to the URL at https://serveraddress:serverport/system/console/configMgr
Search for Content Transfer Tool Extraction Service Configuration
Use the pencil icon button to edit its configuration values
Enable the Enable ssl logging for extraction setting, then press Save:
The following section applies to the new version of the Content Transfer Tool. Follow this section to learn how to use the Content Transfer Tool to migrate content to AEM as a Cloud Service:
Log into Cloud Acceleration Manager (CAM) and click on the CAM project that you had created previously to assess your readiness to move to AEM as a Cloud Service. If you haven’t created a CAM project, refer to Creating and Managing a Project in CAM.
Click on the Content Transfer card. This will take you to the Migration Set List view.
Create a Migration Set by clicking on Create Migration Set.
A maximum of five migration sets can be created per project in Cloud Acceleration Manager.
You should now see your migration list in the list view. Click on the three dots symbol (…) to open the dropdown and click on Copy Extraction key. You will need this key during the Extraction phase. Copy this Extraction key.
The extraction key enables your source AEM environment to securely connect to the migration set. Please treat this key with the same care that you would a password, and never share it over an unsecured medium like email.
To populate the migration set you created in the Cloud Acceleration Manager, you need to install the latest version of the Content Transfer Tool on your source Adobe Experience Manager (AEM) instance. Follow this section to learn how to populate the migration set.
After installing the latest version (v2.0.10) of the Content Transfer Tool on your source Adobe Experience Manager instance, go to Operations - Content Migration
Click on Create Migration Set
Paste the extraction key that was copied from CAM earlier into the Extraction key input field of Create Migration Set form. Once you do this, the Migration set name and Cloud Acceleration Manager (CAM) Project name fields will be automatically populated. These should match the Migration Set name in CAM and the CAM project name that you created. You can now add content paths. Once you’ve added content paths, you will be able to save the migration set. You can run the extraction with either versions included or excluded.
Make sure that the extraction key is valid and is not close to its expiration. You can get this information in the Create Migration Set dialog after you paste the extraction key. If you get a connection error, refer to Source Environment Connectivity for more information.
Next, select the following Parameters to create a Migration Set:
Include Version: Select as required. When versions are included, the path
/var/audit is automatically included to migrate audit events.
If you intend to include versions as part of a migration set, and are performing top-ups with
wipe=false, then you must disable version purging due to a current limitation in the Content Transfer Tool. If you prefer to keep version purge enabled and are performing top-ups into a migration set, then you must perform the ingestion as
Paths to be included: Use path browser to select paths which need to be migrated. Path picker accepts input by typing or by selection.
Following paths are restricted while creating a migration set:
/etcpaths are allowed to be selected in CTT)
Click on Save after you populate all the fields in the Create Migration Set details screen.
After creating a migration set, it is highly recommended to run a size check on the migration set before starting an Extraction process.
By running a size check on the migration set, you will be able to:
crx-quickstartsubdirectory to complete extraction successfully.
Follow the steps below to run a size check:
Select a migration set and click on Check Size.
This will open up the Check Size dialog.
Click on Check Size to start the process. You will then return to the migration set list view and you should see a message indicating that Check Size is running.
Once Check Size process is completed, the status will change to FINISHED. Select the same migration set and click on Check Size to view results. Below is an example of Check Size results with no warnings.
If the Check Size results indicate that either there is insufficient disk space and/or the migration set exceeds product limits, WARNING status will be displayed.
Once you have learned how to create a migration set, you are now ready to learn about Extraction and Ingestion Processes in Content Transfer Tool. Before you learn these processes, you must review Handling Large Content Repositories to significantly speed up the extraction and ingestion phases of the content transfer activity to move content to AEM as a Cloud Service.