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
BedrockMission!

Learn More

View all

Sign in to view all badges

Migration from 6.1 to 6.4 steps

Avatar

Avatar
Affirm 1
Level 3
manikanthar1295
Level 3

Likes

7 likes

Total Posts

83 posts

Correct Reply

1 solution
Top badges earned
Affirm 1
Validate 25
Give Back 10
Give Back 5
Give Back 3
View profile

Avatar
Affirm 1
Level 3
manikanthar1295
Level 3

Likes

7 likes

Total Posts

83 posts

Correct Reply

1 solution
Top badges earned
Affirm 1
Validate 25
Give Back 10
Give Back 5
Give Back 3
View profile
manikanthar1295
Level 3

04-05-2021

Hi Team,

 

Currently we are using AEM 6.1 version planning  to move AEM 6.4 version.

Is there any predefined steps for this.

predefined tools to migrate content from 61 to 6.4

 

any information regarding migration this kindly share here.

 

Regards

Manikantha R

 

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Applaud 25
Level 10
asutosh_jena
Level 10

Likes

576 likes

Total Posts

687 posts

Correct Reply

199 solutions
Top badges earned
Applaud 25
Give Back 100
Boost 500
Affirm 100
Ignite 1
View profile

Avatar
Applaud 25
Level 10
asutosh_jena
Level 10

Likes

576 likes

Total Posts

687 posts

Correct Reply

199 solutions
Top badges earned
Applaud 25
Give Back 100
Boost 500
Affirm 100
Ignite 1
View profile
asutosh_jena
Level 10

04-05-2021

Hi @manikanthar1295 

 

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

https://helpx.adobe.com/ca/experience-manager/6-4/sites/deploying/using/in-place-upgrade.html


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.

 

List of deprecated APIs:

https://helpx.adobe.com/experience-manager/6-4/sites/developing/using/reference-materials/javadoc/de...

 

Detailed steps here:

https://experienceleague.adobe.com/docs/experience-manager-64/deploying/upgrading/upgrade.html?lang=...

https://labs.tadigital.com/index.php/2019/04/17/upgrading-from-aem-6-x-to-aem-6-4/

 

Thanks!

 

 

Answers (3)

Answers (3)

Avatar

Avatar
Springboard
MVP
Shashi_Mulugu
MVP

Likes

224 likes

Total Posts

283 posts

Correct Reply

65 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Applaud 100
Establish
View profile

Avatar
Springboard
MVP
Shashi_Mulugu
MVP

Likes

224 likes

Total Posts

283 posts

Correct Reply

65 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Applaud 100
Establish
View profile
Shashi_Mulugu
MVP

04-05-2021

@manikanthar1295 please refer to EOL matrix for AEM 6.4.

https://helpx.adobe.com/support/programs/eol-matrix.html

 

Hope you have contacted Adobe for this migration?

 

I would recommend to upgrade to AEM 6.5 latest service pack if it is on premise or to either AEM 6.5.8 or AEM Cloud incase of AMS unless you have strong reasons for not doing so 

Avatar

Avatar
Boost 100
Employee
markus_bulla_adobe
Employee

Likes

110 likes

Total Posts

89 posts

Correct Reply

46 solutions
Top badges earned
Boost 100
Applaud 25
Affirm 25
Boost 50
Boost 25
View profile

Avatar
Boost 100
Employee
markus_bulla_adobe
Employee

Likes

110 likes

Total Posts

89 posts

Correct Reply

46 solutions
Top badges earned
Boost 100
Applaud 25
Affirm 25
Boost 50
Boost 25
View profile
markus_bulla_adobe
Employee

04-05-2021

Hi @manikanthar1295!

Please refer to my answer on this thread [1].
The recommendation is the same for most (if not all) versions of AEM.

 

[1] https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/upgrade-6-2-to-6-5/qaq-p/4...

 

Citing my answer here for your ease:

 

There are different approaches to upgrade from older AEM versions to newer ones.

  • In place upgrade - basically stopping your instance, replacing the quickstart.jar with the newer version and starting it again.
  • Upgrade to a new environment - setting up a new environment with the target version and migrating your project (content, code, configurations, etc.) to that new environment.

From my experience the most reliable and clean way is a combination of these two approaches:

  • Setup a new, clean environment with the target version.
  • Perform an in-place upgrade on the old environment.
  • Migrate everything from the old to the new instance (e.g. using the crx2oak tool).

The upgrade process includes rewriting/relocation/transformation of certain elements in the content. This step may get lost if you just migrate your content from an old 6.2 or 6.3 instance to a new 6.5 environment using a content migration tool, such as crx2oak.

 

Apart from the "pure" instance upgrade/migration, please also consider the following tasks that make sense and/or are necessary for an upgrade:

  • Upgrade your JRE to the latest supported version. AEM 6.5 supports Java 8 and 11.
  • Make sure to include the latest Service Pack on the target version (SP 8 for AEM 6.5).
  • Perform some clean-ups and grooming on your repository before migration. Get rid of everything that is no longer needed, execute the common maintenance tasks (workflow and version purge) and run a repository compaction.
  • Upgrade your projects dependencies (primarily the uber-jar).
  • Refactor your code to ensure it's functioning as expected under the new version and with the new dependencies.
  • Consider upgrading any 3rd party libraries, integrations and similar to their respective latest versions as well.
  • Consider some code refactoring work to follow the latest recommendations and best practices, avoid usage of deprecated APIs/features/etc. and make your code base as modern, clean and up-to-date as possible.
  • Consider automating the provisioning and configuration of your AEM environments.

Please also note: the bigger the upgrade version step, the more work it is. So plan to test the actual migration process, ideally on a production clone to ensure that you are comfortable with it and there are no surprises during the actual migration run.

 

Please also refer to these documentations:

 

Hope that helps!