How to identify impacted resources after CopyMoveAssetCommandBuilder asset moves? | Community
Skip to main content
G
GerardMa2
Level 1
May 18, 2026
Question

How to identify impacted resources after CopyMoveAssetCommandBuilder asset moves?

  • May 18, 2026
  • 2 replies
  • 43 views

Hi everyone,

I’m working on a large-scale DAM migration in Adobe Experience Manager using CopyMoveAssetCommandBuilder, and I’m trying to understand the best strategy for maintaining publish consistency after asset moves.

The main issue I’m facing is that CopyMoveAssetCommandBuilder updates references, but it does not seem to return the list of modified resources/paths affected by the operation (or at least I haven’t found a way to retrieve them).

Example:

  1. Asset is moved from one DAM path to another

  2. References inside Content Fragments are updated

  3. Pages consuming those Content Fragments are indirectly affected

  4. However, I don’t have a reliable way to identify all modified resources that should be republished

This becomes a major problem at scale because:

  • Content Fragments may remain unpublished with stale references

  • Pages consuming those fragments may also need republication

  • The dependency chain can become quite large

  • Manual traversal is expensive for hundreds of thousands of assets

What I’m trying to achieve:

  • A controlled migration process

  • Detection of all impacted resources recursively

  • Batched republication strategy

  • Error tracking/auditing persisted into DAM resources/files

  • Ability to retry failed republishes safely

Questions:

  • Is there any supported way to retrieve all modified paths/resources from CopyMoveAssetCommandBuilder?

  • Are there recommended APIs/services for resolving downstream references efficiently?

  • Would using Reference Search before/after the move be the recommended approach? And if so, how are teams resolving the second layer of dependencies (for example: Asset → Content Fragment → Pages consuming that Content Fragment)?

  • Any known patterns for keeping author/publish consistency during massive asset restructures?

Would appreciate any insights from people who have implemented large migration workflows in AEM Cloud.

Thanks!

    2 replies

    S
    Adobe Employee
    SubbaraoGa1Adobe Employee
    Adobe Employee
    May 18, 2026

    ​@GerardMa2 

    Thanks for the detailed write-up. Based on our review, we would not recommend relying on CopyMoveAssetCommandBuilder alone to identify every impacted resource after large-scale asset moves.

    We are not currently aware of a supported public API that returns the complete recursive impacted set from the move operation itself, especially for dependency chains such as Asset -> Content Fragment -> parent Fragment -> Page.

    Our recommendation is to:

    • use reference discovery before and after the move
    • recursively resolve downstream dependencies for Content Fragments and their consumers
    • persist the impacted set into an auditable manifest
    • republish in controlled batches using AEM Cloud's Tree Activation Workflow Step, which is the recommended bulk publication mechanism

    Sources:

    sarav_prakash
    Community Advisor
    sarav_prakashCommunity Advisor
    Community Advisor
    May 20, 2026

    Copied my response from duplicate question

     

     I too did a similar massive DAM project, with heavy taxonomy and move operations. Ended with production server crash, and taking multiple adobe support for prod issues. Then had to redo taxonomy to reduce MOVE operation.

     

    We separated MOVE operation; Needing reference update and NOT needing reference update. Used `resolver.move(sourcePath, destinationPath)` for no reference updates. But used same CopyMoveCommandBuilder for needing updates. Implemented splitting payload to chunks and run in batches. 

    There is an article for same https://techrevel.blog/2025/10/07/rename-move-an-aem-asset-programmatically-and-update-references/

     

    Terms & ConditionsAccessibility statement

    Loading footer...