DocumentationExperience Cloud KCS

Bulk moving assets to multiple destinations by naming conventions in Adobe Experience Manager Assets

Last update: September 9, 2026

This article explains the methods for moving assets in bulk from a Work-in-Progress (WIP) folder to multiple destination folders in Adobe Experience Manager (AEM) Assets based on file naming conventions or metadata. It clarifies supported product features and outlines recommended approaches.

Description description

Environment

Adobe Experience Manager Assets as a Cloud Service (all versions)

Issue/Symptoms

  • Organizations need to move large numbers of assets from a central Work-in-Progress (WIP) folder to appropriate destination folders.
  • The destination folder for each asset is determined by its filename or metadata.
  • The process needs to be automated so that assets are routed to the correct folders in a single action.
  • Assets that do not match any routing rule should remain in the WIP folder for manual review.
  • The WIP folder should be automatically deleted after all assets have been moved and the folder becomes empty.

Root cause

AEM Assets does not provide an out-of-the-box feature for rule-based, multi-destination asset moves based on naming conventions or metadata. This requirement must be addressed through manual operations or custom development.

Resolution resolution

Follow the steps below to resolve the issue.

  1. Review AEM Assets’ native bulk move capability.

    • AEM Assets allows you to select multiple assets and move them to a single destination folder in one operation.
    • For large batches, the move is processed asynchronously.

  2. Use a manual grouping and move workaround.

    1. In the WIP folder, group assets according to their naming pattern or metadata value (for example, by file type or prefix).
    2. Select all relevant assets in each group and use the standard Move operation to move them to the appropriate destination folder.
    3. Repeat this process for each group that matches a known pattern.
    4. Leave assets that do not match any known pattern in the WIP folder for manual review.
    5. After all assets have been moved and the WIP folder is empty, delete the WIP folder manually.

  3. Use a custom implementation for automation.

    1. If you require a single-action, rule-based routing process with automatic cleanup, implement it as a customization.
    2. Engage a qualified implementation partner to scope and deliver the required customization.
    3. For AEM as a Cloud Service, customizations must follow the Cloud Manager deployment model.

  4. Verify that assets appear in the correct destination folders and that the WIP folder is empty or deleted as intended.

recommendation-more-help
experience-cloud-kcs-help-kbarticles