Migrate to AEM Cloud Service Faster - An Agentic Workflow with MCP and Adobe Migration Skills

Every AEM Cloud Service migration hits the same bottleneck: Cloud Acceleration Manager (CAM) and Best Practices Analyzer (BPA) surface hundreds of findings — but turning those findings into code is still manual. Developers interpret reports one at a time, cross-reference documentation, and context-switch constantly between browser, docs, cli-tools, and IDE. The report tells you what's broken. Getting it fixed is still entirely on you.

This session introduces a workflow that closes that gap. The AEM Migration MCP server gives coding assistants structured access to CAM/BPA findings directly inside the IDE. Paired with Adobe migration skills — part of a broader AEM development agent framework — coding assistants act as an agentic migration copilot. The skills encode curated refactoring patterns for common migration issues, enabling the assistant to reason over your project's specific findings and apply targeted, reviewable fixes.

You'll see it end to end, live: connecting via MCP, authenticating through Adobe IMS, pulling findings, and watching the agent produce code changes against a real project.

Early adoption has shown promising results in reducing manual migration effort and improving fix consistency — we'll share what we've observed so far.