AEM - Upgrade to new service pack and Modernize implementation

[VishiCDN]

Hi,

I'm currently planning a phased migration and modernization strategy for our AEM instance, and I'd appreciate your insights and recommendations.

Here's our current setup and intended approach:

Instance Details:

Version: 6.5.4 (on-premise)
UI: Classic UI
Templates: Static

Planned Migration Steps:
a) Upgrade to AEM 6.5.19
b) Component Modernization: Transition classic dialogs to touch-enabled UI dialogs.

c) Template Modernization (Phased Approach):
      Introduce Editable Templates: Create new editable templates for key templates and convert them.
      Gradual Conversion: Address remaining templates in subsequent phases.

Can static and editable templates coexist seamlessly within the same instance during this phased transition?

Is this overall approach viable, or are there potential challenges or recommended alternatives?

Thank you!

[aanchal-sikka · Accepted solution]

@VishiCDN 

The Static and Editable templates can co-exist.

Surely, you can convert the Dialogs first and then plan for templates.

Just a word of caution, along with the Modernizer or Dialog conversion tools, you would still need to put in manual effort.

Preferably execute the conversion in phases/batches. 

[Madhur-Madan]

Hi @VishiCDN ,

Your phased migration plan sounds well-structured and feasible! To answer your first question: yes, static and editable templates can coexist within the same AEM instance. AEM supports having both types of templates simultaneously. This flexibility allows you to gradually transition without disrupting existing content or workflows.

Your approach aligns with best practices for AEM migration and modernization. However, there are a few considerations and potential challenges you might encounter:

1. Content Consistency: Ensuring content consistency between old static templates and new editable templates might require careful planning. The transition should ideally maintain content integrity without causing disruptions or inconsistencies.

2. Testing and Validation: : Each migration phase requires thorough testing to guarantee that functionalities, workflows, and content display remain consistent and error-free post-upgrades.

3. Performance and Compatibility: Upgrading to AEM 6.5.19 might impact performance or compatibility with current components or custom features. Prioritize reviewing release notes and conducting compatibility tests before the upgrade.

4. Custom Code and Extensions: Assess any custom code or extensions for necessary adjustments or updates to align with the updated AEM version or templates.

5. Backup and Rollback Strategy: Always have a robust backup plan and a rollback strategy in case any phase of the migration encounters unexpected issues.

Thanks,
Madhur