A Step-by-Step Approach for Migrating to AEMaaCS
AEM as a Cloud Service (AEMaaCS) is Adobe's software-as-a-service (SaaS) version of Adobe Experience Manager (AEM), which provides clients with a CMS platform (Sites), Digital Asset Management (DAM, or simply Assets), and Forms. It was released a few years ago with several upsides and a few downsides. In the intervening years, Adobe has continued to build on the pros while the cons continue to dwindle. Some fairly large companies have been enticed with licensing discounts and package deals to embrace CS and migrate their AEM instances to it. We have helped a few of our clients with this journey and some are now live on CS. This post briefly describes the key steps involved in such a migration. Assess Current State The migration from on-premise (data center) or cloud-hosted to CS is not a lift-and-shift. Significant refactoring is required in order to make your AEM implementation ready for CS. Additionally, it's a great opportunity to modernize and clear off technical debt. A