Path changes while upgrading from AEM 6.3 to AEM 6.5

Before we start any AEM upgrades we should ensure that a detailed study is done on the release notes.

If the upgrades are planned to the next direct version (Say AEM 6.4 to AEM 6.5), We can just read the release notes of AEM 6.5 and proceed for the upgrade. But if the case is different (AEM 6.3 to AEM 6.5) ensure we are comparing the release notes for each versions.

For eg: Say we are upgrading from AEM 6.3 to AEM 6.5. We know there was an AEM 6.4 available. So while upgrade, first understand the release notes of AEM 6.4 and observe the changes between AEM 6.3 to AEM 6.4 and do the same comparison from AEM 6.4 to AEM 6.5. This process ensure that we are identifying every changes and accommodating all changes by taking precaution not to break anything during upgrades.

Approach

AEM 6.3 -> AEM 6.4(Release Notes) -> AEM 6.5 (Release Notes)

AEM 6.3 to AEM 6.5 Path Changes

Notes:  AEM content is being restructured out of /etc to other folders in the repository, along with guidelines on what content goes where, adhering to the following high-level rules:
•    AEM product code will always be placed in /libs, which must not be overwritten by custom code
•    Custom code should be placed in /apps, /content, and /conf

Old Path	New Path
/etc/workflow/models	/libs/settings/workflow/models   /conf/global/settings/workflow/models   /var/workflow/models
/etc/workflow/instances	/var/workflow/instances
/etc/workflow/launcher/config	/libs/settings/workflow/launcher/config   /conf/global/settings/workflow/launcher/config
/etc/workflow/scripts	/libs/workflow/scripts   /apps/workflow/scripts
/etc/designs/default	/libs/settings/wcm/designs/default   /apps/settings/wcm/designs/default
/etc/taskmanagement	/var/taskmanagement
/etc/tags	/content/cq:tags
/etc/notification/email/default/com.day.cq.replication	/libs/settings/notification-templates/com.day.cq.replication   /apps/settings/notification-templates/com.day.cq.replication
/etc/workflow/notification	/libs/settings/workflow/notification   /conf/global/settings/workflow/notification
/etc/workflow/packages	/var/workflow/packages

How do we estimate an AEM Migration project?

There are scenarios where we need to migrate any existing CMS content to AEM. The steps for migration are given in my previous post.

Now let us see how do we estimate the migration activities.

Below given the activities for doing a proper estimation. The assumption is that the entire site is re-created in AEM as is.

1.         List down the templates: Identify all the templates in site.
2.         Estimate the templates: Estimate time for creating each template.(Skip the same types, consider only unique ones)
3.         List components: Identify all the identical components to be created.
4.         Estimate the components: Define time for each unique component creation.
5.         Analyze the current CMS content ( XML/JSON Data) : Analyse the content. It may have textual content, metadata, tags etc.
6.         Estimate the scripts for each components (XML/JSON Data to AEM Component): Now estimate time required to migrate the content using any of the content migration approach/ scripts.
7.         Analyse asset migration: Find out how the assets are organised in current system. Find out the ways to move them to AEM.
8.         Estimate asset migration and categorization(Extract and update metadata for digital assets on AEM): Here we need to calculate time required to move entire asset(not duplicates) to AEM.
9.         Estimate Analytics part: Calculate the analytics implementation
10.         Analyse the integrations: Find out all integration points and ways to replicate it in AEM.
11.         Estimate Integration (Login, Authorization, Search): List out the time for integration implementation
12.         Analyse the workflows:Find all the workflows to be created in AEM
13.         Estimate Workflow creation: Estimate time for creating workflows based on the complexity.

      
If the site has to be redesigned, we need to consider the design activities also as part of estimation. We also need to estimate time for,

• Environment setup(dev,qa,prod,dr)
• Testing
• Release configurations & activities
• Additional authoring after the content migration.

Above activities helps to provide a valid estimation for any migration project.

Migrating a CMS website content to AEM? Follow this steps:


Read More:
AEM Integration with DOJO
Analytics Integration with AEM
WCM Use class
AngularJS with AEM
New features in AEM 6.3
HTL Tips

Steps to migrate third party CMS website to AEM

AEM(Adobe Experience Manager) is getting more and more popular, due to its enterprise capability for managing content. There are cases where we need to migrate third party CMS site to AEM.
Some examples could be Drupal to AEM, Salesforce to AEM e.t.c.

Let us understand the common process of migration. I will take you through the steps to migrate any third party CMS websites to AEM.

The estimation part of AEM project migration is given in this link.

Below listed are the major steps in a migration project.

• Analysing the current system with integration elements involved
• Define content strategy
• Define asset Strategy
• Design the new system with integration
• Migrate the content to new system
• Test the new system

Background

While migrating a site, we should have an understanding of the current site CMS; then map it with related elements in AEM.

For eg. A site made in Wordpress will have the content stored in a location and images, videos, pdfs in some repository. Understanding the layers in both CMS plays a big role in delivering a successful migration.

Setting up the environment
To ensure a smooth migration, we need an AEM DEV environment ready where we can quickly move the data from current system. The minimal DEV environment configuration could be just an author instance with 2 to 4 publish instances and a dispatcher.

Strategy to Migrate Content 
Below steps to be carried out for a smooth content migration

•     Content Evaluation
•     Cleaning up/ Sanitizing the content    
•     Content Mapping - Organizing the content hierarchy
•     Design

               - Based on the analysis of existing system, we need to design a solution which has proper
               digital asset structure, metadata, tagging, client library, target AEM templates and
               components

•     Content Migration - There are many ways to do this.

              - Manual Migration(When the content in the old system is not structured)
              - Automation Migration(When the content in the old system is structured)
              - Hybrid Migration(When there is structured and unstructured content in the old system)

•     Content Verification

Assets Strategy
Assets plays an important role in any CMS. We need to carry out,

•     Asset migration and categorization
•     Extract and update metadata from old system to AEM

Getting into action
Based on the design we need to have templates, components created.

We need to identify the tools/ methods available to export data from current system to AEM once the templates and components are ready. AEM follows hybrid way of content migration in almost all scenarios.

REST API for migration
Some of the CMS system provides a REST API layer where the content is exposed. We can invoke them in AEM and get those data exported into AEM directly.

To achieve this, our migration scripts should have,    
   -  Map the templates from current system to AEM
   -  Map the components from current system to AEM

           

 Once the content and assets are migrated, we can start manual testing on the pages by creating new pages as per design.

How do we estimate an AEM Migration project?

•     List templates
•     Estimate the templates
•     List components
•     Estimate the components
•     Analyze the current CMS content ( XML/JSON Data)
•     Estimate the scripts for each components (XML/JSON Data to AEM Component)
•     Estimate asset migration and categorization(Extract and update metadata for digital assets on AEM)
•     Estimate Analytics part
•     Estimate Integration (Login, Authorization, Search)
•     Estimate Workflow creation

 Need help?
If any one facing trouble in identifying the strategy, let us know through the comments section.

Subscribe Our YouTube Channel Here.

Read More:
AEM Integration with DOJO
Analytics Integration with AEM
WCM Use class
AngularJS with AEM
New features in AEM 6.3
HTL Tips