Moving AEM Code to the Cloud with AI: The Cloud Migration Skill, the Cloud Migration MCP, and the Best Practices Analyzer
Moving to AEM as a Cloud Service means reworking Java code, OSGi configurations, Dispatcher setup, and legacy UI, not just content. Adobe documents an agent-based toolset for this: the Best Practices Analyzer’s findings, a hosted Cloud Migration MCP that pulls them from Cloud Acceleration Manager, and a Migration Skill that writes a read-only runbook first, then works one pattern per session in batches of five with a review pause after each. This post covers how the pieces fit, what patterns are named, and what Adobe’s pages leave out: maturity labels, accuracy guarantees, rollback guidance, and MCP data handling.




