Getting Started with Content Transfer Tool


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.

Source Environment Connectivity

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:

  • The target AEM as a Cloud Service environment: author-p<program_id>-e<env_id>
  • The Azure blob storage service: *
  • The User Mapping IO endpoint:

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 program_id, environment_id, and migration_token):

curl -i https://author-p<program_id>-e<environment_id> -H "Authorization: Bearer <migration_token>"


If an HTTP/2 200 is received, a connection to AEM as a Cloud Service was successful.

Running the Content Transfer Tool

Follow this section to learn how to use Content Transfer Tool to migrate the content to AEM as a Cloud Service (Author/Publish):

  1. Select the Adobe Experience Manager and navigate to tools -> Operations -> Content Migration.


  2. Select the Content Transfer option from Content Migration wizard.


  3. The console below appears when you create the first migration set. Click on Create Migration Set to create a new migration set.



    If you have existing migration sets, the console will display the list of existing migration sets with their current status.

  4. Populate the fields in Create Migration Set screen, as described below.


    1. Name: Enter the name of the migration set.


      No special characters are allowed for the migration set name.

    2. Cloud Service Configuration: Enter the destination AEM as a Cloud Service Author URL.


      You can create and maintain a maximum of ten migration sets at a time during the content transfer activity.
      Additionally, you have to create a migration separately for each of the specific environments - Stage, Development, or Production.

    3. Access Token: Enter the access token.


      You can retrieve the access token by using the Open access token button. You need to ensure that you belong to the ‘Administrators’ group in the target Cloud Service instance.

    4. Parameters: Select the following parameters to create the migration set:

      1. 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 wipe=true.

      2. 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:

        • /apps
        • /libs
        • /home
        • /etc (some /etc paths are allowed to be selected in CTT)
  5. Click on Save after you populate all the fields in the Create Migration Set details screen.

  6. You will view your migration set in the Content Transfer wizard, as shown in the figure below.


    All the existing migration sets are displayed on the Content Transfer wizard with their current status and status information. You may see some of these icons described below.

    • A red cloud indicates that you cannot complete the extraction process.
    • A green cloud indicates that you can complete the extraction process.
    • A yellow icon indicates that you did not create the existing migration set and the specific one is created by some other user in the same instance.
  7. Select a migration set and click on Properties to view or edit the migration set properties. While editing properties, it is not possible to change the Migration Set name or the Service URL.


What’s Next

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.

On this page