Using Agentic AI and AI Tools to Migrate Content to AEM

There are several ways to approach migrating content to AEM. We would love to get some clarity and “demystification” about the various approaches that are out there, what’s mature for production use, and what is in the works. Here are a few:

1. What we understand as formerly known as Experience Catalyst, there is the Modernization Agent to assist in migrating sites to Edge Delivery Services. Given the documentation, this looks to be the more mature approach.
2. An Experience Modernization Console provides natural language methods to do migrations. This is also available with documentation on Experience League. Is this mature enough for production use? Is the use of the Adobe Outcome Engineer model sufficient for complex migration tasks? Has anyone tried?
3. Since MCP is available for AEM, this opens up the door to multiple approaches of working with content in AEM. I’m probably most excited about this one, but it still raises questions: Are there best practices here? Would this be more of a way to query your AEM content, or use it for true migration?

I would love to hear the community’s thoughts on this. Better yet, I’d love to have this as a topic of discussion for an upcoming AEM User Group Meeting with the Midwest Chapter, which I’d be happy to schedule and coordinate. 

Thanks all!