Before beginning your transition journey to Cloud Service, you should familiarize yourself with AEM as a Cloud Service and review the notable changes that have been made to it and also review the features that have been replaced or deprecated.
AEM as a Cloud Service brings many new features and possibilities for managing your AEM projects.
However, there are a number of differences between AEM On-premise or in Adobe Managed Services as compared to AEM as a Cloud Service.
Refer to Notable Changes to AEM Cloud Service to understand the important differences.
Adobe constantly evaluates product capabilities, to over time reinvent or replace older features with more modern alternatives to improve overall customer value, always under careful consideration of backward compatibility.
Refer to Deprecated Features to learn more about features and capabilities that have been marked as deprecated in Experience Manager as a Cloud Service.
Understanding the Planning Phase
The following figure showcases key steps involved during the Planning phase:
Assessing Cloud Service Readiness
The first step in the Planning phase is to assess your readiness to move from your existing AEM version to Cloud Service and determine areas that will require refactoring to be compatible with AEM as a Cloud Service.
You will need to do a comprehensive assessment of your current AEM source code against the notable changes and deprecated features to determine the level of effort expected in the transition journey.
You can accelerate the assessment step by running the Cloud Readiness Analyzer (CRA) on your current AEM version. For more details refer to CRA Overview .
If you already have access to Cloud Manager and a Cloud Service environment, it is recommended to run your current code in a Cloud Manager code quality pipeline to assess the required code changes to be compatible with Cloud Service.
Reviewing Resource Planning
Once you have estimated the level of effort that will be required to move to Cloud Service, you should identify resources, create a team, and map out roles and responsibilities for the transition process.
If you have not established Key Performance Indicators (KPIs) previously, it is recommended to establish KPIs for your Adobe Experience Manager (AEM) implementation to help your team focus on what matters the most.
Refer to Developing KPIs to learn how to choose the right KPIs for your business objectives.