Migrate existing AEM sites project to Edg Delivery Services via document-based authoring | Community
Skip to main content
Level 2
May 16, 2024
Solved

Migrate existing AEM sites project to Edg Delivery Services via document-based authoring

  • May 16, 2024
  • 2 replies
  • 2423 views

We have an already heavy, complex build website built in AEM sites, wanted to shift this site to Edge Delivery Services (Document-based authoring). What are the correct steps to migrate this existing site to EDS? How to integrate AEM with EDS?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Clemente-3SHARE

In case anyone else like me gets to this post and wonder about that converter Shashi is mentioning:


Connect with Adobe, they have a html converter in place using which you can keep aem sites intact but use EDS for website delivery which will convert aem hosted html to eds sematic html

I recently met with someone from Adobe who explained me that they have removed that converter because of the issues they experienced with different clients. If you are still curious about it, they based that converter on this: https://github.com/suntong/html2md.

Therefore, Adobe does not recommend that approach anymore for AEM-Based authoring. Instead, you should recreate your project using Edge Delivery Services Crosswalk project.

2 replies

Shashi_Mulugu
Community Advisor
Community Advisor
May 16, 2024

@sahildh1 what are the reasons behind choosing to move to EDS? Is it for ease of content management? Better and enhanced editing experience? Faster or better page load times? Based on the you need to choose your path forward.

 

Document based authoring may not give you best of your aem sites experience if you already have one.

 

Connect with Adobe, they have a html converter in place using which you can keep aem sites intact but use EDS for website delivery which will convert aem hosted html to eds sematic html

 

If you are building a net new website and have aem cloud license, then choose aem cloud EDS based Template site where you can still manage content with in aem leveraging msm, launches, translations, versionings etc but use EDS framework to build and deploy sites.

 

Last comes easiest and simplest option document based authoring but choose only if you are site is really simple or less server integration dependency.

Clemente-3SHARE
Clemente-3SHAREAccepted solution
Level 2
June 5, 2024

In case anyone else like me gets to this post and wonder about that converter Shashi is mentioning:


Connect with Adobe, they have a html converter in place using which you can keep aem sites intact but use EDS for website delivery which will convert aem hosted html to eds sematic html

I recently met with someone from Adobe who explained me that they have removed that converter because of the issues they experienced with different clients. If you are still curious about it, they based that converter on this: https://github.com/suntong/html2md.

Therefore, Adobe does not recommend that approach anymore for AEM-Based authoring. Instead, you should recreate your project using Edge Delivery Services Crosswalk project.

kautuk_sahni
Community Manager
Community Manager
May 20, 2024

@sahildh1 Did you find the suggestion helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

Kautuk Sahni
SahilDh1Author
Level 2
May 20, 2024

@kautuk_sahni Yes, the suggestion was helpful. 

Thanks