AEM 6.3 Upgrade Path



Hi All,

We are considering upgrading AEM 6.0 to AEM 6.3. With quite limited knowledge on this, can anyone suggest what would be the best solution for us?

The following is what we have now:

AEM 6.0 with SP1, SP2 and SP3

Java 8 (1.8.0_201-b09)

CRX: Apache Jackrabbit Oak 1.0.22

Classis UI

Frontend: Extjs, JSP

60 templates and customized components, all in html and jsp

What we expect:

AEM 6.3

Content migration with minimal work, such as without modifying templates and components code.

Retain classic UI

Retain Extjs

Open to HTL, mixed of Jsp and HTL

Our team is small and most of the jobs will be handled by the AEM developer. We like to lay out a plan to prepare for the upgrade but are not sure what the path will be. Any suggestion is greatly appreciated.

Accepted Solutions (1)

Accepted Solutions (1)




The recommended upgrade method is in-place upgrade that is supported for moving from AEM 6.0 to AEM 6.3 directly. Please pay close attention to content repository migration to ensure you use the right command for this purpose. You may want to review the following document:

Performing an In-Place Upgrade

Please note that Classic UI has been deprecated as of AEM 6.3. AEM 6.3 has the Classic UI included, and customers upgrading from earlier releases can keep using it as is. Note that Classic UI remains fully supported while being deprecated. But Adobe does not plan to make further enhancements to the Classic UI so it is recommended to start using Touch UI moving forward.

Deprecated and Removed Features

Answers (0)