logo

Migration

Is moving to AEM as a Cloud Service a replatform or just an upgrade?

Reviewed by Martin DejnickiFacts verified 19 sources

Short answer

Adobe Experience Manager (AEM) as a Cloud Service is a replatform for your code and operations and an upgrade for your content and authors. Adobe documents the move as a four-phase migration journey (Adobe, October 2026): code moves to an immutable, pipeline-deployed repository, while content and the Touch UI carry over (Adobe, October 2026).

Adobe's migration phases
Readiness, Implementation, Go-Live, Post Go-LiveAdobe calls the move a migration journey and supports it with Cloud Acceleration Manager, the Best Practices Analyzer and the Content Transfer ToolSources: Adobe Experience League (Getting Started with the Migration Journey to AEM as a Cloud Service, Overview to Cloud Acceleration Manager)
Repository at runtime
/apps and /libs are immutableOSGi bundles and configurations deploy only as code through the Cloud Manager pipeline; the Web Console, custom run modes, replication agents and the Classic UI are goneSources: Adobe Experience League (Notable Changes to Adobe Experience Manager as a Cloud Service, AEM Project Structure)
Content transfer
Content Transfer Tool, AEM to AEM onlyExtraction into a migration set, then ingestion into Cloud Service, with differential top-ups; idle migration sets expire after about 45 daysSource: Adobe Experience League (Overview to Content Transfer Tool)
Sites license
Content requests, no published priceOne content request per page view or per five API calls, counted at the first cache, headless calls included; Adobe doesn't publish AEM pricesSources: Adobe Experience League (Understand Cloud Service content requests, License dashboard); Adobe (Adobe Experience Manager Sites)

Deploi’s call

Treat AEM as a Cloud Service as a replatform of your code and operations that keeps your content and authors where they are. Get the Best Practices Analyzer report before anything else: if it lists adjustments, Cloud Service is the smaller rebuild; if it reads like a rewrite, price Sanity beside it as a second rebuild.

UpgradeMove to AEM as a Cloud Service when

  • Authors depend on Adobe Experience Manager (AEM) features that carry over, such as Multi Site Manager blueprints and AEM Assets, so a replatform would rebuild them too.
  • The Best Practices Analyzer report lists adjustments your developers can absorb, because Adobe's goal is a move without rewriting the bulk of custom code.
  • You want Adobe to run infrastructure and updates (monthly features and twice-monthly maintenance as of October 2026), and Adobe's content-request quote fits your traffic.
  • You run 6.5 on Adobe Managed Services, where Adobe's roadmap says 6.5 support ended by 31 August 2026, so you're moving to 6.5 LTS (Long-Term Support) or Cloud Service anyway.

SanityReplatform to Sanity instead when

  • The Best Practices Analyzer report reads like a rewrite, so you're paying for a rebuild either way.
  • Most delivery is headless or app-first, so you'd rather plan against Sanity's published quota of 1 million application programming interface (API) requests a month through its content delivery network (CDN) on Growth, as of October 2026, than an unpublished content-request contract.
  • Your front end is moving to a JavaScript framework, and few authors use Multi Site Manager or the Adobe Experience Cloud integrations.

What changes when AEM 6.5 moves to AEM as a Cloud Service?

Moving Adobe Experience Manager (AEM) 6.5 to AEM as a Cloud Service changes how your code is built, deployed and run, not what your authors edit. It's one of the exits from the AEM 6.5 support deadline, with core support for 6.5 on premises ending 28 February 2027 (Adobe knowledge base, October 2026). Adobe's own change list is the developer's to-do list (Adobe, Notable changes; Adobe, What is New and What is Different, October 2026).

Seven things an AEM 6.5 team does differently on AEM as a Cloud Service
AreaAEM 6.5AEM as a Cloud Service
Code in /apps and /libsChangeable at runtimeImmutable at runtime; changes come from Git
OSGi (Java module framework) bundles and configurationsChanged in the Web ConsoleDeployed as code through the Cloud Manager pipeline
EnvironmentsCustom run modesNo custom run modes
PublishingReplication agentsSling Content Distribution
Authoring interfaceClassic UI or Touch UITouch UI only
Author sign-inYour own setupAdobe IDs, managed in the Adobe Admin Console
UpdatesService packsMonthly features, twice-monthly maintenance
Sources: Adobe Experience League (Notable Changes to Adobe Experience Manager as a Cloud Service, What is New and What is Different, AEM Project Structure, Adobe Experience Manager releases roadmap). As of 24 October 2026.

