Content Copy / Content Sync should preserve published state and support scheduled, scalable Author→Author+Publish sync | Community
Skip to main content
R
Adobe Employee
rwunsch-adobeAdobe Employee
Adobe Employee
June 18, 2026
New

Content Copy / Content Sync should preserve published state and support scheduled, scalable Author→Author+Publish sync

  • June 18, 2026
  • 1 reply
  • 47 views

AEM as a Cloud Service "Copy Content" copies author-tier content only and intentionally strips replication-status metadata (cq:lastReplicated, cq:lastReplicationAction, cq:lastReplicatedBy, incl. the _publish/_preview variants). As a result, after a Prod→Stage copy the destination author has no record of what was published on the source, and nothing is published on the destination's publish tier.

The only way teams can reproduce the source's published state today is to build external tooling that:
1. queries the source (Prod) for the full activated set (e.g. via QueryBuilder), then
2. re-replicates exactly that set on the target (Stage), chunk by chunk.

This is inefficient by construction — it re-derives state the source environment already holds, it's bounded by QueryBuilder-over-HTTP result limits and request timeouts, and it doesn't scale to large
repositories (millions of nodes / multi-TB). We built and open-sourced such a tool to prove it works — https://github.com/rwunsch/aem-content-sync — but the fact that every customer has to build this is
the problem: it's redoing work the Content Copy tool itself should do.

Requested:
- An option to preserve replication status through Content Copy, and/or
- Auto-publish copied content on the target (so the destination publish tier matches the source), and
- Make these schedulable and scalable (delta/incremental, resumable), so lower environments can be kept in sync unattended without external scripts.

This would eliminate a whole class of brittle, slow custom tooling and make environment refreshes accurately reflect production's published state.

    1 reply

    K
    K_Pr
    Level 1
    June 23, 2026

    Hi ​@rwunsch-adobe 

    This behavior is currently expected in AEM as a Cloud Service.

    The Content Copy feature copies repository content between author environments, but it intentionally does not preserve replication-related properties such as `cq:lastReplicated`, `cq:lastReplicationAction`, and `cq:lastReplicatedBy` (including the `_publish` and `_preview` variants). Because these properties are removed during the copy process, the target environment has no knowledge of which content was activated in the source environment, and no content is automatically published on the target publish tier.

    At present, AEMaaCS does not provide an out-of-the-box mechanism to synchronize publication state as part of a Content Copy operation. Organizations that need Stage or lower environments to mirror Production's published state generally have to implement custom automation that:

    1. Identifies the activated content set in the source environment.
    2. Republishes the same content on the destination environment.

    The proposed enhancements—such as preserving replication metadata, automatically publishing copied content, or supporting scheduled and incremental synchronization—would certainly simplify environment refresh workflows. However, these capabilities are not available in the product today and would need to be considered as an enhancement request by Adobe.

    As a workaround, custom tooling or automation (such as the referenced `aem-content-sync` utility) can be used to recreate the publication state on the target environment.

    Hope this helps.

    Terms & ConditionsAccessibility statement

    Loading footer...