Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
joerghoh
joerghohAccepted solution
Adobe Employee
September 15, 2024

I think that you need to go through an intermediary step of AEM 6.5. That's because with AEM 6.4 some paths in the repository changed (for example /etc/tags moved to /content/cq:tags and some more things), which the migration tools to AEM CS don't handle. 

 

For that reason I would recommend to go through AEM 6.5 before:

  • The changes you need to do (both content- and code-wise) for AEM 6.5 are required for AEM CS anway, you don't waste effort when you migrate to AEM 6.5 first.
  • It allows you to split the amount of changes in 2 steps (AEM 6.2 -> AEM 6.5 and AEM 6.5 -> AEM CS); and that allows you to validate your first bunch of changes on AEM 6.5 (on-prem) and gain some confidence in it, before you then migrate to AEM CS.
View in thread

5 replies

sarav_prakash
Community Advisor
sarav_prakashCommunity Advisor
Community Advisor
September 14, 2024

Yes definitely. So you are migrating from onprem to cloud. There are few considerations, follow 

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

 

  1. What is the difference between onprem 6.x to cloud service ? here.
  2. Plan to migrate
  3. You ll plan for code migration, content migration, config migration. explained here.
  4. Adobe also provides a content transfer tool.
  5. You would forget about adminconsole, configuration managers, crxde for prod etc. Since cloud world many tools are suppressed for good reasons.
  6. There is premigration and postmigration documentations. 

To answer your question, `is it best practice`? It depends on your organization requirement. onprem vs cloud, each have their own pros, cons. Organizations choose what suits them. The migration process is well documented and ample community support have seen to help with migration. 

Translate
    NehaMa
    Level 4
    September 15, 2024

    hi @arunpatidar - Wanted to know can migration from lower version of AEM <6.3 possible directly to AEM as Cloud Service or we have to first migrate to AEM 6.5 and then can move to AEM as CS.

     

    Any relevant documentation/link referencing will help.

    Translate
      joerghoh
      Adobe Employee
      joerghohAdobe EmployeeAccepted solution
      Adobe Employee
      September 15, 2024

      I think that you need to go through an intermediary step of AEM 6.5. That's because with AEM 6.4 some paths in the repository changed (for example /etc/tags moved to /content/cq:tags and some more things), which the migration tools to AEM CS don't handle. 

       

      For that reason I would recommend to go through AEM 6.5 before:

      • The changes you need to do (both content- and code-wise) for AEM 6.5 are required for AEM CS anway, you don't waste effort when you migrate to AEM 6.5 first.
      • It allows you to split the amount of changes in 2 steps (AEM 6.2 -> AEM 6.5 and AEM 6.5 -> AEM CS); and that allows you to validate your first bunch of changes on AEM 6.5 (on-prem) and gain some confidence in it, before you then migrate to AEM CS.
      Translate
        NehaMa
        Level 4
        September 15, 2024

        Thanks @joerghoh for update

        Translate
          AMANATH_ULLAH
          Community Advisor
          AMANATH_ULLAHCommunity Advisor
          Community Advisor
          September 15, 2024

          @lakshmi08 @nehama 

          In case of AEM 6.2 , Content transfer tool is not supported

          The minimum system requirement for Content Transfer Tool is AEM 6.3 + and Java™ 8. If you are on a lower AEM version, upgrade your content repository to AEM 6.5 to use the Content Transfer Tool.

          https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/migration-journey/cloud-migration/content-transfer-tool/guidelines-best-practices-content-transfer-tool

           

          Translate
          Amanath Ullah
            Terms & ConditionsAccessibility statement

            Loading footer...