Upgrade from 5.6.1 on a standalone separate 6.2 instance

[aemanonymous]

We have many sites running on 5.6.1 and we successfully did the in-place upgrade. As each site takes time to test, we would like to deploy it site by site on production by switching DNS to point to the new 6.2 site once thoroughly tested.

Can we create packages from 5.6.1 and deploy it in the new instance. If we are not bothered about versions and audit, is it fine to deploy the code and content packages (including DAM) to the fresh instance. Could someone please confirm if there will be any impact following this approach as the underlying architecture is different(CRX2, CRX3).

Also for Delta content from 5.6.1 production, we are thinking of using the ACS tool - http://adobe-consulting-services.github.io/acs-aem-commons/features/query-packager.html

[Opkar_Gill · Accepted solution]

Using packages to migrate content from 5.6.1 to 6.2 is not supported, there are changes in the repository structure which would not be correctly updated using this method. In the documentation the recommendation is to do an inlace upgrade, which you said have done. You could look at incremental migration as mentioned here[1].

[0]https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade/using-crx2oak.html

[1]https://jackrabbit.apache.org/oak/docs/migration.html

[kautuk_sahni]

Hi 

Please refer to the official documentation for Upgrading to 6.2 from 5.6.1. As stated by Opkar (Incremental upgrade must be done).

Link:- https://docs.adobe.com/docs/en/aem/6-2/deploy/communities/upgrade.html#Upgrading%20from%20AEM%205.6....

I hope this would be helpful.

Thanks and Regards

Kautuk Sahni

[aemanonymous]

Thanks Opkar for your input. In the case of incremental upgrade, how could we identify the recent changes. Is it by using http://adobe-consulting-services.github.io/acs-aem-commons/features/query-packager.html

[Opkar_Gill]

Hi,

please review the documentation[1], the section "Incremental Upgrade" it will help you understand the process and answer your question.

"If an existing repository is passed as the destination, then only a diff between source and destination will be migrated. It allows to migrate the content in a few iterations."

Regards,

Opkar

[1]https://jackrabbit.apache.org/oak/docs/migration.html

[aemanonymous]

Thanks Kautuk