Asset/CF location change in AEM Assets

Hi @shashankja1,

When you move an asset or a content fragment to a different location, you can do so safely using the "Move" operation provided in AEM Assets, which preserves references and updates them automatically - without breaking anything or needing to re-publish pages manually.

Use “Move” functionality via the UI

What it does:

• Updates all references (e.g., pages, templates, content fragments, Experience Fragments).

• Preserves version history and metadata.

• Optionally re-publishes the moved asset and its dependencies (if enabled).

How to Move safely via AEM Assets UI

1. Go to AEM Assets (/assets.html)

2. Navigate to the asset or content fragment.

3. Select the asset and click the "Move" icon from the top toolbar.

4. A wizard opens:

   • Select the new destination folder.

   • Enable the option “Update References” (usually checked by default).

5. Click Move.

AEM internally updates all references (including in /content, /conf, etc.) via its ReferenceUpdateService.

Does this require republishing?

• No, you don’t need to re-publish the pages unless:

  • The moved asset itself is not published yet in the new location.

  • You want the new path to be reflected on the published site (e.g., for direct asset links).

📝 AEM uses internal resource references (UUID-based), so pages referencing the asset will automatically point to the new path, and continue working without needing republishing.

Is there a workflow or job OOTB?

Yes:

AEM OOTB services involved:

1. ReferenceUpdateService – Automatically updates all references to the moved asset.

2. Move Page/Asset Workflow – Triggers updates and asset management tasks under the hood.

3. DAM Update Asset (optional) – Might be invoked after move to refresh renditions/metadata (configurable).

You do not need to create a custom workflow unless you have special post-move logic.