How to identify impacted resources after CopyMoveAssetCommandBuilder asset moves?

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!