Hi everyone,I’m working on a large-scale DAM migration in Adobe Experience Manager using CopyMoveAssetCommandBuilder.The main issue is that while references are updated during asset moves, I can’t find a way to retrieve all modified resources/paths affected by the operation.Example: Asset is moved Content Fragment references are updated Pages consuming those fragments are indirectly affected But I can’t reliably identify everything that should be republished At scale, this creates publish consistency concerns because Content Fragments and pages may remain published with stale references.What I’m trying to achieve: Detect impacted resources recursively Republish in controlled batches Track errors/audit results in DAM Retry failed republishes safely Questions: Is there a supported way to retrieve modified resources from CopyMoveAssetCommandBuilder? Are there recommended APIs/services for resolving downstream dependencies efficiently? Is Reference Search the recommended approach for handling dependency chains like Asset → Content Fragment → Page? Any best practices for maintaining author/publish consistency during large DAM restructures? Would appreciate any insights from teams that have handled large migrations in AEM Cloud.Thanks!

Level 1

Question

Scaling DAM migrations in Adobe Experience Manager: tracking affected resources after asset moves

Forum|Forum|26 days ago
May 18, 2026
2 replies
42 views

Hi everyone,

I’m working on a large-scale DAM migration in Adobe Experience Manager using CopyMoveAssetCommandBuilder.

The main issue is that while references are updated during asset moves, I can’t find a way to retrieve all modified resources/paths affected by the operation.

Example:

Asset is moved
Content Fragment references are updated
Pages consuming those fragments are indirectly affected
But I can’t reliably identify everything that should be republished

At scale, this creates publish consistency concerns because Content Fragments and pages may remain published with stale references.

What I’m trying to achieve:

Detect impacted resources recursively
Republish in controlled batches
Track errors/audit results in DAM
Retry failed republishes safely

Questions:

Is there a supported way to retrieve modified resources from CopyMoveAssetCommandBuilder?
Are there recommended APIs/services for resolving downstream dependencies efficiently?
Is Reference Search the recommended approach for handling dependency chains like Asset → Content Fragment → Page?
Any best practices for maintaining author/publish consistency during large DAM restructures?

Would appreciate any insights from teams that have handled large migrations in AEM Cloud.

Thanks!

S

SubbaraoGa1

Adobe Employee

@PabloSe1 How to identify impacted resources after CopyMoveAssetCommandBuilder asset moves? | Community

Here we can see the same posts.

sarav_prakash

Community Advisor

Cheers @PabloSe1 , 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/

Is there a supported way to retrieve modified resources from CopyMoveAssetCommandBuilder? - builder already provides. But better to run separate using either https://developer.adobe.com/experience-manager/reference-materials/6-4/javadoc/com/day/cq/dam/commons/util/AssetReferenceSearch.html or xpath query is faster
Are there recommended APIs/services for resolving downstream dependencies efficiently? I learnt, to stay way from AEM for downstreams. Used AIO Events, subscribe to asset publish event and do outside AEM. explained in this article https://medium.com/@bsaravanaprakash/building-content-supply-chain-using-workfront-aio-journaling-appbuilder-runtime-actions-finally-4d7a6ca0fbf2
Is Reference Search the recommended approach for handling dependency chains like Asset → Content Fragment → Page? Its slow. And it most times crashes. This API runs at Sling, captures entire jcr snapshot into JVM and then filters. It crashes for large DAM. Instead I was able to add correct lucene property index and run SQL-2 queries faster. Not using reference search
Any best practices for maintaining author/publish consistency during large DAM restructures? Reduce move operation. or seggregate operations needing move + nomove and use different APIs. Try to batch the job and run in chunks. Explained in my article here https://medium.com/@bsaravanaprakash/how-to-chunk-your-large-sling-job-into-micro-jobs-0555a15f6a32

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded