Migration

Orchestrates AEM 6.x/AMS/on-prem to AEM as a Cloud Service migrations with a strict one-pattern-per-session workflow. Works from BPA CSV exports or CAM/MCP to fix Cloud Service blockers like schedulers, replication agents, event listeners, and HTL lint warnings. The separation is clean: this skill handles discovery and orchestration, while transformation rules live in a companion best-practices skill you read first. Includes a dedicated branch for scanning OSGi configs and generating Cloud Manager environment variables with proper secret placeholder syntax. If you're running a methodical AEM Cloud migration and want guardrails against mixing patterns in a single chat, this keeps you on track.

skills.sh installs: 958
GitHub stars: 322
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add adobe/skills --skill migration --agent claude-code

Installs into .claude/skills of the current project.

Files

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 drives the migration workflow: BPA data, CAM/MCP, one pattern per session, and target discovery. Transformation rules and steps live in the code-assessment skill — once a finding's pattern is identified, hand off to {code-assessment}/<pattern>/SKILL.md (or the relevant shared reference under {code-assessment}/references/).

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