Volute earns MASB certification and launches the SightIQ™ Process, raising the standard for how marketing investment gets measured.

Back to Insights

Migrating From AEM to Edge Delivery Services Ahead of the Deadline

Five questions to ask before an AEM 6.5 migration

By Barry Sands

Head of Partnerships, Volute Group

October 13, 2026 - 5 min read

AEM support ends in February 2027. The move to Edge Delivery Services (EDS) is a different kind of project from earlier AEM work.

With the deadline ahead, it helps to know what still applies from AEM and what doesn't. We created WebDeliveryIQ™ with that in mind. It’s Volute Group’s approach to planning and executing EDS migrations. The approach pairs advisory work up front with the migration itself, then adds support after launch. The reasoning is simple. The way you think about the migration determines how it goes, not the tools.

Migrating From AEM to Edge Delivery Services Ahead of the Deadline

It’s Not a Version Bump

When most teams hear “migrate to Edge Delivery Services,” they picture the AEM upgrades they’ve run before, just bigger and more disruptive, with components and templates carried forward and adjusted. But EDS isn’t a newer version of AEM Sites. It’s a different delivery architecture that happens to live under the same Adobe umbrella, and design decisions carried over from that assumption usually create friction later.

Sorting out which instincts still apply and which ones need to be set aside is the first thing we do, before anyone touches code.

What Transfers, What Doesn’t

Content architecture judgment transfers. This means knowing how a site should be structured, how pages relate, and how components get reused. All three matter more in an EDS migration than they do in a typical AEM upgrade, because the source content’s structure largely determines how smoothly it goes.

Most AEM engineering knowledge doesn’t transfer. Sling models, HTL templates, the OSGi service layer, component dialogs, and dispatcher configuration have no direct EDS equivalent. The front end gets rebuilt from scratch, in a stack most front-end developers already know.

The backend engineer who ran the AEM program isn’t automatically the right person to run the EDS one. Their expertise is real, but it’s concentrated in the layer EDS removes. Content structure and authoring requirements determine whether this project goes well, and the people fluent in those areas are FEDs and BSAs. It may feel natural to keep that engineer in place for continuity, but doing so often creates friction in stakeholder reviews later.

We built our team so content and authoring expertise leads. Backend engineering plays a supporting role instead.

The New Division of Labor

Most AEM teams are staffed for the lighter side. We built WebDeliveryIQ™ to cover the heavier one.

EDS is lighter where traditional AEM was heavy. Far less time goes toward OSGi configuration, JCR query tuning, dispatcher rules, Sling performance, and Java dependency management.

Some of that work disappears outright. The heavier side is content schema design, block architecture, authoring governance without dialog constraints, and CDN configuration. The cleanliness of the source content structure matters most of all. A messy source site can survive a new AEM version without issue, because the components hide the clutter. EDS exposes it.

What to Check First

Source content structure is the single biggest determinant of how a migration goes. It's worth auditing before anything else. These are the same questions we start with:

1. Is content consistently structured, or consistently improvised? Pages that follow real patterns map cleanly to blocks. Pages hand-tuned one at a time don’t.

2. Do you know what’s actually live? The microsites, the language copies, and the campaign pages nobody owns are all in scope until proven otherwise.

3. How much of “content” is really component configuration? Logic that lived in dialogs and services has to be rethought as content or as a block, not ported.

4. Who owns authoring governance once the dialogs are gone? Someone has to define the conventions the tooling used to enforce.

5. Are assets accounted for? DAM assets and their references are their own workstream, not a footnote.

The Easier Way to Migrate

WebDeliveryIQ™ pairs the advisory work above with the migration itself, then adds the support model that keeps the site running clean after launch. Our team handles all three phases, so you don’t have to coordinate three separate providers.

The platform treats source-content structuring as part of the work. It scaffolds EDS-native blocks instead of porting server components. It carries the conventions forward, too. You keep your content and your Adobe investment while the delivery layer changes underneath it. We coordinate that work at every phase. Strategy and design stay human. Delivery becomes agentic.

AEM 6.5 reaches the end of support in February 2027, and a lot of teams are still assessing the migration path. Every quarter without a plan makes it more likely that migration happens under deadline pressure instead of on a timeline your team sets. The tooling was never the hard part. WebDeliveryIQ™ lets you migrate on your terms.

About Volute

Volute Group is a customer experience and tech consulting firm focused on helping clients maximize marketing investments they've already made in data, technology, and resources.

Ready for a discussion?

Start a conversation

Website migration, simplified

Discover WebDeliveryIQ