Content Transfer Tool set Destination Folder

[ana_i-ensemble]

Hello,

I am using the Content Transfer Tool to migrate assets from AEM on-premise to AEM Cloud. 

Is there a way to set up a destination folder to define where I want the assets to be migrated?

So far I only saw that you can set the environment and that the assets will be migrated under the same folder structure as provided in the content set configuration.

If this is not available to be configured in the tool, what other alternatives are there to accomplish this use case?

Many thanks,

Ana

[DPrakashRaj]

Yes content transfer will follow the same folder structure on destination as the source an d it’s not configurable on content transfer tool as it’s me at to transfer the content and ideally it should follow the same structure.

To answer your question to is there a way to move the assets folder to different folder location you can use aem move operations with the assets and I believe it’s not going to be straightforward as those assets might be referenced on and pages so that change. We’d to be done as well and if you have predefined rules for ch aging the folders of assets you can automate this via writing your custom script and curl command for move operations on aem.

[giuseppebag]

AFAIK it is not possible with the Content Transfer Tool.

Maybe you can give a try to ACS Commons Renovator which assists you in moving or renaming content in bulk.

To perform multiple moves using Renovator, create an XLSX spreadsheet with "Source" and "Destination" columns. Each row specifies a source and destination path. Leave the source and destination fields blank in the Renovator process UI and provide the spreadsheet instead. A dry run is recommended to validate the file and see what will be affected.

[AmitVishwakarma]

Hi @ana_i-ensemble ,

CTT does NOT support setting a custom destination path.

The Content Transfer Tool is designed to preserve the exact structure from the source. It does not provide configuration options to remap folders or specify alternate destinations.

Alternative Solutions:

1. Post-Migration Move (Adobe Recommended Approach)

After migration, move assets to your desired folder using AEM Move Operations:

     - Can be done manually or scripted.

     - Be cautious about references (to avoid broken links).

2. ACS Commons - Content Renovator

Use for: Bulk moves with mapping.

Steps:

      - Create an Excel file:

Source Path: /content/dam/source/folder	Destination Path: /content/dam/new/folder

     - Go to AEM → Tools → ACS Commons → Content Renovator.

     - Upload the Excel, leave source/destination in UI blank.

     - Run dry run first to verify.

     - Execute actual move.

3. Custom Script with curl or Sling POST Servlet

Write a script to:

     - Use AEM’s Move Servlet:

curl -u admin:admin \
     -F ":operation=move" \
     -F ":dest=/content/dam/new-folder" \
     http://localhost:4502/content/dam/old-folder

Automate via Node.js, Bash, or Groovy script with a mapping file.

Use CTT to migrate → then use ACS Commons Renovator or custom script to move to destination folders.

Regards,
Amit