Skip to main content
MichaelTe5
Level 1
October 22, 2026
Question

Requirement: Refresh INT Environment with Production-Representative Content

Background

For testing, validation, and troubleshooting purposes, we need a supported and repeatable way to recreate or refresh our AEM as a Cloud Service INT environment with content that accurately reflects the current state of PROD.

Requirement

Adobe should provide a supported mechanism to independently copy each repository tier from PROD to INT, specifically:

  1. PROD Author → INT Author
  2. PROD Publish → INT Publish

Business Need

Our production Author and Publish repositories do not contain the same content or the same content versions.

As a result, refreshing only the INT Author environment and subsequently publishing all content to INT Publish does not reproduce the actual production state. This approach can introduce:

  • Draft content that has never been published
  • Unpublished authoring changes
  • Content versions that differ from production
  • Content intentionally absent from PROD Publish

Consequently, test results, defect analysis, and production issue replication performed in INT may not reflect real production behavior.

Expected Outcome

Adobe should provide a supported procedure or capability that allows:

Source Target
PROD Author INT Author
PROD Publish INT Publish


to be refreshed independently and directly, preserving the exact state of each repository tier.

Success Criteria

  • INT Author accurately represents PROD Author.
  • INT Publish accurately represents PROD Publish.
  • No republishing step is required to recreate the Publish state.
  • Published and unpublished content states remain consistent with production.
  • The process is fully supported by Adobe and suitable for regular environment refreshes.

Business Value

  • Reliable reproduction of production issues
  • Higher test accuracy
  • Reduced investigation effort
  • Lower risk of false-positive or false-negative validation results
  • Faster incident resolution for BMW Websites development and operations teams

1 reply

social_portfolio81db
Level 2
October 22, 2026

​@MichaelTe5 ,

Content Copy Tool is the closest thing today, but it only gets you half of this. It can copy PROD Author to INT Author (top-down, and you can include ACLs and wipe the target first). It can’t copy Publish. Adobe’s doc says content can only be copied from and to authoring services. It also skips version history and doesn’t track deletions.

If you want to avoid republishing everything, one workaround is to rebuild the published state on INT yourself:

  1. Unpublish the in-scope content on INT.
  2. Copy PROD Author to INT Author with Wipe turned on.
  3. Run a one-off job on INT Author that finds assets where jcr:content/cq:lastReplicationAction is Activate, then publish only those (Replication API or the Publish Content Tree workflow).

Test on a small folder first. I couldn’t find anything that confirms the replication status survives the copy.

Even then, you only get which items are published, not which version. An asset edited after its last publish in PROD will show the newer content on INT Publish. Content that exists only on PROD Publish won’t come across at all.

For an exact copy of both tiers, I’d raise an Adobe Support ticket and keep this Idea open.

Docs: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developer-tools/content-copy

Regards,

Santhosh

Translate
Terms & ConditionsAccessibility statement

Loading footer...