Surge Migrate

For banks, insurers, universities and public bodies

Migrate AEM without sending your code to a third-party AI

Surge Migrate keeps client code away from third-party AI services: the scan runs in your browser, AI work runs on models on servers Surge operates, the routing rule is enforced in code, and every model call and approval is written to a hash-chained audit trail you can export.

The problem

Regulated teams want the speed of AI-assisted refactoring but cannot send source code to public AI services, and auditors ask who changed what, with which tool, and who approved it.

What to know first

Many banks, insurers and public bodies have rules on where source code may be processed and on keeping records of changes to production systems. Public AI services usually fall outside those rules. A migration that uses AI therefore needs two things: a guarantee about where the code goes, and a record of every AI call and every human approval that an auditor can check later.

How to do it in Surge Migrate

  1. Scan without uploading. The readiness scan reads your BPA CSV or repository zip in the browser. Nothing leaves your machine.
  2. 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.
  3. Require single sign-on. Bind your email domain to the workspace with OIDC or SAML 2.0 (Okta, Microsoft Entra ID, ADFS and others), and make single sign-on required. SCIM provisioning is available.
  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. Let AI work only on our servers. Changes that need judgement are drafted by models on servers Surge operates. External models are used only with your written consent, recorded in the audit log.
  6. Export the audit trail. Export the trail as CSV or JSON with the rule to re-verify the hash chain, or stream it to Splunk.

What you get

  • No client code to third-party AI services
  • SSO, SCIM and signed webhooks
  • A verifiable audit trail
  • A private factory option if code cannot leave your network

When Surge Migrate is not the right tool

We make no data-residency guarantee and have no certification or external penetration test yet. If your rules require those today, the private factory service (run inside your environment) is the conversation to have.

Questions

Which AI models do you use?

Open models served on Surge's own AI server. External models only with your written consent.

Can code stay inside our network?

Yes, with the private factory service for organisations that cannot share source code at all.

Do you have ISO or SOC 2 certification?

Not yet.

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