How to Migrate to Adobe Commerce as a Cloud Service (ACCS)

Migrating to Adobe Commerce as a Cloud Service (ACCS) is a strategic shift from merchant-managed upgrades to Adobe's fully managed, versionless SaaS — with architectural implications for storefront, integrations, and custom code.

PaaS vs SaaS responsibility: On PaaS, merchants manage application code, patching, and infrastructure config. On ACCS, Adobe manages core application and infrastructure; merchants customise via App Builder, API Mesh, and supported APIs only.

Three migration paths: (1) Full migration — all data, customisations, and integrations at once; best for smaller catalogues and fewer extensions. (2) Incremental migration — staged data and customisation moves for complex enterprises. (3) Commerce Optimizer first — adopt Merchandising Services and Edge Delivery storefront while backend remains on existing Commerce — lowest-risk modernisation step.

Storefront mitigation: Luma storefronts must migrate to Commerce Storefront powered by Edge Delivery. PWA Studio can migrate to Edge Delivery or remain temporarily. Existing headless storefronts may need less storefront rework but still require API Mesh updates.

Customisations & extensions: In-process PHP extensions must move to App Builder out-of-process extensions. Plan recreation, not porting — budget 30–50% of original extension cost as a planning estimate.

Data migration: Use Adobe's bulk data migration tooling with staged validation. Never skip redirect mapping, order history decisions, and ERP cutover testing.

Integrations: Rebuild on the integration starter kit or ACCS REST APIs. API Mesh centralises GraphQL for storefront and third-party systems.

Nexa TechnoLabs delivers ACCS discovery, Optimizer Connector deployments, and full SaaS migration programs. ACCS migration guide