Best practices Aem cloud to on premise migration

[narendiran_ravi]

Hi All, 

We have a requirement to move few sites from AEMaaCS to on premise. Client has decided this due to some security requirements. Has anyone done this before. What are the best practices?

Do we need to make any code restructuring or is it backward compatible. Please share your thoughts 

[Hemalatha]

Hi @narendiran_ravi,

Moving to AEM Cloud Services from On premise is a long journey with various phases involving during the migration. You can check the below links as a starting point and contact with your Adobe Customer Success Manager to get personalized recommendations based on your Project Architecture & Needs.

Adobe AEMAACS Migration Guide Documentation:

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/migration-journe...

Adobe 2023 Summit Presentation on AEMAACS transitioning process:

https://business.adobe.com/summit/2023/sessions/transition-to-cloud-service-with-confidence-s312.htm...

An Informative blog about AEMAACS Cloud Migration journey:

https://one-inside.com/aem-cloud-service/migrate-aem-onprem-to-cloud/

Hope this helps!

Regards,

Hemalatha C

[narendiran_ravi]

Thanks @Hemalatha . We have a unique requirement to migrate from AEMaaCS to on-premise not the other way around.

[Hemalatha · Accepted solution]

@narendiran_ravi Sorry that I missed your specific requirement. We recently moved back from AMS to On Prem for a client. We did it with collaboration from Adobe CSE who helped in sharing the AWS Images of AEM repos which we set up again on the vanilla setup of On Prem AEM Servers. We did few code changes, IP rules update but overall it avoided the need to move assets, content seperately. But when it comes to AEMAACS the whole underlying infrsturcture is different. Try to compare what is compatible with On prem AEM 6.5 what is not compatible against what you have on AEMAACS, which gives you a clear picture on strategising your migration approach. This will be custom based approach based on your implementation. You need to consider migration of Assets, User ACLs, Workflows, Scheduled Jobs, Tags etc.

[EstebanBustamante]

Hi, 

That’s an interesting scenario. Off the top of my head, I don’t think you need to do any code refactoring, as long as the on-premise target is AEM 6.5 (with a recent service pack). However, pay special attention if you are using Sling Content Distribution or if you have any external asset ingestion processes, as these might require rework. The advantage is that you can quickly start a local AEM instance, deploy your code project, and see if anything is not working. This approach might be faster than troubleshooting the issues directly in the target environment.

Hope this helps

[narendiran_ravi]

Thanks for your suggestion. We have already tried installing and testing the code base locally. Do you have any input on migrating assets, content, and user accounts?

[EstebanBustamante]

There is no automated way to do this (only the other way around), so your best option would be to contact Adobe Support (AMS). They may provide you with more "automated" options or offer guidance on how to repurpose the storage you have on AEMaaCS servers. Otherwise, you will need to handle it manually.