We build on Adobe Experience Manager (AEM), upgrade AEM 6.5 to AEM as a Cloud Service, put Next.js frontends on AEM headless content, and migrate sites off AEM to a headless CMS. Most AEM owners who contact us in 2026 ask the same thing: modernise on Adobe’s stack, or leave it?
The 6.5 deadline makes that question urgent. As of October 2026, Adobe’s support page lists core support for AEM 6.5 on premise until February 28, 2027, and extended support, critical fixes only, until February 28, 2028. Adobe’s release roadmap says support for 6.5 on Adobe Managed Services ends by August 31, 2026, and that service pack 6.5.26.0, planned for November 19, 2026, is the last one for 6.5. If you run 6.5, you are choosing a destination this year, planned or not.
What AEM services do we offer?
Most clients need two of the five services below in a row, usually an audit and then an upgrade or a migration.
AEM builds and component development
We build new templates and components on AEM Sites: HTL markup, Sling Models, Content Fragment Models, workflows, and Dispatcher and CDN rules. We connect AEM to Adobe Analytics, Target, search, commerce and CRM. We also take over AEM codebases a previous partner left behind, starting with a code and configuration audit.
Upgrade from AEM 6.5 to AEM as a Cloud Service
AEM as a Cloud Service is Adobe’s cloud native version of AEM. Adobe applies the updates: its roadmap says new features arrive through a monthly feature activation and fixes through maintenance releases twice a month. Code ships through Cloud Manager, Adobe’s CI/CD tool with built in code quality gates.
A 6.5 project does not lift and shift. Custom code that writes to the repository in unsupported ways, old workflow launchers and integrations that assume on premise servers need refactoring before Cloud Manager will deploy them. Our AEM migration services page covers the upgrade path step by step.
Headless frontends on Next.js
AEM can run headless. Information architects define Content Fragment Models, authors fill in Content Fragments, and a frontend reads them over HTTP. Adobe offers two delivery APIs for this: a GraphQL API whose schema comes from your models, and an OpenAPI based REST API that returns JSON and works well behind a CDN. For GraphQL on publish, Adobe recommends persisted queries, because clients call them with GET and the Dispatcher and CDN can cache the response.
We build the frontend on those APIs, usually in Next.js, with preview for authors.
Edge Delivery Services
Edge Delivery Services is Adobe’s newer delivery layer for AEM. Authors work either in the Universal Editor, a visual editor with live preview, or in documents in Microsoft Word and SharePoint, with Google Drive as the alternative. Adobe describes it as replacing AEM Publish and Dispatcher, and it can share a domain with existing AEM Sites pages.
It suits marketing sites that need fast pages and simple authoring. Before we recommend it, we check that your components map onto its block model.
Migration off AEM
When the numbers say leave, we move content, assets and URLs from AEM into a headless CMS such as Payload, Contentful, Sanity, Storyblok or Strapi, and build the new frontend. Our AEM vs headless CMS comparison sets the two options side by side.
If you need people inside your own sprints rather than a project, you can hire AEM developers who know Sling, the JCR repository and Cloud Manager.
Should you stay on AEM or leave it?
Neither answer is right by default. AEM is a suite, so it comes down to how much of the suite you use. These are the signals we check in an audit.
| Signal | Points to staying on AEM | Points to leaving AEM |
|---|---|---|
| Adobe stack | You run Adobe Target, Analytics or other Adobe products, and the integrations already work | AEM is the only Adobe product in use |
| Personalisation | Marketing runs targeted experiences and tests every month | Personalisation was in the business case, but nobody runs it |
| Assets | AEM Assets holds a large library with renditions, rights metadata and approvals | Assets are mostly page images that a CMS media library can hold |
| Authors | Many authors across brands and locales depend on AEM workflows and permissions | A small team publishes a few pages a week and finds the authoring UI heavy |
| Developers | You have, or can hire, Java and AEM specialists | Your engineers work in TypeScript and React and avoid the AEM codebase |
| Contract | Your licence was renewed recently on terms you accept | Renewal is coming up and the renewal price is the trigger for this discussion |
When staying on AEM is right
Stay when AEM does work you would otherwise buy as separate products. If you run Target campaigns, keep a large library in AEM Assets and route content through multi-step approvals, a headless CMS needs extra tools to match that. Complaints about upgrades, servers or slow pages are then cheaper to fix with Cloud Service or Edge Delivery Services than with a replatform.
When leaving AEM is right
Leave when you pay for an enterprise suite and use it as a page CMS. The usual picture: a marketing site with a few dozen templates, personalisation switched off, every copy change waiting for an AEM developer, and a 6.5 deadline that forces a migration anyway. If you would have to move to Cloud Service regardless, price that move against one migration to a headless CMS.
What drives the total cost of owning AEM?
Adobe does not publish AEM Sites prices. As of October 2026, its pricing page describes a core package with add-ons and asks buyers to request a custom quote. We do not quote numbers either, because they depend on your contract. The drivers we model in an audit:
- Licence. The Adobe subscription is usually the largest line. It is negotiated per contract and often bundled with other Adobe products, so AEM’s own share is hard to see.
- Specialist developers. AEM work needs Java, OSGi, Apache Sling, the JCR repository, HTL and Dispatcher configuration. The pool of engineers with that mix is smaller than for React and TypeScript, which shows up in hiring time and rates.
- Infrastructure. On premise or on Adobe Managed Services, you pay for author, publish and Dispatcher servers and the people who patch them. On Cloud Service, hosting is in the subscription, but environments and CDN setup still cost time.
- Release cycle. On 6.5, service packs and upgrades are projects of their own. On Cloud Service, your code has to keep pace with Adobe’s monthly updates, and every deploy goes through the Cloud Manager quality gates.
- Partner and support contracts. Many AEM sites depend on one implementation partner on a retainer, and that cost rarely shows up in the licence discussion.
A headless CMS moves these costs around. The licence gets smaller or disappears, and you take on the frontend, hosting and integrations.
How does a migration off AEM run?
We run every migration off AEM in six steps, and we keep the first two even when the renewal date is close.
- Content, URL and integration audit. We export every page, Content Fragment, Experience Fragment and asset path, plus the vanity URLs and Dispatcher rewrite rules. We mark which pages rank, which get traffic and which can go.
- Content model and platform choice. AEM pages are trees of components. We turn the components that matter into structured content types and blocks in the new CMS, and that model usually settles which platform fits. You sign off on both before we build.
- Build the CMS and the frontend. We set up roles and approval states that match the AEM workflows your authors use, and build the frontend against real migrated content.
- Scripted content and asset migration. We read content through AEM’s APIs and content packages and normalise it into the new schema. The scripts can rerun, so mapping errors get fixed in code. Assets move with their metadata or stay in AEM Assets.
- Redirects, SEO parity and cutover. Every legacy URL, vanity URLs and Dispatcher rewrites included, maps to a new URL or keeps its path. Titles, descriptions, canonicals and structured data carry over, and we compare old and new page by page.
- Parallel run and handover. On large estates both platforms run side by side until authors trust the new one. Then we train authors and document the model and deployment for your developers.
Our headless CMS migration checklist lists every check we run at steps 4 and 5.
Replatform work we can show
We have no published AEM case study yet. The two projects below are our closest replatform work. Both are anonymized, and the figures come from our case studies.
A European enterprise healthtech organization: Drupal 7 to Payload and Next.js
Drupal 7 reached end of life, so the deadline was fixed, as it is for AEM 6.5 now. The site carried over 1,200 content nodes in four languages. We moved it to Payload with a Next.js frontend. LCP fell from 4.3s to 1.5s, editor publish time dropped by roughly half, and there were no SEO ranking regressions at cutover. Read the Drupal replatform case study.
A US-based enterprise multi-brand retail group: five CMSs into one
Five brands ran five legacy CMSs, and editors published the same campaign four or five times. We built one Payload backend that serves Next.js storefronts, React Native apps and in-store screens through a single API, and ran both systems in parallel for six weeks. Average publish time fell by about 65%, and seasonal campaigns launch roughly four times faster. Read the omnichannel retail case study.
How we work on AEM projects
We start with an audit. You get a written scope, a price and one recommendation: upgrade, add Edge Delivery Services, go headless on AEM, or leave. We work on AEM and on five headless platforms, so we gain nothing from pushing you off Adobe, and sometimes we tell clients to stay. The senior engineers who scope the work also build it. If the answer is to leave, our headless CMS agency page explains how we run those builds.
Talk to us about your AEM estate
Book a discovery call and tell us which AEM version you run, how many sites sit on it and when the contract renews.