Surge Migrate

Get started

From AEM 6.5 code to your first pull request

Six steps. The first two take a few minutes and need no account; the rest happen in the client portal and in your own repository.

  1. Export your code or a BPA report

    Your machine5 minutes

    Either input works; both together give the most complete picture.

    • Code: zip the repository from its root, as below.
    • BPA report: on an AEM 6.5 author with Best Practices Analyzer installed, open Tools → Operations → Best Practices Analyzer, generate the report and download the CSV.
    Zip the repository (run in its root)
    git archive --format=zip -o aem-repo.zip HEAD

  2. Run the readiness scan

    Browser, no sign-up2 minutes

    Drop the zip or CSV on the scan page. Files are read in your browser and never uploaded.

    • Readiness score and blockers by category
    • Each finding with file and line, the fix, and how automatable it is
    • Effort range in engineer-weeks, with the method shown

    Open the readiness scan →

  3. Create a workspace and add the scan

    Client portal3 minutes

    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.

    Sign in to the portal →

  4. Connect your repository

    Client portalOptional

    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.

  5. Get your Blueprint

    Client portalReviewed within two weeks

    Create a Blueprint from any scan. Our engineers review it and approve the plan: phases, effort, risks and the decisions your team needs to make. Open it in the browser, save it as PDF, or publish it to Confluence.

    See a sample Blueprint →

  6. Review and merge pull requests

    Your Git hostOngoing

    Each pull request covers one pattern and explains what changed and what to check. Your team reviews and merges; Cloud Manager verifies. Phases, decisions and every approval are tracked in the portal's audit trail.

What leaves your machine

Nothing during the scan. In the portal, scans and repository contents are processed on our servers, and AI work runs on models we operate.

Security details →

Who does what

Deterministic code finds and counts. Our private model drafts changes that need judgement. Engineers approve. Your team merges.

How the pipeline works →

What it costs

Everything is free while we are in early access. Before we introduce prices we will tell you in advance, and nothing you started for free becomes paid without your written agreement.

Pricing →

Start with step 2

Already have a zip or a BPA CSV? Drop it on the scan page and see your blockers in a few minutes.

Run the free scan