AEM Upgrade | Community
Skip to main content
mohanr35700715
mohanr35700715
New Participant
Jul 28, 2017 12:35 PM UTC
Solved

AEM Upgrade

I have two simple sites on CQ 5.5. My plan is to move to AEM 6.3. Instead of upgrading the repository etc. (in place upgrade), my plan is to package the content and assets from 5.5 and deploy it on fresh new instance of AEM 6.3 (lift and shift). Do you see any challenges with this?

Thanks,

Mohan.

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
Employee
Jul 28, 2017 8:32 PM UTC

Besides the fact, that you need to make your application work on AEM 6.3, there are a few challenges with your approach (next to all the other items the others mentioned):

* Some structures might have changed in the course from CQ 5.5 to AEM 6.3; when you have deployed your 5.5 content package in AEM 6.3, make sure that you trigger the content upgrade processes.

* You will loose all the versions.

Kind regards,
Jörg

View reply

4 replies

sreesankara
sreesankara
New Participant
Aug 15, 2017 3:47 PM UTC

We migrated the sites from 5.6.1 to 6.3 in the similar approach instead of upgrade. I would recommend to use CRX2OAK.

I have an article on my blog about this

Adobe – CQ to AEM – Repository Migration – sree's WORLD

Translate
joerghoh
joerghohAccepted solution
Employee
Jul 28, 2017 8:32 PM UTC

Besides the fact, that you need to make your application work on AEM 6.3, there are a few challenges with your approach (next to all the other items the others mentioned):

* Some structures might have changed in the course from CQ 5.5 to AEM 6.3; when you have deployed your 5.5 content package in AEM 6.3, make sure that you trigger the content upgrade processes.

* You will loose all the versions.

Kind regards,
Jörg

Translate
ankurk67503819
Level 4
Jul 28, 2017 1:51 PM UTC

Hi,

There will be many issues in directly creating packages and deploying them to aem 6.3-

1. There could be content nodes which might have names with special characters those will be removed while installing , you might loose huge amount of content as in previous version those node names was not a issue.

2. On installing the dam package huge number of workflows will get triggered which will cause high load on servers.

3. Users and groups permissions might be difficult to package but in place upgrade will solve these issues.

4. Installing packages will take huge amount of time, in place upgrade will be too fast.

5. We migrated from aem 5.6 to aem 6.2 we tried creating packages and installing it over we faced many issues.

6. Anyways pom & code needs to be updated in any case

Hope this helps.

Translate
susheel
susheel
Level 5
Jul 28, 2017 1:41 PM UTC

Below are few of the things you might need to consider.

  • You might have to clean up deprecated code from backend.
  • Pom update and there might be chances that some code might not work completely. You might have to fix it.
  • As you are coming 5.5, you will have classic dialog components and it will work fine. But in later versions it might not be there.
  • So its better to shift your code to touch UI and sightly for better usage.
Translate
Terms & ConditionsAccessibility statement

Loading footer...