Migrating from 6.2 to 6.5 or from on-prem to AEMaaCS

[jayv25585659]

Do I need to rebase my code to the latest maven project archetype or the BPA/pattern detector will do it for me via the recommendations/findings? 

Thanks

[ShivamKumar]

Hi @jayv25585659 ,

According to my understanding, the BPA or Pattern Detector will not rebase your code to the latest Maven project archetype. They will only provide recommendations and findings to help guide the migration. You must rebase manually if needed.

Both tools analyze your existing codebase to: Identify deprecated APIs or features, highlight areas that are incompatible with AEM 6.5 or AEM as a Cloud Service, suggest refactoring (e.g., replace custom OSGi configs with OSGi annotations). Flag usage of repository paths, run modes, or configurations that are problematic in AEMaaCS.

But neither tool modifies your code or project structure.

[jayv25585659]

But is code rebasing part of the migration process? I checked the info from adobe.com but it's not so clear. Thank you.

(I did a migration from 6.2 to 6.4 long ago but I cannot remember if the code was rebased)

[PRATHYUSHA_VP]

Hi @jayv25585659 

It's part of migration process to AEMasCS. Repository modernization tool can automate the process. Check below --

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/migration-journe...

Thanks

[jayv25585659]

is there something similar for on-prem upgrades (example: 6.3/6.4 to 6.5)? Thanks