AEM 6.5 EOL: Upgrade, Migrate, or Wait—What’s the Smart Move? | Community
Skip to main content
Shashi_Mulugu
Community Advisor
Community Advisor
September 4, 2025

AEM 6.5 EOL: Upgrade, Migrate, or Wait—What’s the Smart Move?

  • September 4, 2025
  • 10 replies
  • 5412 views

Hey Adobe community,

With AEM 6.5 heading towards End of Life (core support ends Feb 2027, extended support Feb 2028), a lot of us are asking: What’s next? Should we stick with Long-Term Support (LTS) or take the leap to AEM Cloud?

Let’s dig into the real questions:

  • Why Upgrade?
    Is it just about staying supported, or are there real benefits to moving forward?

  • LTS vs. Cloud: Pros and Cons
    What’s working for you with LTS? What’s tempting about Cloud? Any pain points or unexpected wins?

  • Who Should Go Where?
    Are there certain teams, industries, or use cases that make more sense for LTS or Cloud? How do you decide?

  • End-State Business Value
    What does success look like after the upgrade or migration? How do you measure the impact on your business or clients?

Share your experiences, opinions, and advice—whether you’re deep in migration planning or just starting to think about it. Let’s help each other figure out the smartest path forward!

10 replies

daniel-strmecki
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
September 4, 2025

Hi @shashi_mulugu,

I don't see any point in waiting if AEM is your long-term CMS choice. I've been using AEMaaCS for 5+ years now, and I would never like to work with on-prem again, unless I really need to.🙂 Let's dig into your questions:

  • Why Upgrade?
    Besides missing out on Adobe innovation, there are several real benefits of moving to AEMaaCS. There is almost no DevOps effort, and we manage it fully in the Dev team. Integration with GitHub is great, and all you need are a few GitHub Actions. We had zero downtime for 5 years on AEMaaCS. There is a straightforward process for moving content between instances, as well as restoring production content. The OOTB CDN is much better now and more configurable. Basically, AEMaaCS is a very mature product; I see no reason to wait.

  • LTS vs. Cloud: Pros and Cons
    Besides the migration effort, I see no other cons with moving to the Cloud. Remember that after that initial migration effort, there will never by any migration, you are constantly up-to-date. 

  • Who Should Go Where?
    The only reason I would recommend on-prem is for industries with regulatory requirements like banking, healthcare, and government, which may have data residency or compliance mandates that prohibit storing content in Adobe’s cloud.

  • End-State Business Value
    You can measure many things, like downtime, backend performance, the number of support tickets, costs for the DevOps team and infrastructure, and costs for the upgrade efforts... Remember that author tier also scales on AEMaaCS.

Check out my blog where I share my thought on this and related topics: https://meticulous.digital/blog/f/what-aem-upgrades-to-prioritise-in-2025 

 

Good luck,

Daniel

Shashi_Mulugu
Community Advisor
Community Advisor
September 4, 2025

Thank you @daniel-strmecki . This is insightful.

arunpatidar
Community Advisor
Community Advisor
September 5, 2025
Shashi_Mulugu
Community Advisor
Community Advisor
September 5, 2025

Thanks for sharing it here @arunpatidar . It consists of great discussions on why upgrade to AEM 6.5 LTS. But if a org is doesnt have any on-prem restrictions what should be there motivation behind choosing LTS vs AEM cloud? To play safe goto AEM LTS or To get new GEnAI features goto AEM cloud?

mlaraadobe
Adobe Employee
Adobe Employee
September 5, 2025

AEMaaCS today is a mature, cloud-native enterprise CMS. With Edge Delivery, extension points, and constant innovation, waiting will only put you behind. For anyone not strictly bound to compliance requirements forcing an on-prem model, Cloud is the clear path forward.

If anyone wants more migration tooling info, check out Cloud Acceleration Manager for a guided planning and migration process.

Has anyone migrated recently or been using new features? Want to share your story? happy to dig deeper!

Shashi_Mulugu
Community Advisor
Community Advisor
September 5, 2025

thanks for your input and opinion here @mlaraadobe .

EstebanBustamante
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
September 5, 2025

I completely agree with @daniel-strmecki — if an upgrade is already on your roadmap, moving to the Cloud is the best path forward. That’s where Adobe is investing most of its effort, and the platform has matured significantly. Even for sensitive data, AEMaaCS is now well equipped (for example, it already offers HIPAA certifications) and will continue to evolve. Like with any trade-off, my recommendation would be to prioritize Cloud over on-prem whenever possible.

 

That said, I’d like to comment on the idea of “End-State Business Value.” This is a tricky one because it really depends on what your client considers valuable. For some, zero downtime is already a major win; for others, reducing DevOps overhead is the key driver. In many cases though, these benefits may feel less relevant because “it’s managed anyway.” Instead, factors like performance, SEO, or integration with MarTech products often take precedence. AEMaaCS supports all of these, but the actual value depends on the implementation approach — whether EDS, headless, or traditional. So while Cloud is always the right foundation, the way you architect within the Cloud ultimately determines the real business value for your customers IMHO.

 

Cheers!

Esteban Bustamante
Shashi_Mulugu
Community Advisor
Community Advisor
September 9, 2025

Thanks @estebanbustamante for the insights and yes you covered most of the important considerations.

 

If client is in Adobe Experience suite it might make sense but if a client is on custom infra and looking at AEM as Content repository,  I am not sure how much it make sense to move to cloud.

Lokesh_Vajrala
Community Advisor
Community Advisor
September 8, 2025

