Adobe Commerce to Shopify migration: what June 2027 changes

The 1 June 2027 date that takes Adobe Commerce Cloud storefronts offline is not the version deadline for a 2.4.7 store. If you are pricing an Adobe Commerce to Shopify migration against that date, you are probably reading the wrong row of Adobe's table. A 2.4.6 or 2.4.7 store on Cloud has until 1 June 2028 to change versions, but its PHP, database, search and cache services face deadlines of 30 October 2026 and 31 May 2027, and missing those carries the same penalty.

By the end of this piece you will know which date applies to your store, what the 2.4.9 upgrade actually involves, what a move to Shopify has to carry, and why the upgrade quote is the number to get before you price anything else. All dates below come from Adobe's own pages as of 28 October 2026.

Your version (Adobe Commerce on Cloud)	Dependencies upgraded by	Commerce version upgraded by
2.4.4 or 2.4.5	30 October 2026	1 June 2027
2.4.6 or 2.4.7	30 October 2026 or 31 May 2027, depending on the software	1 June 2028
2.4.8 or 2.4.9	30 October 2026 or 31 May 2027, depending on the software	Not required at this time

Source: Table 1 of Adobe's Security and Compliance Notice, last updated 14 October 2026.

What happens to Adobe Commerce Cloud on unsupported versions in June 2027

Adobe's lifecycle policy, last updated 18 September 2026, says that starting 1 June 2027, "Adobe will no longer maintain Cloud environments running unsupported Commerce versions". It continues: "This includes suspending traffic to the affected infrastructure. As a result, your ecommerce storefront will go offline."

Suspension is not the last step. The same page says that if an environment stays non-compliant after traffic is suspended, Adobe may terminate cloud services and begin decommissioning, after which all data, instances, environments and branches "will be permanently deleted and cannot be restored." The Security and Compliance Notice adds a softer first stage: Adobe may suspend Admin access for all users while the storefront stays online, and/or suspend inbound traffic.

The scope is narrower than most coverage implies. The notice applies to "Adobe Commerce on Cloud (PaaS) environments running Adobe Commerce versions 2.4.4 through 2.4.9" and states that it "does not apply to Adobe Commerce as a Cloud Service (SaaS) environments or Adobe Commerce on-premises deployments." Magento Open Source is self-hosted and is not named in either document. If you run on-premises, nobody is switching your store off in June 2027; you are simply on your own for patches once support ends.

When does Adobe Commerce 2.4.7 support end?

Adobe Commerce 2.4.7 standard support ends on 31 May 2027 and extended support ends on 31 May 2028, according to the lifecycle policy's end-of-support table. Adobe describes that extra year as "one year of additional support at no additional cost" for 2.4.6 and 2.4.7, covering quality and security patches for the core application. The Cloud enforcement date for 2.4.7 is 1 June 2028.

Your 2.4.7 store's June 2027 problem is its dependencies

The lifecycle policy is explicit that the version is not the only trigger: "Running unsupported dependency versions may result in a security vulnerability on your Cloud instance that Adobe is unable to resolve," and the consequence it then describes is the same traffic suspension. Adobe also states that it does not provide fixes for third-party services that reach end of life during a Commerce support period. Table 2 of the Security and Compliance Notice sets these deadlines for every Cloud store on 2.4.4 through 2.4.9:

Service	If you run	Move to	Deadline
PHP	8.1 and below	8.2 or higher	31 May 2027
MariaDB/Galera	10.5 and below	10.6 or higher	30 October 2026
MariaDB/Galera	above 10.5, below 10.11	10.11 or higher	31 May 2027
Elasticsearch	any version	OpenSearch 3 (2.4.6 and above)	30 October 2026
OpenSearch	1.x	OpenSearch 3 (2.4.6 and above)	31 May 2027
Redis	5 and below	Valkey 8 or higher	31 May 2027
RabbitMQ	3.9 and below	3.13 or higher	30 October 2026
RabbitMQ	above 3.9, below 3.13	4.3 or higher	31 May 2027

