Adobe Global Community

Migrating AEM Content with Groovy

Published on by Dan Klco on
Migrating content into AEM is nobody’s idea if fun. Creating experiences and authoring content in the powerful AEM authoring experience is great, but identifying, classifying and mapping legacy content? Not so much. AEM’s repository structure contributes to this challenge. AEM, being based on the Java Content Repository (JCR) offers a massively more flexible content taxonomy than relational-based repositories, however, paraphrasing Uncle Ben, with great flexibility, comes great mapping efforts



comments powered by Disqus

Get Insights from the AGC!

Related Posts