AEM Edge Delivery Services Migration Checklist
A practical AEM EDS migration checklist covering content inventory, blocks, authoring, redirects, integrations, performance, and phased rollout.
On this page
Migrating to AEM Edge Delivery Services is a content, authoring, and delivery transformation rather than a direct component translation. A pilot should reveal which patterns simplify the site and which integrations need a different boundary.
#Inventory before coding
List templates, blocks, metadata, media, redirects, analytics, search, personalization, forms, and external integrations. Identify high-value pages and pages that can be retired or simplified.
#Choose the authoring model
Decide where authors will work: documents, spreadsheets, SharePoint, Google Drive, Universal Editor, or a combination. Define section boundaries, block tables, metadata names, permissions, preview, approval, and publishing rules.
#Design blocks around contracts
A block should have a small authored input contract and produce semantic, accessible markup. Document missing-value behavior, responsive rules, keyboard interaction, and any dependency on an external service.
#Plan content and URLs
Preserve meaningful URLs where possible, create a redirect map, audit internal links, and keep titles, descriptions, social metadata, and indexing behavior. Migrate representative content, not only ideal fixtures.
#Validate performance and operations
Measure Core Web Vitals, accessibility, SEO, author effort, error handling, and media behavior. Document code deployment, content publishing, ownership, monitoring, rollback, and coexistence with the old system.
#Common migration mistakes
Translating every old component one-for-one.
Choosing a block contract without real authored content.
Ignoring redirects and metadata.
Moving sensitive integrations into browser code.
Scaling before the pilot has measurable results.
#Frequently asked questions
#Should an entire site migrate at once?
Usually a staged migration provides better evidence and a safer rollback path.
#Does EDS guarantee performance?
No. Images, blocks, third-party code, and content still determine the measured experience.
#Conclusion
A successful EDS migration starts with content and authoring decisions, then proves them with a representative pilot. Inventory carefully, design narrow blocks, preserve URLs and metadata, measure the real experience, and scale only after the operating model is clear.