If we want to upgrade AEM from 6.2 to 6.5 what is best approach(upgrade to new instance not inplace) for /content and dam migration.
I was trying with oak.jar upgrade with including necessary path /content/projectcontent and /content/dam/projectcontent.
Will this approach of oak-upgrade.jar works for 6.2 or it is recommended only for 6.3 and above versions.
Thanks in advance.
Solved! Go to Solution.
Thanks for the response.
It says both needs to be same version is it mandatory or lower to higher version is also possible ?
If possible then i also need to migrate the versions and timeline history on pages and dam is this can be achievable from this ?
There are different approaches to upgrade from older AEM versions to newer ones.
From my experience the most reliable and clean way is a combination of these two approaches:
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:
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!