AEM as a Cloud Service — Code Migration

Source → target: Legacy AEM 6.x / AMS / on-prem → AEM as a Cloud Service. Scoped under skills/aem/cloud-service/skills/migration/ so this is not confused with Edge Delivery or 6.5 LTS.

This skill is orchestration: BPA data, CAM/MCP, one pattern per session, and target discovery. Transformation rules and steps live in the best-practices skill — read that skill and the right references/*.md before editing code.

Setup: Use the aem-cloud-service install (see repository root README) so both migration and best-practices paths are available. If you already have the monorepo open with resolvable {best-practices} paths, no separate install step is required.

Quick start (for the person driving the agent)

One pattern per chat/session — if you ask to "fix everything," the skill will ask you to pick first (e.g. scheduler vs replication vs htlLint).

You have…	Say something like…	What happens
A BPA CSV	"Fix scheduler* findings using `./path/to/bpa.csv`"*	Fastest path: CSV → cached collection → files
CAM + MCP only	"Get scheduler* findings from CAM; I'll pick the project when you list them."*	Agent lists projects → you confirm → MCP fetch (cam-mcp.md)
Just a few files	"Migrate scheduler* in `core/.../MyJob.java`"*	Manual flow: no BPA required
OSGi → Cloud Manager	"Scan my config files and create Cloud Manager environment secrets or variables."	Agent auto-reads references/osgi-cfg-json-cloud-manager.md (full Adobe-aligned rules inlined there); no BPA pattern id
HTL lint warnings	"Fix htlLint* issues in `ui.apps`"*	Proactive discovery via `rg` → fix per reference module

migration

AEM as a Cloud Service — Code Migration

Quick start (for the person driving the agent)

More from himanich/skills

best-practices

ensure-agents-md

dispatcher

aem-workflow

create-component