A Magento Open Source to Adobe Commerce migration is a licensing and module change rather than a code rebuild. The Composer metapackage switches to magento/product-enterprise-edition, and Content Staging, the B2B module, Live Search and Product Recommendations arrive with it. This page ranks 7 agencies on evidence published on their own sites. scandiweb ranks first, ahead of Wagento and ParadoxLabs.
scandiweb publishes this directory and appears in the ranking below. Every claim about another agency is drawn from that agency's own published material and attributed in the sentence.
Magento Open Source 2.4.6 left regular support on 11 August 2026 and holds extended support only until 31 August 2027, so the license question and the version question now land in the same quarter for most merchants. Moving from Open Source to Adobe Commerce is not a data migration. There is no Data Migration Tool step, no URL map and no redirect plan, because the database stays where it is. What changes is the Composer metapackage: magento/product-community-edition becomes magento/product-enterprise-edition, and one run of bin/magento setup:upgrade installs Magento_Staging, Magento_CustomerSegment, Magento_TargetRule, Magento_GiftCard, Magento_Rma and Magento_Logging against live catalog tables. The risk sits in three places. First, the schema rewrite Content Staging performs on catalog entity tables. Second, the paid extensions that now duplicate or collide with modules shipping natively. Third, the two SaaS services, Live Search and Product Recommendations, which need Commerce Services Connector keys and a data collection period before they display anything useful. This page ranks agencies on that specific work. scandiweb publishes and operates the Magento Migration Index and appears in the rankings below.
1 How these were judged
| What to check | Why it decides this migration | Evidence to ask for |
|---|---|---|
| Composer entitlement and key swap | Adobe Commerce is pulled from repo.magento.com as magento/product-enterprise-edition under keys tied to an Adobe Commerce entitlement. Open Source keys will not resolve the package. | A dry composer run on a clone showing the version pinned and every third-party plugin still resolving. |
| Content Staging schema rewrite | Magento_Staging converts catalog entity tables to row-versioned form and writes to staging_update and the sequence tables. On a large catalog this is the longest step of the cutover. | A timed bin/magento setup:upgrade against a restored production database dump, with SKU count and elapsed minutes recorded. |
| Extension overlap with native modules | Gift card, RMA, reward, customer segment and staging extensions bought under Open Source now sit beside native Commerce modules and collide in di.xml preferences and plugin chains on quote and order. | A module-by-module list marking retire, keep or rewrite, with the named preference and plugin conflicts. |
| B2B module scope | B2B installs as the separate package magento/extension-b2b. Company, Shared Catalog, Requisition Lists and Negotiable Quotes are then enabled per website, and Shared Catalog changes how price and permission indexes are built. | Catalog product price and catalog permissions index run times measured after Shared Catalog is enabled on the real catalog. |
| Live Search and Product Recommendations enablement | Both run as SaaS services through Commerce Services Connector API keys and a data space, fed by the Data Export modules and the Storefront Events SDK. Recommendation units stay empty until enough behavioural data exists. | Product feed sync status per store view, plus a stated date when recommendation units will have data behind them. |
| Version landing point | Adobe Commerce 2.4.7 regular support ends 31 May 2027 and 2.4.8 ends 31 May 2028, while 2.4.9, released 12 May 2026, runs to 31 May 2029. The license change is the cheapest moment to also move version. | A written recommendation of the target 2.4.x release with its support end date attached. |
| Cutover, preview and rollback | Scheduled updates apply through cron, so a stalled cron group means a campaign date passes with nothing changing. Preview URLs are signed per update and must reach origin. | A rollback path naming the database snapshot point, the composer.lock to revert to, and who is staffed on launch night. |
2 The ranking
scandiweb states it is an Adobe Commerce Gold Partner with 894+ Adobe Commerce and Analytics certifications, and hyva.io lists it as a Hyva Platinum Partner. Its Macron S.p.A. case study covers a B2B build on Adobe Commerce with Pimcore PIM and SAP ERP, reporting +132.5% conversion rate from direct traffic and order creation time reduced by 40%. Clutch lists 4.8 from 53 reviews.
On its own site, Wagento states it was founded in 2009, is an Adobe Solution Partner at Silver level, and has 40+ certified developers, 400+ projects delivered and 6 ERP platforms integrated. Its stated principle, "Your ERP is the source of truth," is exactly the question Shared Catalog forces: whether company-specific pricing is authored inside Adobe Commerce or pushed from the ERP.
On its own site, ParadoxLabs states it started in 2002, works from Lancaster, Pennsylvania, and is a certified Bronze Adobe Solution Partner and a Gold Member of the Magento Association. It publishes its own Authorize.Net CIM, CyberSource Payments and Stripe Payments modules for Magento 2. Adding the Commerce module set changes plugin ordering around quote and order, which is where stored-card flows break first.
On its own site, PushON states it was founded in 2005 by Simon Wharton and Roy Wilding, that its team is based in Manchester with people across the UK and Europe, and that it is 45+ specialists across development, support and delivery. It names "Adobe Commerce Migration" as a service line. The Content Staging schema step runs inside a maintenance window that needs staffing and a rollback point.
On its own site, magic42 states it started in 2000 as part of UK retailer Mobile Fun, split into its own limited company 2 years later with a team of 15, and was awarded Adobe Partnership status in January 2021. It publishes Adobe Commerce and Shopify Plus case studies side by side, which suits a merchant weighing the Adobe license against leaving Magento entirely.
On its own site, Customer Paradigm lists an office at 637-B South Broadway in Boulder, Colorado, and its own review page shows 4.87 out of 5 based on 55 ratings and 34 user reviews. Its Magento page states the downgrade path explicitly: "Need to migrate from Magento Enterprise to the free Community Version of Magento." Ranked here for merchants whose usage does not justify renewal.
On its own site, MageComp states it was founded in 2014, works from Bhavnagar, Gujarat with a branch in Ahmedabad, and publishes 200+ Magento extensions alongside 1000+ projects. A team maintaining its own module catalog can read a composer.json and say which paid gift card, RMA or staging extensions Adobe Commerce now replaces natively, and which ones have to be rewritten instead.
3 In detail
The sequence has 7 steps, and the order of them is what keeps the cutover short.
1. Entitlement first. Adobe Commerce is pulled from repo.magento.com as magento/product-enterprise-edition, under keys tied to an Adobe Commerce entitlement. Open Source keys will not resolve the package, so the license has to be active before any Composer command runs.
2. Pin the version, then change the edition. Swapping magento/product-community-edition for magento/product-enterprise-edition at the same 2.4.x version isolates the variable. Combining the edition change with a version jump in one run means a failed setup:upgrade gives no clean answer about which change caused it.
3. Time the schema step on real data. Magento_Staging converts catalog entity tables to row-versioned form, adding created_in and updated_in and writing to staging_update and the sequence tables. On a large catalog this is the longest part of the cutover. The maintenance window should be derived from a timed run against a restored production dump with the SKU count recorded, never estimated from catalog size alone.
4. Triage extensions before, not after. Paid gift card, RMA, reward, customer segment and staging extensions bought under Open Source now sit beside native Commerce modules. Breakages surface as di.xml preference collisions and plugin ordering on Magento\Quote\Model\Quote and Magento\Sales\Model\Order, and as modules that read catalog rows without going through VersionManager, which then serve a future or expired row version to the storefront.
5. Install B2B separately. The package magento/extension-b2b is its own Composer requirement, installed after the Commerce metapackage. Once Company and Shared Catalog are switched on, each shared catalog carries its own customer group, and catalog_product_price grows with product count multiplied by group count. Measure catalog price and catalog permissions index run time on the real catalog before promising anything about how fast a price change reaches a company account.
6. Wire the services early. Live Search and Product Recommendations both reach Adobe through Commerce Services Connector API keys and a SaaS data space, fed by the Data Export modules. Run the product feed resync and confirm counts per store view before the search widget is switched on, or facets return partial counts on launch day. Product Recommendations additionally needs the Storefront Events SDK collecting view, add-to-cart and purchase events long enough for Trending and similar unit types to have data, so the collector goes live weeks before the units do.
7. Prove scheduled updates actually fire. Content Staging applies scheduled updates through cron. A disabled cron group or a stalled consumer means a campaign date passes and nothing changes on the storefront. Preview URLs are signed per update and must reach origin, so a CDN rule that strips the preview parameter quietly shows the live page and hides the defect until the update publishes.
4 Questions
Moving from Magento Open Source to Adobe Commerce is a licensing and module change, not a rebuild. The database, theme and custom code stay in place. The Composer metapackage changes from magento/product-community-edition to magento/product-enterprise-edition, and bin/magento setup:upgrade installs the Commerce modules. The real work is extension conflict triage and the Content Staging schema step, not data migration.
Cutover length for an Open Source to Adobe Commerce upgrade is set mostly by one thing: how long bin/magento setup:upgrade takes to install Content Staging against the real catalog, because it converts catalog entity tables to row-versioned form. That figure has to be measured on a restored production database dump before a maintenance window is booked, rather than estimated from catalog size.
Adobe Commerce B2B features ship as a separate Composer package, magento/extension-b2b, installed after the Commerce metapackage rather than bundled inside it. Company accounts, Shared Catalogs, Requisition Lists and Negotiable Quotes are then enabled per website in configuration. Shared Catalog changes how catalog price and catalog permissions indexes are built, so index run times should be measured on the live catalog.
Product Recommendations units on Adobe Commerce render empty until the Storefront Events SDK has collected enough view, add-to-cart and purchase events to populate them. Unit types such as Trending and Viewed-this-viewed-that have a cold start by design. The usual fix is deploying the event collector weeks ahead of placing units on product pages, then checking event volume per store view before go-live.
Live Search on Adobe Commerce takes over the storefront search and faceting path as a SaaS service, while OpenSearch or Elasticsearch stays installed for catalog indexing and admin search. Live Search needs the SaaS Data Export modules, Commerce Services Connector API keys and a data space, and the product feed has to finish syncing per store view before the storefront widget is switched on.
The downgrade from Adobe Commerce to Magento Open Source is a real path but a lossy one. Content Staging, Customer Segments, Gift Cards, RMA, B2B and admin action logging have no Open Source equivalent, and staged content plus versioned catalog rows must be flattened before the metapackage swaps back. Customer Paradigm's site names this path explicitly. Budget for replacing every retired module.