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.
wolf
Any plan to have critical BPA recommendations to be implementable on AMS well, to avoid the need to create major differences in the code setup for AMS and AEMaaCS?
Himani chauhan
We do not have this in the roadmap yet but their is a workaround you can use. So the skills repo has expert skill for each of the pattern that we listed and the migration skill orchestrates it via MCP. For your use case: 1. Install the aem-cloud-service skill 2. you can give the agent a local BPA report or provide path to the files directly and the agent can use the expert skills to fix them.
Tad Reeves
What does the process look like internally for vetting & flagging to the models & skills when a certain migration or implementation pattern is GENUINELY IMPORTANT (like the scheduler example you gave) rather than being transient, general documentation? Is that something the community can influence?
bharat
What we prioritize: patterns that show up repeatedly in BPA reports across customers — high frequency + high impact (like scheduler) gets priority How we vet: we build the skills from Adobe best practices and internal AEMaaCS knowledge, then test them on different complex projects to confirm they actually work. Community influence: yes — the repo is Open Development. Anyone can raise an issue or PR (external contributors sign the Adobe CLA once). Same vetting applies.
Thomas
Is there a way to influence the resulting code, for example by using well-kown solutions like ac tool, wcm.io or even acs commons?
Himani chauhan
You can add those preferences as context when invoking the skill. If it’s a recommendation that applies across projects, you can contribute it to the adobe/skills repo, where the skill owners can review and potentially merge it into the skill.
Ramon
Any plans for Adobe to support a fully automated migration instead of providing a BPA report? ;-)
bharat
BPA stays as the auditable discovery layer for now, but yes — we're already moving in that direction. Several flows work today without BPA: dispatcher conversion, OSGi → Cloud Manager, template modernization, vault package dependencies, htlLint. Expect that list to keep growing as we build more workspace-scan and converter-driven paths on top of the skills.
angela
Any plans to make the migration developer-free? I.e. allow anyone to run the initial steps without ide or installing a sny skills?
Himani chauhan
We have been exploring options of getting this addressed via coworker and another option toward a more guided, web-based experience. That’s still in exploration though and we are yet to decide which direction we would proceed based on the results.
TamalB
What challenges one can face running the same demo in AEM 6.5? Any already known limitations?
Himani chauhan
The current workflow is designed for AEMaaCS migration. Although the skills for each of the patterns can be used in the IDE to provide the correct fix recipe to the agent. Please refer to wolf’s question in the chat where I’ve added some steps for this workaround.
jack.jin
How are we testing adobes skills with evals? I see evals in Adobe repos but don’t quite understand them
Himani chauhan
Evals are basically tests for agent behavior. We give the skill realistic tasks and expectations for what good behavior looks like, then measure how well the agent performs with the skill versus without it. So rather than testing code, we’re testing whether the skill actually improves the agent’s outcome.