Surge Migrate

For adobe Managed Services customers on AEM 6.5

Plan your move after Adobe Managed Services support for AEM 6.5 ended

Adobe Managed Services support for AEM 6.5 ended on 31 August 2026. With Surge Migrate you scan your code for free, see what blocks AEM as a Cloud Service, compare that with an upgrade to AEM 6.5 LTS, and get a reviewed plan for the option you choose.

The problem

AMS customers face a decision under time pressure: move to Cloud Service now, or upgrade to 6.5 LTS to stay supported while funding the cloud move. Each path has different work, and the choice depends on the code.

What to know first

Adobe Managed Services (AMS) is Adobe hosting and operating AEM 6.5 for you. With AMS support for 6.5 over, the realistic options are AEM as a Cloud Service, AEM 6.5 LTS (Adobe's long-term-support line, which needs Java 17 or 21) as a bridge, or in some cases a rebuild on Edge Delivery Services. The right choice depends on how much of your code needs to change for each, which is exactly what a scan measures.

How to do it in Surge Migrate

  1. Run the free readiness scan. Open the readiness scan and drop your Best Practices Analyzer CSV or a zip of your repository. It is read in your browser and nothing is uploaded. In a few minutes you see a readiness score, every blocker with file, line, fix and how automatable it is, and an effort range in engineer-weeks.
  2. Compare the two paths. Our guides compare AEM 6.5 LTS with Cloud Service. The scan's blockers show how much of the cloud work is mechanical; LTS mostly needs Java 17 or 21 and removed dependencies.
  3. Create your free account and a project. Press Start free, enter your work email and open the one-time link (there is no password). Name your workspace, then start a project and pick the service and how you want to work. Your first 3 months are free.
  4. Pick the service that fits. Choose Cloud Service migration or AEM 6.5 LTS upgrade when you start the project. Both use the same Blueprint and pull-request flow.
  5. Create the Migration Blueprint. Add the scan to the project and press Create Blueprint. You get phases, effort in hours, risks and the decisions your team must make. Our engineers review and approve it; open it in the browser, save it as PDF or publish it to Confluence.
  6. Review and merge the pull requests. Connect GitLab, Bitbucket Cloud or Azure DevOps with an access token. Fixes arrive as small pull requests, one pattern at a time, each approved by a senior AEM engineer. Your team merges and Cloud Manager verifies the build.

What you get

  • The relevant Adobe dates in one place
  • A factual blocker count for the cloud path
  • A plan for either Cloud Service or 6.5 LTS

When Surge Migrate is not the right tool

If your contract with Adobe already includes a migration programme run by Adobe, use that first; Surge Migrate can still scan and review in parallel.

Questions

When does on-premise AEM 6.5 support end?

Core support ends 28 February 2027; extended support (critical fixes only) ends 28 February 2028.

Should we go to LTS or Cloud Service?

It depends on your code and your timeline. The scan shows how much the cloud path involves; our LTS vs Cloud Service guide explains the trade-offs.

Is the scan free for AMS customers?

Yes, for everyone, with no account.

Read next

Try it on your own code

The readiness scan is free and needs no account. The portal is free for your first 3 months.

Start free — 3 months on usRun the free scan

Last updated 1 November 2026 · by Venu Gopal Reddy Muvva, founder