Migrating to Adobe Cloud Service from AWS or On-Premise
Moving to Adobe Cloud Service, or AEM as a Cloud Service from your current Adobe Experience Manager setup is a tough decision. There are many business and technology factors that you will want to consider before taking the leap and sometimes Adobe’s marketing and sales do not provide all of the information required to make an informed decision.
There are a handful of topics that need to be investigated before you make the move to Cloud Services from AEM.
- Review any Custom Services
- Existing Environment Review
- Code Compatibility Review and Upgrade
- Content Migration
- Cloud Infrastructure
- Legacy Content Review & Purge
- Review Content Hierarchy
- Adobe Marketing Cloud and External Services
- AEM Services and Bundles
- AEM Assets Microservices
Are you ready to move to AEM as a Cloud Service?
The answer to this question varies between every organization using AEM. You can work through Adobe’s Cloud Readiness tool to test your readiness for the move to the new configuration.
This tool will check if your system is using Adobe’s best practices to prepare you for the migration. However, keep in mind that this tool is limited and will not tell the entire story. Contact us if your organization is looking for additional guidance, and our Adobe Experience Manager Architects and Experts can review your AEM Cloud readiness.
Is it worth moving to Cloud Service?
Benefits of Moving to Adobe’s Cloud Service
- AEM CS has a potentially lower cost of ownership
- Your CMS will always be up-to-date and you will work with the most recent innovation offered by the tool
- AEM as a Cloud Service offers seamless daily maintenance updates and monthly feature updates
- AEM as a Cloud Service provides a scalable, secure, and agile Digital Experience Platform
Drawbacks of Moving to Adobe’s Cloud Service
- Cost of migrating to AEM Cloud
- Custom Components and Solutions might not be compatible with AEM as a Cloud Service
- Adobe is in control of your AEM platform data and management
- Some features that are available on AEM 6.5 are not available on the new platform
Final Thoughts
The development of content management systems is constantly evolving. You do not want your organization to get stuck on a legacy, or outdated version of AEM. If you have more detailed questions about the process please reach out to us, we are happy to help!
About The Author
Hank Thobe
Business Director at Arbory Digital
Technical Project Manager and Business Director leading and supporting AEM experts to provide high-quality services and solutions for various industries and sectors.