What problem does it solve?
Bulk content migration from a traditional CMS to AEM Edge Delivery Services (EDS) is hard because EDS is document-based, so teams must redesign content structure, templates, and query indexing while preserving metadata and SEO.
Core Features & Use Cases
- Source-to-EDS mapping: Analyzes representative pages from AEM, WordPress, Drupal, or other CMSs and maps content types and fields to EDS document conventions (sections, blocks, metadata tables).
- Template and schema generation: Produces complete EDS document templates and a metadata schema aligned to what authors and listing/query views need.
- Query index configuration: Generates
helix-query.yaml rules so listings and search can index migrated metadata reliably.
- Migration execution paths: Provides both manual workflows (small migrations) and scripted workflows (large migrations) including extract/transform/import/validate.
- Post-migration validation: Outputs an EDS-specific validation checklist using
.plain.html to confirm document rendering and head metadata correctness.
Quick Start
Ask an AI agent to plan an 8-step migration by analyzing 5–10 representative source pages, generating the EDS templates and helix-query.yaml, and producing step-by-step author instructions for bulk importing.