Surge Migrate

For adobe partners and AEM agencies

Run AEM migrations for your clients as an Adobe partner or agency

Adobe partners and AEM agencies can use Surge Migrate for their own clients: scan each client's estate, share a reviewed Blueprint in a client workspace, and deliver the mechanical changes as pull requests in the client's repository, with an audit trail the client can verify.

The problem

Agencies win migration work but lose margin on repetitive refactoring, and clients increasingly ask how AI was used on their code and who approved each change.

What to know first

Most AEM estates are built and maintained by partners and agencies, and many clients now need the move to Cloud Service done before their support ends. The repetitive part of that work is the same across clients: removed APIs, OSGi formats, admin sessions and dispatcher rules. Tooling that finds and fixes those patterns lets a partner spend its engineers on the design work clients actually pay for.

How to do it in Surge Migrate

  1. Scan a client's estate. Run the free readiness scan on the client's BPA report or repository zip. Nothing is uploaded.
  2. Create a workspace for the client. Sign up free, create a workspace in the client's name, and invite the client's team. Workspaces keep each client separate.
  3. Pick how you work. Start a project with Done with you or Self-serve, so your developers review, adjust and merge the pull requests.
  4. 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.
  5. 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.
  6. Give the client the audit trail. Export the hash-chained audit trail as CSV or JSON. The client can re-verify the chain to see which model produced each change and who approved it.

What you get

  • One workspace per client
  • Pull requests your developers own
  • An audit trail clients can verify
  • Our engineers on call

When Surge Migrate is not the right tool

If you need white-labelled branding or reselling terms, talk to us first: the partner programme is set up per partner, not self-serve.

Questions

Is there a partner programme?

Yes. It is free during early access; contact us to set it up.

Can clients see what AI did?

Yes. Every AI call and approval is recorded in the audit trail, and client code goes only to models on servers Surge operates.

Do we keep the client relationship?

Yes. You invite the client to the workspace you create; pull requests land in their repository.

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