Migration Assessment

A Commerce migration assessment is an automated analysis of your existing Adobe Commerce implementation. Adobe’s tooling scans your Commerce codebase and produces a structured report that inventories everything built, customized, or modified. The report then indicates how the customizations made to your codebase impact your migration to Adobe Commerce as a Cloud Service.

The report is delivered as an HTML file that you can open with any browser. No access to your production environment is required, except initially sharing your project codebase.

The assessment provides:

Understanding the migration assessment report

The report is organized into three tabs: Summary, Module Reports, and Report Reliability.

Summary tab

The Summary tab provides an overview of key signals organized into these areas:

Migration complexity

The Migration Complexity section contains the assessment rating for your store overall. It explains how the score was calculated and highlights your primary risk drivers.

Migration Complexity and Complexity Score

{width="600" modal="regular"}

The Complexity Score weights each input by how difficult it is to migrate. The score maps to a Migration Complexity rating using fixed thresholds:

Custom Module Ratio

{width="600" modal="regular"}

The percentage of your modules that were built specifically for your implementation. A higher ratio means more custom code must be audited and migrated. The average customer’s Custom Module Ratio is approximately 62%.

File Type Breakdown

{width="600" modal="regular"}

A list of the number of files in your codebase, organized by type.

Highest-Impact Modules

{width="600" modal="regular"}

A curated list of the specific modules in your store requiring the most migration attention. These modules are often modules that interact with checkout, payments, or order management. Each high-impact module needs its own migration plan. This list is the best starting point for conversations with your technical team.

Storefront complexity

{width="600" modal="regular"}

The Storefront Complexity section surfaces the effort required to migrate your store’s front-end presentation layer. This workstream is a distinct workstream from backend code migration, addressed by front-end developers and typically requiring separate planning conversations.

Migration drivers

{width="600" modal="regular"}

The Migration Drivers section displays the top factors driving your complexity rating.

Each driver appears with a High, Medium, or Low effort. Address the highest-rated drivers first when scoping and planning.

Data model

{width="600" modal="regular"}

The Data Model section displays a count of custom tables, modifications to the Adobe Commerce core database tables, and critical Entity-Attribute-Value (EAV) attributes.

Core table modifications are the most difficult category to migrate, because they create dependencies on a specific platform schema version and have a high impact in the Complexity Score formula.

Customization breakdown

{width="600" modal="regular"}

The Customization Breakdown section provides detailed metrics across every category of customization in your store.

Layout XML

The number of Layout XML files and their total operation count. Layout XML defines the structure of every page, including which blocks appear, the containers they appear in, and the page types they are under.

A high file count with many operations signals significant page structure customization that must be re-architected.

Core handle overrides

The number of places where your Layout XML overrides a core Adobe Commerce page handle (for example, checkout_cart_index or catalog_product_view). Core handle overrides are the highest-risk layout signal because they modify page structure at the platform level and require explicit rebuilding.

Blocks

The number of block and template (.phtml) files in your store. Blocks are the primary server-side rendering artifacts. Each block represents a discrete migration task.

High-risk blocks

Blocks that touch core render paths, such as checkout rendering, cart display, and similar front-end surfaces. Any high-risk blocks require individual migration assessment before scheduling.

Themes and email templates

The namespace of your store’s custom theme (for example, BrandName_Theme). The presence of a custom theme means a full theme rebuild is required. Every assessed store with a custom theme namespace must plan a dedicated front-end migration workstream.

Template overrides (core modified)

The number of core Adobe Commerce .phtml templates that have been overridden. Each core template override creates a dependency on a specific version of that template. Platform updates that change the template break the override silently.

Drop-in migration required

Adobe Commerce as a Cloud Service uses a modular drop-in component architecture for storefront surfaces including checkout, cart, and product detail. Customizations to these surfaces must be rebuilt as drop-in components. These customizations can cover a wide range of functionality, such as adding custom checkout steps, modifying cart display logic, or extending the product detail page.

The Drop-in migration required field indicates which storefront areas require drop-in rebuilds.

Module Reports tab

{width="600" modal="regular"}

The Module Reports tab contains a dedicated entry for every custom module in your store. Share this information with your technical team.

For each module, the report displays:

Workflow

Reference: key terms

AI developer tools for Commerce extensibility

You can use the module descriptions in the Module Reports tab as prompts for Adobe’s AI developer tooling. The tooling assists you in building and deploying a replacement extension that is compatible with Adobe Commerce as a Cloud Service.

What the tools provide

Adobe’s AI developer tools for Commerce extensibility include two primary capabilities.

Install AI tools

Refer to installing the AI developer tools for full instructions and specific IDE configurations.

Prerequisites: Node.js 22.x, npm 9.0.0 or higher, Adobe I/O CLI.

Install command:

aio commerce extensibility tools-setup

Create prompts from the assessment report

While the assessment gives you a blueprint for development, the AI tools allow your team to start building immediately, before a full migration plan is finalized.

Manages custom shipping rate calculations based on customer account tier and order    weight thresholds.

Next steps

Resources