The Classic UI row is the one authors feel: dialogs still built for it land on the Best Practices Analyzer's list to modernize (Adobe, Best Practices Analyzer, October 2026).

What carries over from AEM 6.5 to AEM as a Cloud Service unchanged?

Your content, page tree and authoring habits carry over from Adobe Experience Manager (AEM) 6.5 to AEM as a Cloud Service. Adobe says the authoring interface's basic principles "will be very familiar" and that, apart from the Classic UI, "the basics remain unchanged" (Adobe, What is New and What is Different, October 2026).

  • Content and groups. Adobe's Content Transfer Tool moves existing content from the 6.5 instance and transfers user groups automatically (Adobe, Content Transfer Tool, October 2026).
  • Multi Site Manager. Blueprints and rollout configurations still work, installed from Git through the pipeline (Adobe, Notable changes, October 2026); page moves and rollouts now run as background jobs (Adobe, Notable changes to AEM Sites, October 2026).
  • AEM Assets. Adobe reworked asset upload, processing and download, which "impacts the existing custom code and some operations" (Adobe, Notable changes, October 2026).
  • Most custom code. Adobe's stated goal is a move "without having to rewrite the bulk of their customized code", though "some adjustments might still be needed" (Adobe, What is New and What is Different, October 2026).

So the content model survives and the delivery machinery around it is new, which is why AEM as a Cloud Service is an upgrade for authors and a replatform for developers. The side-by-side comparison of AEM and Sanity starts from the same split.

How does Adobe move code and content to AEM as a Cloud Service?

Adobe moves an Adobe Experience Manager (AEM) 6.5 site to AEM as a Cloud Service in four phases: Readiness, Implementation, Go-Live and Post Go-Live (Adobe Experience League, October 2026).

