As digital ecosystems evolve, many organizations are considering a move to Adobe Experience Manager (AEM) Cloud Services. While the AEM Cloud offers significant benefits, concerns around licensing, costs, and technical risks remain prevalent. iCrossing has been at the forefront of helping enterprises navigate these challenges, and our recent experience with a global manufacturing client offers valuable insights for organizations in a similar situation.  

Client Background and Project Goals 

Our client, a leading global manufacturing company, manages hundreds of digital web domains and countless digital assets across a complex digital experience and commerce platform. Faced with increasing operational costs, scalability challenges, and the need for improved performance, the client sought to migrate from AEM Managed Services to AEM Cloud Services. This migration was designed to enhance scalability, reduce operational expenses, and future-proof the company’s digital infrastructure. 

However, the migration process was daunting. The client was concerned about potential disruptions to their digital ecosystem, the compatibility of legacy code, and the complexities introduced by multi-tenancy. Our mission was to assess these challenges, mitigate risks, and ensure a smooth and successful migration. 

Challenges in Migrating to AEM Cloud Services 

1. Code Readiness

The client's legacy code, developed over many years, posed compatibility issues with current cloud standards. A comprehensive review was needed to identify code that required refactoring or retirement. Ensuring that the codebase met the cloud’s supported coding standards was essential to avoid disruptions during migration. 

2. Configuration Changes

In AEM Cloud Services, many configurations are handled differently.  For example, infrastructure configurations must be converted from XML to JSON formats and project structures required refactoring references. A thorough analysis of the new technical archetype was required to ensure a seamless transition. 

3. Operational Reallocation

Post-migration, deployment processes, code standards enforcement, and production issue management would shift from the Managed Service Provider (MSP) to Adobe's cloud services. This required careful planning to avoid operational inefficiencies and redundancies, and to redefine roles and responsibilities. 

4. Multi-Tenancy Complexities

The move to a single codebase per program in AEM Cloud Services introduced challenges in managing multiple code bases and environments. Multi-tenancy would require the integration of different code bases into a single repository, complicating both team workflows and digital experiences. 

5. Cost Management of Redundant Infrastructure

The client's digital ecosystem included critical components such as enterprise caching and Content Delivery Network (CDN) strategies that could hinder the adoption of AEM Cloud Services’ caching approach. Addressing these challenges was crucial to realizing cost savings. 

Solution Approach 

 To address these challenges, iCrossing developed a structured plan that focused on thorough preparation, testing, and phased execution. 

1. Preparation Phase

• Best Practice Analyzer: We utilized Adobe’s analyzer tool to identify critical issues within the codebase. While critical issues were addressed immediately, lower-priority findings were deferred to reduce the level of effort required. 

• Code Review: The team evaluated, deprecated, and modernized legacy code to align with current cloud standards. This included removing unused code, which helped reduce technical debt and streamline the migration process. 

2. Configuration Changes

• Conversion: Configuration files were updated from XML to JSON, and project archetypes were adapted to meet cloud standards. 

• Manual Adjustments: While Adobe’s migration tools were helpful, some manual adjustments were necessary to complete the configuration updates, ensuring all gaps and errors were addressed. 

• Secret Key Management: We transitioned the management of sensitive information from encrypted OSGi configurations to AEM Cloud Manager's centralized system, enhancing security and compliance through fine-grained access control and audit logs. 

3. Development Adjustments

• Client-Side Library Updates: Client-side libraries were updated to meet the latest standards required by AEM Cloud Services, ensuring compatibility and reducing technical debt. 

• Local Environment Configuration: The supported Maven archetype and local environment configurations were reestablished to mirror cloud requirements, ensuring consistency across development environments. 

4. Execution of Migration

• Tool Utilization: Adobe’s migration tools facilitated a smooth conversion process, but manual steps were also necessary to address gaps and errors. 

• Thorough Testing: Comprehensive testing, including a 45-minute stress test, was conducted to ensure the servers could handle increased loads and scale automatically. Performance tests revealed significant improvements in scalability and efficiency. 

5. Operational Transition

• SLA Realignment: Responsibilities were reallocated from the MSP to Adobe, focusing on cloud-specific roles and reducing redundancy. This realignment was critical to streamlining operations and managing costs effectively. 

• Enterprise Architecture Changes: Modifications were made to caching solutions, integrations with enterprise systems, and digital asset management processes to optimize resource usage and manage operational costs. 

 Lessons Learned for Multi-Tenancy Solutions 

One of the key takeaways from this migration was the complexity of managing multi-tenancy within AEM Cloud Services. By design, Adobe deploys a single codebase per program, which complicates the management of tenants with different functionalities or development teams. 

• Integration of Multiple Code Bases: Teams combined code bases and identified common components for shared use. DevOps teams developed pipelines to automate the consolidation of code bases into a single repository, allowing each team to work independently while ensuring unified deployment. 

• Pipeline Development: Automated consolidation processes were established to ensure seamless integration and operation within the Adobe cloud environment. 

• Feasibility: Despite Adobe’s discouragement of certain multi-tenancy practices, our team successfully configured the environment to support multiple code bases within a single program, with validation from Adobe engineers to ensure compliance with best practices. 

 The migration from AEM Managed Services to AEM Cloud Services was a strategic initiative that significantly improved the client's operational efficiency, reduced costs, and enhanced performance. By conducting thorough readiness assessments, modifying configurations, managing multi-tenancy complexities, and implementing cost management strategies, the client experienced a seamless transition that positioned them for future growth. 

These learnings offer a valuable roadmap for organizations planning similar migrations, showcasing best practices and the importance of meticulous planning and execution in achieving a successful implementation. 

Ready to transform your digital experience and unlock new levels of efficiency? Contact us today to explore how iCrossing can guide your migration to Adobe Experience Manager Cloud Services and drive your business forward.