In this part of the journey, you will learn how to plan and perform the migration once both the code and the content are ready to be moved over to AEM as a Cloud Service. Additionally, you will learn what are the best practices and known limitations when performing the migration.
In the previous phases of the journey:
This document will help you understand how to perform the migration to AEM as a Cloud Service once you are familiar with the previous steps of the journey. You will learn how to perform the initial production migration as well as the best practices to follow when migrating to AEM as a Cloud Service.
Initiate the migration from production based on the experience you gained during the AEM as a Cloud Service stage migration performed on clones:
Validate the content ingested into both the AEM as a Cloud Service author and publish tiers.
Instruct the content authoring team to avoid moving content on both source and destination until the ingestion is complete
New content ca be added, edited, or deleted but avoid moving it. This applies both to source and destination.
Record the time taken for full extraction and ingestion to have an estimate for future top-up migration timelines.
Create a migration planner for both author and publish.
After the initial migration from production you must perform incremental top-ups to make sure your bring your content up to date on the cloud instance. Because of this, it is recommended you follow these best practices:
As mentioned previously, you will have to schedule a code and content freeze period. Use the following questions to help you plan the freeze period:
To answer the first question, you should consider the time it has taken to perform trial runs in non-production environments. To answer the second question, you need close collaboration between the team who is adding new features and the team refactoring the code. The goal should be to make sure all the code that is added to the existing deployment is also added, tested, and deployed to the cloud services branch. Generally speaking, this means that the amount of code freeze will be lower.
Additionally, you need to plan for a content freeze when the final content top-up is scheduled.
When planning or performing the migration, you should consider the following guidelines:
Content Transfer Tool best practices
Make sure that when going live, you run the content migration on production instead of a clone. A good approach is to use AZCopy for the initial migration and then run top up extractions frequently (even daily) to extract smaller chunks and to avoid any long-term load on the source AEM.
When performing the production migration you should avoid running the Content Transfer Tool from a clone because:
Optimizing the load on your AEM source while performing the content migration
Remember, the load on the AEM source will be greater during the extraction phase. You should be aware that:
Please take into account that the entire ingestion fails if any of the following limitations are found as part of the extracted migration set:
rep:AuthorizableIDbeing ingested that is already present on AEM as a Cloud Service
Compared to the section above the ingestion does not fail due to the following asset concerns. However, it is highly recommended you take the appropriate steps in these scenarios:
Both of the above items will be identified and reported in the Best Practice Analyzer report.
Please review the list of activities presented below to ensure that you can perform a smooth and successful migration:
You can always reference the list in case you need to recalibrate your tasks while performing the migration.
Once you understand how to perform the migration to AEM as a Cloud Service, you can check the Post-Go-Live page to keep your instance running smoothly.