Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM 6.1 to 6.4 inplace migration

Avatar

Level 1

What are the best practices in managing in place AEM migration related to existing content.

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

You might have to refactor your code to use the updated API's(Check [1]) but as far as content is concerned, the upgrade will not change anything under the "/content" directory.

That being said, Repository was restructured in AEM 6.4 and most of the folders from /etc were moved to either /conf or /apps or /content. Please check [2] and make sure you update the location for workflows/tags/clientlibs

[1] Deprecated List ("The Adobe AEM Quickstart and Web Application.")

[2] Pomocník pre Adobe Experience Manager | Repository Restructuring in AEM 6.4

View solution in original post

0 Replies

Avatar

Employee Advisor

It is recommended to follow the official documentation at [1]

Other Best practices I could think of:

- Make sure you run all the pre-upgrade and maintenance tasks before the upgrade.

- Watch the upgrade.log while running content migration and check for any errors. You should not proceed till you observe no errors.

- When starting the AEM instance for the first time after replacing the jar, tail the error.log to check for any errors.

- Log a Daycare ticket if you are not able to figure out the errors on your own.

[1] Performing an In-Place Upgrade

Avatar

Level 3

Hi Jaideep,

Thanks for sharing the documentation. Have few queries :

  • Will migration from lower to higher version, will affect any existing set up services for existing Content support team ?
  • Will Content authors/Publishers has to do some updates or changes during or after this migration ?

Looking forward to your response.

Thanks

Piyush

Avatar

Correct answer by
Employee Advisor

You might have to refactor your code to use the updated API's(Check [1]) but as far as content is concerned, the upgrade will not change anything under the "/content" directory.

That being said, Repository was restructured in AEM 6.4 and most of the folders from /etc were moved to either /conf or /apps or /content. Please check [2] and make sure you update the location for workflows/tags/clientlibs

[1] Deprecated List ("The Adobe AEM Quickstart and Web Application.")

[2] Pomocník pre Adobe Experience Manager | Repository Restructuring in AEM 6.4