Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.
SOLVED

Helix-4 to Helix-5 Migration - Prerequisites & Docs

Avatar

Level 2

Hi all,

We are currently working for a customer that is on Helix-4. You can see the code repo here - https://github.com/hlxsites/danaher-ls-aem-prod.

We would like to upgrade from Helix-4 to Helix-5. So, here are things that we would need your support.

1. Could you pls point to the step by step documentation to migrate from Helix-4 to Helix-5. Can't find any comprehensive guide to do this on the public documentation.

2. We would like to understand if it is mandatory for all pages to be entirely on Universal Editor to migrate from Helix-4 to Helix-5. Asking this explicitly because, we still have some pages that are authored in AEM and being delivered through EDS via Converter module. More details here - https://github.com/hlxsites/danaher-ls-aem-prod/tree/main/tools

 

Thanks

BSR

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi @bsr78033597

The recommended migration path for moving your Edge Delivery Services (EDS) project from Helix-4 to Helix-5 is documented here: 
https://www.aem.live/developer/upgrade

Summarized steps include:

  • Switch your domains from hlx.live / hlx.page to aem.live / aem.page.
  • Migrate your site config to Helix-5's Config Service by POSTing to:
    POST https://admin.hlx.page/config/{org}/sites/{site}.json?migrate=true
  • Once migration is successful, remove legacy config files (fstab.yaml, config.xlsx) from your repository.
  • After switching to Helix-5, manage API keys and secrets using the new Config Service Admin docs.

    You can migrate your project and keep supporting pages authored in AEM and delivered via EDS "Converter" modules. The UE is recommended for most modern setups but doesn't force legacy projects to rewrite immediately; sites can transition gradually.

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

Please let me know if this helps or if you have any further questions.

View solution in original post

2 Replies

Avatar

Administrator

@konstantyn_diachenko @aanchal-sikka @h_kataria @Kamal_Kishor @Lokesh_Vajrala @Manu_Mathew_ @RiteshY18 @Sady_Rifat @MonalikaKapoor could you kindly take a look at this question when you have a moment? Your insights are much appreciated!



Kautuk Sahni

Avatar

Correct answer by
Employee

Hi @bsr78033597

The recommended migration path for moving your Edge Delivery Services (EDS) project from Helix-4 to Helix-5 is documented here: 
https://www.aem.live/developer/upgrade

Summarized steps include:

  • Switch your domains from hlx.live / hlx.page to aem.live / aem.page.
  • Migrate your site config to Helix-5's Config Service by POSTing to:
    POST https://admin.hlx.page/config/{org}/sites/{site}.json?migrate=true
  • Once migration is successful, remove legacy config files (fstab.yaml, config.xlsx) from your repository.
  • After switching to Helix-5, manage API keys and secrets using the new Config Service Admin docs.

    You can migrate your project and keep supporting pages authored in AEM and delivered via EDS "Converter" modules. The UE is recommended for most modern setups but doesn't force legacy projects to rewrite immediately; sites can transition gradually.

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

Please let me know if this helps or if you have any further questions.