Two of those rows are not version bumps. Adobe's own wording is that "Elasticsearch to OpenSearch and Redis to Valkey are migrations to different software rather than version upgrades," so custom code, extensions or configuration that reference the old service may need changes. It also warns that moving from PHP 8.1 to 8.2 "can surface deprecations in custom code and third-party extensions." On Cloud you cannot upgrade these services yourself: Adobe does it from a support ticket, which it asks you to open at least 30 days before your enforcement date, and the requirements apply to every environment, not just production.

This is where agency coverage goes stale fastest. Shero Commerce's Adobe Commerce to Shopify page still describes the latest Adobe Commerce release as 2.4.8-p4 from March 2026, while Adobe's lifecycle policy lists 2.4.9 as generally available since 12 May 2026. If the page selling you the migration has the current version wrong, check its deadlines against Adobe's tables before you plan around them. We made the same point about the PHP clock in our Magento 2.4.6 end of support breakdown: on 2.4.6, PHP 8.2 reaches end of life before Adobe's own support for the release does.

The Adobe Commerce 2.4.9 upgrade touches more than the version number

Adobe names 2.4.8, 2.4.9 or the latest release as its "fully supported versions," and its Table 3 tells 2.4.6 and 2.4.7 stores to upgrade to 2.4.9 or migrate to Adobe Commerce as a Cloud Service. Adobe Commerce 2.4.9 went GA on 12 May 2026 with standard support to 31 May 2029, which is about three years of standard support.

The 2.4.9 release notes explain why this is not a patch-level jump for a heavily customized store:

• "PHP 8.2 and PHP 8.3 are no longer supported." PHP 8.5 is fully supported, and PHP 8.4 is "allowed for upgrade purposes only (not recommended for production)."
• A native MVC implementation replaces the legacy Laminas MVC.
• The Symfony Cache component replaces the deprecated Zend_Cache.
• The admin WYSIWYG editor moved from TinyMCE to HugeRTE.
• OpenSearch 3.x is the recommended search engine, Valkey 9.x is supported, and ActiveMQ Artemis is the recommended long-term message broker.

If your store runs PHP 8.2 or 8.3 today, the upgrade is also a PHP jump to 8.4 or 8.5. We covered why we would target 8.5 rather than 8.4 in upgrade PHP 8.1 to 8.4 or 8.5, and Adobe's production guidance points the same way. Every custom module that extends framework classes, caches through Zend_Cache or customizes the WYSIWYG editor needs checking. Adobe provides an Upgrade Compatibility Report through its Site-Wide Analysis Tool that lists the modules and files needing updates and the number of critical issues.

Adobe Commerce to Shopify migration is one of three exits, not two

Most comparisons frame this as upgrade versus Shopify. Adobe's own pages list a third path, and it is the one Adobe recommends: migrate to Adobe Commerce as a Cloud Service, its SaaS product, where Adobe "manages all infrastructure, patching, and upgrades automatically." Adobe offers a migration assessment tool and a bulk and incremental data migration tool for that move "at no cost to you."

Path	What it removes	What it keeps or adds
Upgrade to 2.4.9 on Cloud	The 2028 version deadline; standard support runs to 31 May 2029	Your code and extensions, plus future upgrades: Adobe says this path "does not eliminate future upgrade obligations"
Adobe Commerce as a Cloud Service	Recurring upgrade cycles and the PaaS enforcement policy, which does not apply to SaaS	A re-platform inside Adobe; Adobe points to App Builder for extension re-platforming
Shopify (Plus or another plan)	Adobe licensing and hosting, and the upgrade treadmill	A full rebuild of storefront, integrations and custom logic on Shopify's apps and APIs, plus a 1- or 3-year Plus term if you choose one

