content and Asset Migration from Production AEM as cloud instance in one org level program to Stage AEM as a cloud instance in another org level program

[tnik]

Hi ,

We have a requirement where we need to transfer/copy the content (Pages and Assets) from Production AEM as a cloud instance which is in a particular cloud program lets say p1  to Stage AEM as a cloud instance which is in another cloud program lets say p2. Content transfer tool provided OOTB by Adobe does not support this use case as both the instances are in different cloud programs. The volume of assets is quite high. Is there any best strategy/approach which can be used to tackle this use case , also any approach to make this process automated. 

Any suggestion would be appreciated.

Thanks,

[arunpatidar]

Hi @tnik 
Content transfer tool uses vlt tool behind it, you can implement your own solution to do transfer between two different program

https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/developing/dev... 

ACS Common has built something as well : https://adobe-consulting-services.github.io/acs-aem-commons/features/contentsync/index.html 

[tnik]

Hi @arunpatidar ,

I have seen in the docs that content transfer tool is used only for AEM (On Prem or AMS ) content transfer to AEMaaCS , but our use case is cloud to cloud transfer , also the VLT and ACS commons links shared above , they seems to be around 6.5 , will those work in cloud. 

Can you share your thoughts please?

Thanks,

[arunpatidar]

Hi @tnik 
I think with vlt tool, it would be possible to transfer content, it basically connects to any jcr repository and transfer the node as .content.xml

[tnik]

@arunpatidar - CTT does not work in cloud to cloud migration as migration set is not created for source cloud instance  , so it is not of use in this case , we tried that .

Also  trying to use VLT by installing it locally and trying to transfer content from source to target cloud instance.

As far as ACS AEM commons utility is concerned , it works for small set of content , but fails to build catalogue if the content is slightly significant in nature

still exploring the most viable option for this use case , Also discussing with Adobe in the background

Thanks

[tnik · Accepted solution]

For this usecase Vlt wont work until CRX is blocked on cloud environment, best is to work with Adobe for their opinion and evaluate the options

[HrishikeshKa]

Hi @tnik ,

When migrating content and assets from one AEM as a Cloud instance to another AEM as a Cloud instance in different cloud programs, there are a few strategies and approaches you can consider:

1. Manual Export/Import: You can manually export the content and assets from the Production instance and import them into the Stage instance. This can be done using the Package Manager in AEM. However, this approach can be time-consuming and may not be suitable for large volumes of assets.

2. Custom Migration Scripts: You can develop custom scripts or utilities to automate the migration process. These scripts can use AEM APIs to export content and assets from the Production instance and import them into the Stage instance. This approach allows for more flexibility and customization but requires development effort.

3. Third-Party Migration Tools: There are third-party migration tools available that can help with content and asset migration between AEM instances. These tools often provide features like selective migration, scheduling, and error handling. You can explore options like Apache Sling Content Distribution or other commercial migration tools.

4. Cloud Manager: If you are using Adobe's Cloud Manager, it provides a built-in content and configuration migration feature. This feature allows you to migrate content and assets between different environments within the same cloud program. However, it may not support migration between different cloud programs. You can check with Adobe Support or documentation to confirm the capabilities of Cloud Manager for your specific use case.

When choosing an approach, consider factors such as the volume of assets, complexity of content structure, and the need for automation. It's also important to thoroughly test the migration process in a non-production environment before performing it in a production environment.

[tnik]

Hi @HrishikeshKa ,

Thanks for your response , but its more of generic thing , i am looking for any particular solution which has already been tried , i am trying VLT approach currently and Adobe does not provide any OOTB feature via Cloud manager for content sync between the programs , the content sync which Adobe provides only sync content from Prod to lower environment within a same cloud program. Package Manager is not feasible approach for the volume of assets we have 

Thanks,

[HrishikeshKa]

Hi @tnik ,

If you are looking for a specific solution that has been tried for migrating content and assets between different AEM as a Cloud instances in different cloud programs, you may want to consider using the Apache Sling Content Distribution tool.

Apache Sling Content Distribution is a content synchronization and distribution tool that can be used to replicate content and assets between different AEM instances. It provides features like selective replication, scheduling, and error handling.

To use Apache Sling Content Distribution for your migration, you can set up a distribution agent on the Production instance to publish content and assets to a distribution server. Then, you can set up a distribution agent on the Stage instance to subscribe to the distribution server and receive the content and assets.

This approach allows for more flexibility and customization than manual export/import or Cloud Manager, and can handle large volumes of assets. However, it does require some setup and configuration effort.

You can find more information on Apache Sling Content Distribution in the official Apache documentation or reach out to Adobe Support for guidance on using this tool for your specific use case.

[tnik]

Hi @HrishikeshKa ,

Can the sling distribution be used for moving content from author to author , i thought this is only used for moving the content be it pages and assets from author node to publish node of the same program. Can you please share the link to configuration steps of the above approach

Thanks,

[kautuk_sahni]

@tnik Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!