DocumentationCommerceInformation Center

Migration and adoption

Last update: October 21, 2026

CREATED FOR:

  • Admin
  • Developer
  • Leader

Adoption does not need to be a single, all-at-once platform change. Select a route based on whether your immediate goal is storefront modernization, merchandising improvement, backend modernization, or a complete move to managed software as a service (SaaS).

Adoption routes

Modernize the existing Adobe Commerce deployment

  • Keep the existing Commerce Foundation as the transactional backend.
  • Adopt the Commerce Storefront powered by Edge Delivery Services.
  • Use Storefront Services, App Builder, API Mesh, and an optional AEM Assets integration.

Use Commerce Optimizer as a bridge

  • Connect Adobe Commerce cloud or on-premises using the Adobe Commerce Optimizer Connector.
  • Adopt Merchandising Services, discovery, recommendations, and an Edge Delivery Services storefront.
  • Keep Adobe Commerce as the primary system of record for products, prices, catalog structure, cart, checkout, customers, and orders.
  • Use this architecture as a possible transition toward Adobe Commerce as a Cloud Service.

Migrate fully to Adobe Commerce as a Cloud Service

  • Assess the current application, customizations, integrations, storefront, and data.
  • Modernize customizations using SaaS-compatible extensibility patterns.
  • Rebuild or adapt the storefront and integrations.
  • Migrate and validate catalog, customers, orders, configuration, and supported custom data.
  • Test, cut over, and operate the new SaaS environment.

Adopt stand-alone Adobe Commerce Optimizer

  • Ingest catalog and price data from a third-party Commerce platform, PIM, ERP, or other source.
  • Use Adobe Commerce Optimizer Merchandising Services for catalog retrieval, discovery, recommendations, and merchandising.
  • Use the Commerce Storefront powered by Edge Delivery Services.
  • Keep cart, checkout, customers, orders, payments, tax, shipping, and fulfillment in the connected third-party systems.
  1. Assess the current state and define system ownership.
  2. Establish API-first integration boundaries.
  3. Modernize the storefront and experience layer.
  4. Adopt merchandising services and AEM Assets in parallel.
  5. Migrate the Commerce Foundation when required.
  6. Validate, cut over, monitor, and optimize.
recommendation-more-help
commerce-help-information-center