Really good points raised here! I’d also call out the license costs. Since pricing isn’t public and can vary by org usage, availability, and other factors, I often wonder if the move to Cloud Service truly justifies the spend — especially for organizations not leveraging MarTech integrations, GenUI, or managing large volumes of marketing content, where an on-prem LTS upgrade might make more sense. Curious how others see this — do you find the ROI in those cases?

Shashi_Mulugu
Community Advisor
Community Advisor
September 9, 2025

100% @lokesh_vajrala you are bang on.

 

I somehow align with your thoughts. Finding ROI is very hard.

Shashi_Mulugu
Community Advisor
Community Advisor
September 9, 2025

@santoshsai @aanchal-sikka @rohan_garg @joerghoh @briankasingli @vaibhav_mathur Request you to post your opinion here.

September 13, 2025

Upgrade might be suitable for most of the customers who does not have specific requirement for the server/data to be hosted in house,but that does not mean everyone should be choosing it, there would be good number of customers who would still choose LTS for variety of reasons such as data residency , blue/green server for new product launches or protected content , complex architecture which is not supported by cloud.

 

Good thing that Adobe maintains LTS as they foresee lot of customer using it. 

 

Shashi_Mulugu
Community Advisor
Community Advisor
September 15, 2025

Thank you @ashfaq-ali for your insights. Yep complex architecture is a key derivative here. 

Rohan_Garg
Community Advisor
Community Advisor
September 15, 2025

For most of the business cases jumping to AEM Cloud makes sense. If your use case is the standard WCM + DAM where you want elasticity, zero downtime upgrades, built-in CDN and no low-level tweaks, Cloud is usually the better bet.

Other than our government clients who use on-prem to meet security certification requirements most of the other domains such as retail, aviation, software services have long migrated to AEM Cloud.

Shashi_Mulugu
Community Advisor
Community Advisor
September 15, 2025

Thank you @rohan_garg for your thoughts. 

 

What about clients irrespective of architecture complexity having high content refresh rates.. will AEM LTS save some money for them? As AEM Cloud charges based on hits to publishers?

Rohan_Garg
Community Advisor
Community Advisor
September 15, 2025

Yes, if the refresh rate is extreme then the cloud pricing model could get expensive compared to LTS deployment where infra cost is capped.

But having often seen operation teams struggle with scaling infra to handle traffic surges especially during campaigns, Black Friday sales etc. or ensuring zero-downtime deployments or patching activities gone wrong thereby requiring rollbacks.

All these costs for people and infra ultimately dwarf the licensing cost on LTS.

But just want to know how high is the content refresh rate?

It would have to be for instance thousands of SKU updates per day for e-commerce or say a news portal publishing hundreds of articles per hour to consider staying on LTS. 

 

jatan41
September 25, 2025

We heavily rely on Adobe support with most of the bugs and enhancements at product level and trying to fix them creates lots of customisation to OOTB functionalities.

 

Cloud version automated upgrades and ownership of Infrastructure at Adobe end kind of shifts lot of responsibilities. So, if End of support is coming and Cloud versions have been doing well from many years ‐ Its high time to plan roadmaps for cloud Migration if not already done. 

 

Thanks,

Jatan

Shashi_Mulugu
Community Advisor
Community Advisor
September 25, 2025

Thanks @jatan41, yes that's the game changer. No upgrade headaches.

 

But from Gen AI features standard point, will they make a bigger difference in decision making? What do you think?

Shashi_Mulugu
Community Advisor
Community Advisor
September 25, 2025

@tad_reeves @brettbirschbach 

@brianli6 @ravisurampudi can you comment your opinion here?

BrettBirschbach
Adobe Champion
Adobe Champion
September 25, 2025

The value prop of migrating to Cloud Service is something that's difficult to commoditize in a way that will resonate with everyone.  For example, saving on infrastructure can be high value to some orgs that struggle keeping AEM working efficiently (e.g. particularly those that have a high quantity and velocity of assets) whereas to others it might be minimal savings if their instance is humming and DevOps processes are highly automated.

 

When considering an upgrade, make sure you're thinking about it more than from purely the technical perspective. Yes, technology licenses and infrastrucure represent meaningful cost, but inefficiencies in your overall content supply chain due to a mess of page templates and components that have not been maintained well over time can be costing you a multiple of the technical costs, yet I don't often see people talk about that aspect.

 

When you upgrade, a big part of the value prop can (and many times should) be to also modernize/consolidate/clean up.  You're already going to be touching everything, regression testing everything, and maybe even reauthoring things depending on the required changes to your components in the upgrade.  If you're already going to be doing all that work regardless, it's now only an incremental effort to fully get onto best practices and make the authoring experience simple, delightful and efficient.  I'm wrapping up a Cloud Service upgrade right now for a client that did it the right way, and it was awesome to hear an author state "I authored the home page last night because I was having fun" - I assure you they would have never said that about their pre-migration environment.

 

I recommend everyone take a look at the first half of https://experienceleague.adobe.com/en/docs/events/the-skill-exchange-recordings/aem/aug2023/developer-track/migrate-to-aemcs which focuses on building the value prop of migration.

Shashi_Mulugu
Community Advisor
Community Advisor
September 25, 2025

Really appreciate your take on the broader value of modernization and the authoring experience—those real-world stories are exactly what make these decisions tangible.


You raise a great point about the “hidden” costs of technical debt versus the visible costs of licensing and infrastructure. That’s often overlooked in upgrade conversations.


Curious—have you seen teams opt to stay on LTS, and if so, what was their main reasoning?


Would love to hear any perspectives or lessons from organizations that chose LTS over migration, and how that played out for them.


Looking forward to more experiences from the community, whether you’ve upgraded, migrated, or chosen a different path.