Requires Sample Source code for AEM 6.5 to AEM Cloud Migration

Hi @randeep_virk,

You won’t find a single “ready-made source code” package that migrates everything from AEM 6.5 to AEM as a Cloud Service, but Adobe and the community provide some really useful reference tools and examples you can leverage.

Here are the main things to look at:

1. Source Migration Tools (Adobe GitHub)
   Adobe maintains the aem-cloud-service-source-migration repo. It includes utilities like:

   • Repository Modernizer -> helps restructure static templates/configs into the Cloud-compatible model

   • Index Converter -> converts custom Oak indexes for AEMaaCS packaging/deployment

   • Dispatcher Converter -> adapts dispatcher configs to Cloud Service format

2. Static Templates
   In AEMaaCS, templates must come from code (immutable). You’ll need to migrate legacy static templates into the new /conf-based structure or editable template definitions. The Repository Modernizer can help as a starting point.

3. Oak Indexes
   Custom indexes are still supported, but must be deployed via code packages. The Index Converter tool will transform existing index definitions, and don’t forget to include the proper filter.xml entries so your /oak:index/... nodes are packaged and deployed correctly.

4. Asset Workflows
   A lot of asset processing in Cloud Service is handled by microservices (Asset Compute, etc.). If you have custom workflows (renditions, transformations), you’ll need to either re-implement them using the new microservice model or integrate them as custom steps. Adobe also provides the Content Transfer Tool (CTT) to handle the bulk migration of assets, renditions, and metadata.

5. Dispatcher Config
   Dispatcher configs must be adapted to the Cloud Service dispatcher structure. The Dispatcher Converter in the migration repo will help here.

Recommended approach:

• Start by running Adobe’s compatibility/best practices analyzers to identify blockers.

• Scaffold a new Cloud Service project using the latest AEM Maven archetype.

• Use the migration tools (repo modernizer, index converter, dispatcher converter) to transform your existing code.

• Migrate templates, indexes, and workflows into the new structure.

• Use the Content Transfer Tool for moving actual page/asset content.

• Set up Cloud Manager pipelines for deployment since all code/config goes through CI/CD.

In short: there isn’t a full “drop-in project,” but Adobe’s migration tools + reference projects (like the WKND site) cover the majority of what you need. The rest will require adapting your own custom logic (especially for static templates and asset workflows).

hi @randeep_virk 

Adobe’s Source Migration Tools (GitHub)
The aem-cloud-service-source-migration repository includes utilities such as

• Repository Moderniser → restructures static templates and configurations into a Cloud-ready format

• Index Converter → converts custom Oak indexes for deployment in Cloud Service

• Dispatcher Converter → adapts on-prem dispatcher configs to the Cloud Service style

Templates
In AEMaaCS, templates are immutable and must come from code. Legacy static templates need to be migrated to the /conf editable template structure. The Repository Moderniser is a good starting point here.

Oak Indexes
Custom indexes remain supported, but they have to be deployed through code packages. The Index Converter will transform existing definitions, and you’ll need proper filter.xml rules so your /oak:index/... nodes get packaged.

Asset Workflows
In Cloud Service, much of the asset processing (renditions, transformations, etc.) is offloaded to microservices such as Asset Compute. Custom workflows may need to be rebuilt with the microservice model or re-implemented with custom workflow steps. For bulk content (assets, renditions, metadata), Adobe provides the Content Transfer Tool (CTT).

Dispatcher Configuration
Dispatcher configs must follow the Cloud Service format. The Dispatcher Converter tool helps convert existing setups.

Suggested migration approach

1. Run Adobe’s compatibility and best-practice analysers to identify blockers.

2. Generate a new Cloud Service project using the latest AEM Maven archetype.

3. Apply the migration tools (repo moderniser, index converter, dispatcher converter) to adapt your codebase.

4. Move templates, indexes, and workflows into the new structure.

5. Use the Content Transfer Tool for migrating content.

6. Set up deployments via Cloud Manager pipelines (all code/config flows through CI/CD).

Let me update my requirement , I think there is some misunderstanding.
Let me communicate in better way this time.
My requirement is a sample codebase or an open-source project (running on AEM 6.5) that I can migrate to AEM as a Cloud for my hands-on practice.

@santoshsai  @syed_shaik