Skip to main content
Adobe Employee
June 1, 2026
Question

Content Copy between two different AEM Cloud programs

  • June 1, 2026
  • 2 replies
  • 34 views

We are looking to copy content between two environments across different AEM as a Cloud Service programs, such as from Environment A in Program A to Environment B in Program B.

We explored the Content Copy feature and can see the “Destination Program” option. However, after selecting the destination program, we are still able to see only the source program environments.

Is cross-program content copy currently supported? If yes, are there any prerequisites or additional configurations required for destination environments to appear?

2 replies

Saravanan_Dharmaraj
Community Advisor
Community Advisor
June 1, 2026

Hi ​@ShashankSa3 , currently “Cross-program and cross-region content copy is not possible” , please check out the below link

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/using/content-copy

Adobe Employee
June 2, 2026

We referred to the below documentation where it explicitly mentions:

“By default, Cross-Program content copy is disabled. However, upon customer request, it can be enabled, which makes an additional Destination Program input field available.”

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

Also found this Experience League discussion related to the same topic:

https://experienceleaguecommunities.adobe.com/adobe-experience-manager-sites-8/cross-program-content-copy-in-aem-as-a-cloud-service-13174

Since we are able to see the “Destination Program” option in the UI, we wanted to understand whether the feature is currently supported only for limited scenarios or still generally unsupported.

chaudharynick
Level 4
June 2, 2026

Hi ​@ShashankSa3 

Please check for the following

  1. if you have a deployment manager role in both programs
  2. if the destination program is enabled by adobe or not(by default its not enabled)
  3. if there are any running pipeline for the particular program/environment 
  4. if you are targeting a lower environment from the higher environment(prod → stage)