How to migrate your infrastructure to AEM as a Cloud Service

Credera’s Adobe specialists have unparalleled experience in Adobe Experience Manager (AEM) migrations and implementations, as evidenced by our being one of the select few companies to have earned Adobe’s highest partner status, Adobe Global Platinum Solution Partner.

We leverage that knowledge and experience to ensure smooth, successful transitions to new strategic platforms for our clients, including AEM as a Cloud Service, the next-generation platform to build and serve experiences using AEM.

Here we’ll outline our step-by-step approach to that migration.

Step 1: Initial assessment and planning

Evaluate current instances

• Conduct a thorough assessment of your current AEM setup, including versions, customizations, integrations, and content.

• Identify any dependencies and third-party integrations that need to be addressed.

Create a migration plan

• Develop a detailed migration plan that outlines the scope, timeline, resources, and key milestones.

Key tools: Best Practices Analyzer, Cloud Acceleration Manager

Step 2: Preparation

Set up development and testing environments

• Provision development and testing environments in AEM as a Cloud Service to begin the migration process.

Review and update custom code

• Review existing custom code and components to ensure compatibility with AEM as a Cloud Service.

• Refactor or rewrite any customizations that are not compatible. A few examples include:

  • Custom run modes are not supported in AEM as a Cloud Service.

  • Custom log files are not supported; however, custom log statements are recorded exclusively in the error.log.

  • Apart from the “/home” folder on the publish tier, direct changes to publish repository are not allowed.

  • OSGi configuration changes must be managed through code and deployed via the CI/CD pipeline.

Content inventory and cleanup

• Perform a content inventory to identify outdated or redundant content.

• Clean up and archive unnecessary content to streamline the migration process.

Key tools: Best Practices Analyzer, Repository Modernizer, AEM Modernization Tools, Cloud Manager

A few changed and deprecated features to note:

• Asset Manager APIs 

• Non-availability of DAM Update Asset Workflow and introduction of Processing Profiles 

• Immutable vs mutable content 

• Changes to Publish Repository 

• Long-running jobs 

• File IO / disk usage 

• Custom Run modes 

• Token-based authentication and integration strategies 

• Some maintenance tasks are not configurable 

• CRXDE Lite access 

• Built-in CDN and Get your own CDN 

• Content indexing 

• Cloud Manager Pipeline Execution for deployment

Step 3: Migration execution

Content and asset migration

• Use AEM’s migration tools to migrate content and digital assets to the cloud environment. 

• Validate the migrated content to ensure accuracy and completeness.

Configuration and code migration

• Migrate configurations, templates, and custom components to the cloud environment.

• Test customizations to ensure they work correctly in the new environment.

Integration migration 

• Migrate and configure integrations with third-party systems, such as CRM, analytics, and marketing automation platforms. 

• Test integrations to ensure seamless data flow and functionality. 

  • If there is a server-side integration from AEM to an external server that is protected by IP based firewall, plan for setting up a dedicated egress IP for AEMaaCS

Key tools: Content Transfer Tool, Cloud Manager, Admin Console

Step 4: Testing and validation

Functional testing

• Conduct comprehensive functional testing to ensure all features and functionalities work as expected.

• Involve content authors and business users in testing to gather feedback and identify any issues.

Performance testing 

• Conduct performance testing to ensure the cloud environment meets performance and scalability requirements. 

• Identify and resolve any performance bottlenecks.

Security testing 

• Conduct security testing to ensure the cloud environment is secure and compliant with data protection regulations. 

• Address any security vulnerabilities identified during testing.

Step 5: Training and change management

User training 

• Provide training sessions for content authors, administrators, and other users to familiarize them with the new environment. 

• Create documentation and training materials to support ongoing learning.

Change management 

• Implement change management strategies to ensure a smooth transition for all users. 

• Communicate the benefits and changes associated with the migration to all stakeholders.

Step 6: Go-live and post-migration support 

Go-live preparation 

• Plan and execute the go-live process, including final data migration, cutover activities, and user communication. 

• Perform a final round of testing to ensure everything is ready for production. 

Monitoring and support 

• Monitor the cloud environment closely after go-live to quickly identify and resolve any issues. 

• Provide ongoing support to users and address any post-migration concerns.

Continuous improvement

• Gather feedback from users and stakeholders to identify areas for improvement. 

• Continuously optimize and enhance the AEM as a Cloud Service environment based on feedback and evolving business needs.

Key Tools: Cloud Manager, New Relic, Admin Console

The bottom line

By following this step-by-step plan, you can ensure a successful upgrade to AEM as a Cloud Service. Proper planning, thorough testing, and effective change management are key to a smooth transition and maximizing the benefits of the cloud environment.

• B2b
• B2c
• D2C
• Marketing Technology
• Adobe Campaign
• Adobe Target
• Adobe Experience Cloud
• Adobe
• Adobe Experience Manager
• AEM
• Cloud Services
• Content Management