Migrate AEM 6.5 to Cloud Service, one reviewed pull request at a time.
Scan your code in the browser, get a plan with every blocker and its fix, then receive the changes as small pull requests your team reviews and merges.
No sign-up. Your code is not uploaded.On-prem 6.5 core support ends 28 Feb 2027▶ Watch the 2-minute demo
What it does
Everything a migration needs, from first scan to the last pull request
Deterministic tools find the work. A model on our own server drafts what needs judgement. Engineers approve. You stay in control of your repository.
Readiness scan Finds every blocker with file and line, so effort estimates rest on facts, not guesses.
33 code rules and 31 BPA codes find what blocks AEM as a Cloud Service, with file, line, fix and effort for each finding. Runs in your browser.
Run the scan →Deterministic codemods Rewrites the mechanical patterns without AI, so the most common changes are exact and repeatable.
5 rewrites that need no AI: Commons Lang 2 → 3, Log4j 1 → SLF4J, OSGi configs → .cfg.json, CQ XSS → Sling XSS, CQ Workflow → Granite Workflow. Each opens as its own pull request with notes.
See the pipeline →AI refactoring, privately Drafts the harder changes on our own server, so your code never goes to a third-party AI.
Patterns that need judgement go to a model on our own server, never a third-party AI service. Deterministic checks screen every change before an engineer sees it.
Where your code goes →Migration Blueprint Turns findings into phases, effort and decisions, so you can plan and get budget approval.
A component-by-component plan: blockers, phases, effort in hours, risks and the decisions your team must make. Open it in the browser, save it as PDF or publish it to Confluence.
See a sample →Client portal Keeps scans, decisions and pull requests in one place, with a trail you can export for audit.
One place for scans, Blueprints, decisions, pull requests and phases, with a hash-chained audit trail you can export. Links to Jira, Confluence and Cloud Manager.
Tour the platform →Deprecation Watch Watches your code after go-live, so Adobe's next API removals don't break your pipeline.
After go-live, your repository is re-scanned on push or nightly, and new usages of APIs Adobe is removing are flagged before Cloud Manager fails the build.
How it works →How it works
Code counts. The model drafts. A person decides.
Language models are good at refactoring patterns and bad at counting, so each step is done by the right kind of tool. Every step is written to an audit trail.
- 01
Collect
Parsers read code, OSGi configs, dispatcher, indexes and your BPA report.
DeterministicDone by code alone: the same input always gives the same result. - 02
Classify
Every finding maps to a Cloud Service pattern with file and line.
DeterministicDone by code alone: the same input always gives the same result. - 03
Plan
Our private model ranks risk and drafts the change for each pattern.
AI on our serverDone by a model on our own server, then checked by code before a person sees it. - 04
Refactor
Small pull requests, one pattern at a time, with notes and tests.
AI on our serverDone by a model on our own server, then checked by code before a person sees it. - 05
Review
A senior AEM engineer approves every pull request. Your team merges.
HumanA named person approves; nothing merges without it. - 06
Verify
Cloud Manager build, AEM Analyser and parity checks; all steps logged.
DeterministicDone by code alone: the same input always gives the same result.
Get started
From zip file to first pull request
Start with the scan; it takes a few minutes and needs no account. Everything after that happens in the portal and in your own repository.
Export your code or a BPA report Gives the scan something to read; both inputs together give the fullest picture.
Either input works; both together give the most complete picture.
git archive --format=zip -o aem-repo.zip HEADRun the readiness scan Shows blockers, fixes and effort in minutes, in your browser.
Drop the zip or CSV on the scan page. Files are read in your browser and never uploaded.
Create a workspace and add the scan Gives your team one shared place for scans, plans and decisions.
Sign in with your work email (we send a one-time link; there is no password). Create a workspace and a project, then add a scan: a repository zip, a BPA CSV or a short questionnaire.
Connect your repository Lets fixes arrive as pull requests in your own repository.
Link GitLab, Bitbucket or Azure DevOps with an access token. The default branch is scanned on our server, and codemod changes arrive as pull requests on their own branches. GitHub connects through our GitHub App, which is being set up.
Your code, your control
Built for teams that cannot hand their code to a black box
- The scan runs locally. Your zip or CSV is read in the browser and never uploaded.
- Private AI only. Client code goes to models on servers we operate, not third-party AI services, unless you agree in writing.
- Humans approve every change. Pull requests land in your repository; your team merges.
- Tamper-evident audit trail. Every scan, model call and approval is hash-chained and exportable as CSV or JSON.
- Open rules. 33 code rules and 31 BPA codes, each with the fix and the effort method shown.
Questions
Common questions
Do you upload my code for the readiness scan?
No. The scan reads your BPA CSV or repository zip inside your browser. Only if you ask for an AI summary do we send aggregated counts (finding types and numbers, never file contents or paths) to our server.
Which AI do you use, and where does my code go?
Client code is processed by AI models running on servers we operate, not by third-party AI services. External models are used only if you agree in writing. Deterministic tools do the fact-finding, so the AI never decides what exists in your code.
Who reviews the changes?
A senior AEM engineer reviews every pull request before it reaches you, and your team merges. Nothing lands on your main branch without a named approval, recorded in the audit trail.
How is this different from Adobe's free migration tools?
We use them. Best Practices Analyzer, Cloud Acceleration Manager and Adobe's migration tooling fix individual patterns. We add estate-wide fact collection, a reviewed plan, pull requests per pattern, verification and an audit trail for the whole migration.
Can our own team or current partner do part of the work?
Yes. Pull requests land in your repository, so your developers or your partner can review, adjust or take over any part of it.
What does it cost?
Nothing during early access. Before we introduce prices we will tell you in advance, and nothing you started for free becomes paid without your written agreement.
See what your migration involves
Drop in a repository zip or a BPA report. You get blockers, fixes and an effort range in a few minutes, without creating an account.
Surge Migrate is a new product from Surge Software Solutions Private Limited, an Adobe Experience Cloud services firm founded in 2018. About us. We will publish case studies once clients agree to them.