Moving AEM 6.5 to AEM as a Cloud Service: the tools Adobe documents, in a typical order (Deploi's reading)

  1. Run the Best Practices Analyzer. Its report lists code to refactor, repository items to move, legacy dialogs to modernize, deployment issues and 6.x features Cloud Service doesn't support (Adobe, Best Practices Analyzer, October 2026).
  2. Plan in Cloud Acceleration Manager. Adobe's cloud application guides your teams from planning to go-live (Adobe, Cloud Acceleration Manager, October 2026).
  3. Restructure the code. Split code and content into separate packages, because /apps and /libs are immutable (Adobe, AEM Project Structure, October 2026).
  4. Transfer the content. The Content Transfer Tool extracts content into a migration set, then ingests it into Cloud Service (Adobe, Content Transfer Tool, October 2026).
  5. Top up before go-live. Run differential top-ups so the final content freeze stays short (Adobe, Content Transfer Tool, October 2026).

Idle migration sets expire after about 45 days of inactivity, though acting on the set extends the expiry (Adobe, Content Transfer Tool, October 2026). The Content Transfer Tool only targets AEM as a Cloud Service; a move to Sanity uses the routes in the AEM to Sanity playbook.

How does the AEM license change on AEM as a Cloud Service?

Adobe Experience Manager (AEM) Sites as a Cloud Service is licensed against content requests, so your traffic becomes a contract line. Four details matter:

  • What counts. One content request per page view or per five API (application programming interface) calls, measured where the first cache receives it (Adobe, License dashboard, October 2026). Requests through AEM's headless APIs "still count as content requests", whether the CDN (content delivery network) cache serves them or not (Adobe, Content requests, October 2026).
  • What also counts. Adobe's content requests page adds that a Page Not Found response returned with status 200 counts as a content request, and that requests from an AI agent that uses a generic browser user agent may count as billable (Adobe, Content requests, October 2026).
  • What it costs. Adobe doesn't publish AEM prices: the AEM Sites page offers a demo, not a price (Adobe, AEM Sites, October 2026).
  • How Sanity compares. Sanity meters requests as well: its Growth plan includes 1 million API CDN requests a month and bills usage above that as overage, as of October 2026 (Sanity pricing; Sanity Docs, Growth plan add-ons; Sanity Docs, Plans and payments, October 2026). Sanity's Growth rates are published, Adobe's are quoted and Sanity's Enterprise pricing is custom, so the two units don't convert.

When is AEM as a Cloud Service the right move?

Adobe Experience Manager (AEM) as a Cloud Service is the right move when the Best Practices Analyzer report reads as a list of adjustments; when it reads like a rewrite, price a replatform beside it. Adobe says the report "speeds up the process of estimating the time and cost" of the move (Adobe, Best Practices Analyzer, October 2026), so it's the document to size both paths from. Cloud Service keeps Multi Site Manager and AEM Assets, with reworked asset handling, and offers deep integration with the Adobe Experience Cloud (Adobe, Notable changes; Adobe, Introduction, October 2026). A replatform to Sanity rebuilds the content model, the import and the front end.

Deploi’s point of view

Where we disagree
The common framing calls Cloud Service an upgrade because the content and the authoring screens come across. For developers it isn't one: the repository rules, the deploy path, the configuration tools, author sign-in and the license model all change. The opposite claim, that Cloud Service is a full rebuild, is wrong too. Adobe's stated goal is a move without rewriting the bulk of custom code, and the analyzer report, not a slogan, says which case you're in.
What this adds
The root names AEM as a Cloud Service as one exit from the 6.5 deadline and mentions its content-request license in one line. This page carries Adobe's change list against what carries over, the Best Practices Analyzer and Content Transfer Tool mechanics, including the 45-day idle expiry of migration sets, and how the content-request license counts page views and API calls.
What we suggest you do first
Get two things before any replatforming talk: the Best Practices Analyzer report, which you run on your 6.5 instance, and a content-request estimate from Adobe. The report sizes the code work, and the content-request count, which includes headless API calls, is the license line nobody can price from a public page.
What we refuse to promise
We won't size an AEM refactor or quote hours for either path from a call: both depend on your own code, and Adobe doesn't publish AEM prices. Cost questions go to a scoping conversation. Our view of AEM rests on Adobe's documentation and public sources.

When this answer changes

  • Adobe publishes one 6.5 LTS end-of-support date across its knowledge base and support matrix
  • Adobe changes how content requests are counted, including the one request per five API calls rule
  • Adobe publishes AEM as a Cloud Service prices
  • Adobe extends AEM 6.5 core support past 28 February 2027
  • The Content Transfer Tool changes its migration set expiry or adds non-AEM targets
  • Sanity changes the Growth plan's included API CDN requests, publishes an AEM migration course or importer, or adds AEM to its MCP server's guided migration paths

Sources

Every source opened and checked on 25 October 2026.

  1. Adobe Experience League, Getting Started with the Migration Journey to AEM as a Cloud Serviceexperienceleague.adobe.com · checked 24 October 2026
  2. Adobe Experience League, Notable Changes to Adobe Experience Manager as a Cloud Serviceexperienceleague.adobe.com · checked 24 October 2026
  3. Adobe Experience League, What is New and What is Differentexperienceleague.adobe.com · checked 24 October 2026
  4. Adobe Experience League, AEM Project Structureexperienceleague.adobe.com · checked 24 October 2026
  5. Adobe Experience League, Overview to Best Practices Analyzerexperienceleague.adobe.com · checked 24 October 2026
  6. Adobe Experience League, Overview to Cloud Acceleration Managerexperienceleague.adobe.com · checked 24 October 2026
  7. Adobe Experience League, Overview to Content Transfer Toolexperienceleague.adobe.com · checked 24 October 2026
  8. Adobe Experience League, Understand Cloud Service content requestsexperienceleague.adobe.com · checked 25 October 2026
  9. Adobe Experience League, License dashboardexperienceleague.adobe.com · checked 24 October 2026
  10. Adobe Experience League, An Introduction to Adobe Experience Manager as a Cloud Serviceexperienceleague.adobe.com · checked 24 October 2026
  11. Adobe Experience League, Adobe Experience Manager releases roadmapexperienceleague.adobe.com · checked 24 October 2026
  12. Adobe, Adobe Experience Manager Sitesbusiness.adobe.com · checked 24 October 2026
  13. Adobe Experience League, AEM 6.5 LTS Frequently Asked Questionsexperienceleague.adobe.com · checked 24 October 2026
  14. Adobe Experience League, AEM 6.5 On-premise support timelines and service pack policyexperienceleague.adobe.com · checked 24 October 2026
  15. Adobe Help Center, Products and technical support periodshelpx.adobe.com · checked 24 October 2026
  16. Adobe Experience League, Notable Changes to AEM Sites as a Cloud Serviceexperienceleague.adobe.com · checked 24 October 2026
  17. Sanity, Plans that scale with yousanity.io · checked 24 October 2026
  18. Sanity Docs, Plans and paymentssanity.io · checked 24 October 2026
  19. Sanity Docs, Extending the Growth plan with paid add-onssanity.io · checked 24 October 2026