AEM to the cloud in months, not years.

AEM 6.5 support ends in December 2026, and migrating does not have to mean 18 months of consultants. AI agents do the heavy lifting, certified Swiss AEM architects make every call, and your price is fixed before the project starts.

Book your migration assessment See how it works

72 hours of agent runtime from read-only access to a fixed-price offer. From CHF 25,000.

The deadlineThe migration wave is dated, and the clock is Adobe's

December 2026 is not a suggestion

Adobe ends general support for AEM 6.5 on 31 December 2026, with paid extended support through 2027. Managed Services hosting retires even earlier. Staying is not free either: extended support costs money and every month on 6.5 adds patching debt. Every AEM 6.x platform moves: to Cloud Service, to the LTS holding pattern, or off Adobe.

There is no lift-and-shift

AEM as a Cloud Service is rebuilt, not rehosted: code becomes immutable at deploy time, code and content travel separately, and the only path to production is a Cloud Manager pipeline with mandatory quality gates. Every customisation gets re-assessed.

Migrations are scoped on assumptions

The traditional path runs 9 to 18 months and is priced on time and material, because nobody really knows what is in the codebase before the project starts. The overruns are born on day one, in the estimate.

Most of the work is mechanical

Cataloguing components, diffing against deprecated APIs, JSP to HTL conversion, package restructuring: repetitive, rule-driven, high volume. Exactly the work AI agents do well, supervised by people who spent years doing it by hand.

How it worksEight AI agents, human decision gates

A purpose-built multi-agent framework for AEM 6.x to Cloud Service and Edge Delivery migrations. Every agent is domain-constrained: it knows Adobe's compatibility rules and our migration playbooks, and it does not improvise outside its lane. A VASS-certified architect signs off every structural decision, and the framework runs in an isolated environment per client: your tenant, a VASS-managed Swiss environment, or on-premise for regulated industries.

Agent 01

Orchestration

Plans the migration, assigns tasks to the other agents, tracks state, and enforces a human checkpoint between every phase.

Agent 02

Assessment

Crawls your repository across nine analysis areas, from Java APIs to OSGi to i18n. Flags what it cannot determine from code instead of guessing. Produces your assessment report.

Agent 03

Cloud readiness

Prepares the codebase while you still run on-prem: package restructuring, deprecated API replacement, archetype upgrade. Risk drops before migration starts.

Agent 04

Refactoring

Automated code transformation: JSP to HTL, Sling Model updates, Core Component swaps, Java 21 fixes. High-confidence changes committed, the rest queued for architect review.

Agent 05

Content & assets

Audits the content tree, finds orphaned and duplicate assets, validates metadata, generates the Content Transfer Tool and asset upload configurations.

Agent 06

Quality & tests

Generates unit, integration, and UI regression tests. Predicts Cloud Manager quality-gate failures before the first deploy, not after.

Agent 07

Go-live

Handles certificates, DNS, and egress early (they have hidden lead times), models your traffic-based license sizing, flags where it needs a commercial conversation with Adobe, and orchestrates cutover with a tested rollback.

Agent 08

Edge Delivery pathway

For teams going straight to Edge Delivery Services: maps components to blocks, scaffolds the project, sets up document-based authoring.

Agents are the engine. Years of Swiss AEM delivery are the guardrail: the agents run on the compatibility rules and lessons learned from real enterprise migrations like Swissgrid and GVB. Your code never traverses external AI services without your explicit consent, and the full agent decision log is part of your deliverable: every transformation traceable, auditable, reversible.

The pathAssess first, then prepare, migrate, switch
01

The assessment

72 hours · read-only access
  • Nine areas mapped: code structure, Java APIs, OSGi config, service users, integrations, assets, i18n, frontend, third-party modules
  • Every finding traceable to a file and line, nothing guessed
  • Effort priced from measured engagements, not optimism
  • Your side: a 30-minute call to set up read-only access. That is all until the report lands
02

Prepare and migrate

Agents build · architects decide
  • Cloud readiness first, while you still run on-prem: the lowest-risk path
  • Automated refactoring and content migration run concurrently, tests generated as components complete
  • Quality gates predicted before the first deploy, a live dashboard instead of a weekly status deck
  • Your side: a product owner and a part-time platform lead. No client dev capacity needed for the mechanical work
03

Go-live and run

Cutover, then a safety net
  • Certificates, DNS, and egress handled early, not at go-live week
  • Cutover is mostly a DNS switch, with a tested rollback
  • Your on-prem system stays on standby through the safety window
  • Optional retainer keeps you off the next support cliff, without a second migration project
The offerThree products, priced in the open

Start with the assessment. Migrate at a fixed price. Stay current with the retainer.

Migration assessment

Fixed scope, fixed price, read-only access. The readiness report, the risk map, and a preliminary fixed-price offer, in 72 hours of agent runtime plus architect review. The report is yours to keep, whoever you migrate with.

CHF 25,000 to 45,000 · fixed

Accelerated migration

A fixed price built on assessment data, not assumptions. Where you land in the range depends on component count, custom integrations, and asset volume: the assessment tells you. If we finish ahead of the baseline fixed at contract, the savings split 50/50 with you.

Typically CHF 0.8M to 2.2M · fixed

Cloud success retainer

After go-live: monitoring for new Adobe deprecations, regression tests after every Service Pack, upgrade readiness reports. Your platform stays current instead of aging into the next forced migration.

CHF 8,000 to 20,000 per month

Most AEM migrations fail on scope, not skill. So we price on data, not assumptions.

That is why the assessment comes first. You see your technical debt, your risk map, and your fixed migration price before you commit a single franc. The numbers behind the offer come from effort figures measured on delivered Swiss migrations. And where parts of a platform are genuinely unpredictable, the offer says so openly instead of hiding it in a time-and-material clause.

Where it connectsBuilt and run by the VASS Adobe practice

Adobe Gold Partner · 70+ certified employees · 80 Adobe certifications

Adobe AEMEdge Delivery ServicesAdobe practice overviewDigital Experience services
ProofSwiss enterprises already moved with us

Swissgrid: on-premise to AEM Cloud Service in four months

VASS moved Swissgrid, operator of Switzerland's power grid, from AEM on-premise to AEM as a Cloud Service in four months: lower hosting and license costs, automatic updates, smooth operations after cutover, with VASS staying on for support.

Read the Swissgrid case →

GVB logo

GVB: 15+ websites on AEM Cloud, migrated in under 3 months

GVB, the Bern-based building insurer, runs a network of over 15 websites from a single AEM Cloud authoring environment. VASS migrated them in under 3 months and stayed as the long-term partner, expanding the stack into personalization, targeting, and marketing automation.

Read the GVB case →

We show you the bill before you sign.

A 72-hour assessment on read-only access: your technical debt, your risk map, your fixed migration price. From CHF 25,000. If your platform is too complex for a fixed price, we tell you that too.

Samuel Schmitt
Samuel Schmitt
Head of Sales & Marketing, VASS Switzerland
Book your migration assessment