How to update/migrate content from lower to higher enviromnemt in AEM as a CS?

[parth3]

I am working on a AEM as a CS project, I need to migrate/update content from dev to prod but there is no way to do it. There is a tool that exists with which I can move the content from higher to lower env (from prod to dev and so on) but there's no way to do it from lower to higher (dev/qa to staging/prod).

Ideally, one would migrate from lower to higher env. Hence, I am wondering if anyone has faced this in past and if so, how this was tackled.

Thanks!

[h_kataria · Accepted solution]

You can use still leverage package manager to transfer the content or can check this feature from ACS commons as well https://adobe-consulting-services.github.io/acs-aem-commons/features/contentsync/index.html 

[AMANATH_ULLAH]

@parth3 

Content copy tool only migrates content from higher to lower environments. There is no tool from Adobe which can copy content to higher environments in AEMaaCS

Usually since content is created in production environment by authors, Content copy tool provides option to move content to lower environments

You can use package manager to move your content to higher environments 

[MukeshYadav_]

Hi @parth3 content cannot be copied from lower to higher environment https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/dev...

However still if we need to migrate we can use package manager or corresponding curl command

[Harwinder-singh]

@parth3  The copy content tool available in the cloud manager allows you to copy content from a higher environment to a lower environment and not the other way round. However, you can try copying content using the content transfer tool available in ACS commons library.

[Jagadeesh_Prakash]

@parth3  Below is my response. 

You can use content copy tool from PROD to any lower environment or between environments. But not from lower to PROD. Below is the documentation

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

If it's a small package we can do it via package manager. 

Note: Never sync content from lower environments to PROD. It is never recommonded 

[RahulBGPandey]

Hi @parth3 ,

Generally, we do content sync from Prod to lower environment, because of content is generated on Prod environment. 

But at the initial phase of the site development, we get the requirement to sync the lower environment content to the Prod, so we do it from the code base, and keep it as Mutable content. But this should be removed in later stage so that content generated on Prod should not get impacted.

/Thanks