The strongest case for Shopify deserves its full weight. If you would pay for a 2.4.9 upgrade now and face another when 2.4.9 standard support ends on 31 May 2029, the upgrade is not a one-off cost, and Adobe says so in its own words. A team that has spent years paying to keep a customized Magento codebase current has a reasonable argument for buying a platform where that work is the vendor's job. The answer is that Adobe's SaaS makes the same promise without abandoning your catalog structure, B2B setup or Adobe integrations, so "no more upgrades" alone does not point to Shopify. The case for Shopify has to rest on something else: cost, team skills, or a storefront you want to rebuild anyway.

What a Magento to Shopify migration has to carry

Shopify's tooling for this move is thinner than the agency pages suggest. Shopify's own Store Migration app lists Square, WooCommerce, Etsy, Wix, Amazon, eBay, Clover and Lightspeed as sources; Magento is not on that list, so you are into third-party apps such as Cart2Cart and LitExtension, or a custom script against Shopify's APIs.

Order history is the item most often underestimated. Shopify's migration guide lists only migration apps, the Order API and the Transaction API for historical orders, with no CSV route, and says to "import your products first, then your customers, and then any historical orders." Redirects can be imported by CSV, and Shopify's setup guide warns that its "link structure for individual pages is likely different from your previous service," which means every Magento product, category and CMS URL needs a mapped redirect before the domain moves.

Shopify Plus migration from Adobe Commerce for B2B

B2B is no longer a Plus-only question. Shopify's B2B documentation says "Shopify B2B is available on the Basic, Grow, Advanced, and Shopify Plus plans," and the Plus pricing page lists unlimited B2B catalogs for Plus. Feature depth is the question to test. Even Shero, which sells these migrations, concedes in its FAQ that requisition lists and negotiated quotes "require custom development or App Store solutions." If your Adobe B2B buyers rely on those, cost them as builds, not as settings.

Custom extensions follow the same rule. None of them move; each becomes a Shopify app, a custom app or a dropped feature. That inventory, module by module, is the real size of an Adobe Commerce to Shopify migration.

Is it cheaper to upgrade Adobe Commerce or migrate to Shopify?

Nobody can answer that from a published figure, because the published figures are sales material. Shero states that "Adobe Commerce migrations run 14-22 weeks depending on B2B complexity, Experience Cloud scope, and ERP integration depth"; treat that as one agency's pitch, not a benchmark. We found no primary source for migration cost or duration, and we are not going to invent one.

What you can get is a real number for the baseline. The Upgrade Compatibility Report tells you which modules break on 2.4.9; the dependency table tells you which services must move by 31 May 2027. Price that work first. A Shopify quote is only meaningful when it is compared with the upgrade quote for the same store, because you will be paying one of them before 1 June 2028 either way, and for 2.4.4 and 2.4.5 stores, before 1 June 2027.

Shopify is the wrong choice if your differentiation lives in custom checkout logic, complex B2B pricing rules or deep Adobe Experience Cloud integrations you intend to keep. The 2.4.9 upgrade is the wrong choice if your module audit shows most of your customizations are workarounds you would not rebuild, because then you are paying to preserve code you would rather delete.

Price the 2.4.9 upgrade before you price Shopify

1. Check your version with bin/magento --version and your service versions in the Cloud Console's Containers tab, then find your row in Adobe's tables.
2. Open the Adobe support ticket for dependency upgrades at least 30 days before your deadline. As of 28 October 2026, the 30 October dependency deadline is two days away; if you need more time, Adobe's notice says to contact your account team for a short extension.
3. Generate the Upgrade Compatibility Report and sort every flagged module into fix, replace or drop.
4. Only then request Shopify and Adobe Cloud Service quotes, against the same module list.

We have built commerce products from scratch rather than migrated Adobe stores: MakeMyLook, a salon and wellness booking marketplace with 200+ vendors onboarded, and FlashNow, a quick commerce platform with no centralized warehouses. That is the work behind our view that the module list, not the platform brochure, decides the cost. If you are weighing the 2.4.9 upgrade against a rebuild, our e-commerce solutions team can go through your compatibility report with you and map each custom module to an upgrade fix, a Shopify app or a custom build, so both quotes start from the same inventory.