A QA tool for AEM to Edge Delivery Services migrations

Moving a site from AEM Sites to Adobe Edge Delivery Services is mostly a content and quality problem, not a coding problem. Hundreds or thousands of pages have to arrive with the same content, metadata and links, and every old URL needs a working redirect. Today most of that checking is manual.

What problem would the tool solve?

During a migration, teams need to know which pages are missing, which lost content or metadata on the way, which links now point nowhere, and whether the new pages are actually faster. Checking this by hand is slow, and spot checks miss the long tail of pages that matter for search.

What would it do?

The first version we have in mind would:

• crawl the old and the new site and pair up matching pages
• compare visible content, titles, descriptions, canonical tags and structured data
• check that every old URL redirects to the right new one
• flag broken internal links and missing images
• compare lab performance metrics for each page pair
• produce a report the migration team can work through, page by page

Where does the idea come from?

It comes from our own AEM delivery work, where migration QA keeps landing in spreadsheets and manual checks. We have not built it yet. Right now we are talking to teams who have done a migration or are planning one, to find out which checks matter most.

How can you help?

If you are planning a move to Edge Delivery Services, or have done one, we would like to hear what went wrong and what you wish you had checked. Send us a note or join the Lab list below to hear when we start building.