content Migration From AEM 5.56 to AEM 6.2 | Community
Skip to main content
Level 4
February 18, 2017
Solved

content Migration From AEM 5.56 to AEM 6.2

  • February 18, 2017
  • 3 replies
  • 1382 views

Hi,

We are planning to upgrade CQ version from 5.56 to 6.2.

I want to migrate /content/[project-name]/ all nodes from old to new one.

I tried with package manager but it did not succeeded as size is in GB.  and it throw Memory overflow error.

Any Help?

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ogill

Hi,

the docs for upgrades all recommend doing an in place upgrade, as this is what is tested internally at Adobe. The alternative is to use CRX2OAK, as Feike suggested, which allows you to migrate a path from the source repository to the target repository. Please note though, the old and new repository must be stopped. 

However, you should note that an in-place upgrade does more than just migrate the content, there are also post upgrade tasks which are run which transform the content for OAK, for example if you use MSM, then these tasks would be missed if you only did a content migration with CRX2OAK.

Regards,

Opkar

3 replies

smacdonald2008
Level 10
February 18, 2017

Refer to the AEM 6.2 upgrade documentation here: https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade.html

Feike_Visser1
Adobe Employee
Adobe Employee
February 20, 2017

Have a look at crx2oak, this is a filebased tool where the AEM-instances need to be offline.

ogillAdobe EmployeeAccepted solution
Adobe Employee
February 20, 2017

Hi,

the docs for upgrades all recommend doing an in place upgrade, as this is what is tested internally at Adobe. The alternative is to use CRX2OAK, as Feike suggested, which allows you to migrate a path from the source repository to the target repository. Please note though, the old and new repository must be stopped. 

However, you should note that an in-place upgrade does more than just migrate the content, there are also post upgrade tasks which are run which transform the content for OAK, for example if you use MSM, then these tasks would be missed if you only did a content migration with CRX2OAK.

Regards,

Opkar