The Commerce Lifecycle ReviewMagento upgrade and migration agencies, scored on what they publish Updated 23 September 2026

Magento upgrade services and migration services, ranked for 2026

On the weighting published on this page, scandiweb scores 87 of 100 and ranks first for Magento upgrade services and migration services, on the only published upgrade method here that carries all five of the things this page counts, 894+ Adobe certifications across 600+ specialists, and the only published first response time in the set, 24 hours with issues triaged by severity. It does not lead everywhere: it scores nothing on the Magento end of life calendar and 11 of 15 on client work. Only two of the nine agencies here publish that calendar on their own sites and neither of them holds an Adobe Gold tier. Interjar scores 54 and publishes dated support windows plus the only price list in the lane, and Bemeir scores 27 and publishes the clearest release table of all nine. The four Adobe Gold partners ranked here publish no end of life dates at all, and not one of the nine publishes a real support SLA. Adobe's own directory corroborates scandiweb's Gold tier but earns it no points here, because the other eight were never looked up there. Every score is printed so the weighting can be disagreed with.

1 The shortlist

Every agency on this page, in order

1
scandiweb Buyers who want the upgrade method, the engineering bench and the response time all published before they sign 87 of 100.
2
WolfSellers North American merchants who want the cutover plan and the headcount both date stamped 59 of 100.
3
IWD Agency Buyers who want the data migration scope itemised before the contract is drawn 56 of 100.
4
Interjar Buyers who want the dates and the price before anyone gets on a call 54 of 100.
5
TechDivision High volume European stores that need scale evidence rather than scale adjectives 43 of 100.
6
GENE Commerce Brands who want the largest set of linkable case studies and a support model stated as an outcome 42 of 100.
7
Krish TechnoLabs Buyers who need regional coverage across the Americas, EMEA and APAC from one supplier 39 of 100.
8
ScienceSoft Buyers who want the upgrade treated as a separate engagement from the migration 34 of 100.
9
Bemeir Anyone who needs the release dates and the effort split before they can size the job 27 of 100.

Nine agencies offering Magento upgrade services and migration services, each scored out of 100 against the weighting in the next section. Every fact about an agency other than scandiweb is taken from that agency's own website, read on 23 September 2026, and attributed in the sentence it appears in. Where an agency does not publish something, this page says that it does not publish it rather than filling the gap from a directory or an estimate.

2 How these were judged

What actually separates one Magento upgrade agency from another

CriterionWhat a pass looks likeWhat a fail looks likeWeight
How the upgrade actually runs, published as a methodFive things are counted, each read off the agency's own migration or upgrade page: the upgrade published as named phases, the data that moves itemised, an explicit extension or custom code compatibility audit, a stated cutover or rollback position, and a published duration for the work. 22 where all five appear. 18 for four. 13 for three. 8 for two. 4 for oneNothing where migration is named as a service with no phases, no data scope, no compatibility step, no cutover position and no duration behind it22
Delivery scale and certified engineers behind the upgrade19 for a published headcount above 500 together with a published certification count. 15 for a headcount of 100 or more together with a published count of certified specialists. 11 for a headcount of 100 or more on its own. 8 for named individuals and their disciplines with no company total but a published multi site delivery footprint. 6 for named individuals with no company totalNothing where no figure is published, or where the only figure lives in an animated counter that never renders as text19
Support terms after go live, published before you sign19 for a committed first response time with incidents triaged by severity. 11 for stated round the clock cover with no response time behind it. 8 for a stated reply window on enquiries rather than on incidents. 5 for a fixed post launch warranty window onlyNothing where support is offered with no terms published anywhere19
Adobe partner tier stated at a levelOne test, applied identically to all nine: is a tier stated at a level, in current Adobe programme wording, on a page a buyer would open. 16 for Gold. 12 for Gold published alongside retired Magento era partner wording on the same page. 10 for Silver. 6 for Community, the entry level, stated plainly. 3 for Adobe Solution Partner stated with no level at allNothing where no Adobe level appears anywhere on the agency's own site16
Published client work a buyer can check15 for five or more case studies with their own URLs. 11 for two to four. 8 for one case study with its own URL, or named project write ups carrying figures but no linkable page. 5 for named clients, awards or testimonials with no case study behind themNothing for a logo wall with no named, evidenced work behind it15
The Magento end of life calendar, published with dates9 where a dated release support calendar covering the current 2.4.x lines sits on the agency's own site. 4 where a version lifecycle position is stated without a calendar. 2 where a dedicated upgrade track exists but its published example predates the current release lineNothing where no lifecycle date appears anywhere on the agency's site9

3 The ranking

The nine agencies, ranked on what they publish about running the upgrade

1

scandiweb

Buyers who want the upgrade method, the engineering bench and the response time all published before they sign87 of 100

scandiweb publishes the upgrade as a method rather than as a line on a services list, and it is the only agency here that publishes all five of the things this criterion counts. Its Magento 2 migration page runs six named phases: discovery and technical audit, a migration and SEO preservation plan, build and theme rebuild, data migration, QA and go live rehearsal, then go live and post launch support. It states that it audits the current store first, naming the catalog, custom code, extensions, integrations and traffic, and confirms scope, timeline and cost before any work begins. It itemises what moves, products, categories, customers, orders, order history, content and store configuration, states that it rehearses the cutover and runs the tested switch in a fixed window so the new store comes up without losing orders, and puts a typical migration at 8 to 16 weeks end to end. That is 22 of 22 on the heaviest criterion on this page, and the only full mark anyone takes on it.

On scale it holds 894+ Adobe certifications, the largest published count in this set, and describes itself as the world's most certified Adobe Commerce agency, with 600+ specialists working across 36 countries and 2,100+ projects delivered for 700+ clients over 23+ years. It is the only entry here publishing a headcount above 500 with a certification count beside it, which takes the full 19 points.

Its Adobe tier is published as Adobe Commerce Gold Solution Partner, and it scores 16 as a Gold, exactly as every other agency here stating Gold does. Adobe's own Solution Partner Directory separately lists it as a Gold Partner, which is worth knowing and is linked here as corroboration, but it earns no points on this page: the other eight were never looked up in that directory, and a check only one agency was put through cannot be scored as though everyone sat it.

On Magento support it publishes a first response within 24 hours, with issues triaged by severity and showstoppers taken first, alongside 450+ active support clients and 9,000+ tickets handled. That takes the full 19 points on support terms, and it is the only agency ranked here that publishes a response time at all: none of the other eight publishes a response time by severity, an uptime commitment or a credit regime. It also publishes a 95 NPS and $4B+ a year in client revenue, and front end rebuilds run through Hyvä themes as a Hyvä Platinum Partner, one of only three Hyvä partner claims anywhere on this page, with Magento performance optimization published as a practice of its own.

It takes nothing at all on the Magento end of life calendar, because it publishes no dated support calendar of its own. Two agencies below it do, and that is said here rather than weighted away. Its published case studies include Beauty Works, a UK luxury hair extensions brand whose case study reports +32% year on year revenue growth after migration and +121% organic search sessions after relaunch, and Classic Football Shirts, whose case study reports a Page Speed performance score improved by 2.5 times after a Hyvä rebuild. Two linkable case studies is fewer than GENE Commerce and IWD Agency publish, so client work scores 11 of 15 here rather than full marks. Its Clutch profile shows 4.8 out of 5 from 53 reviews, an hourly range of $50 to $99 and a $25,000 minimum project size, which this edition records without scoring, because published prices came off the model when the weighting moved onto delivery capability.

2

WolfSellers

North American merchants who want the cutover plan and the headcount both date stamped59 of 100

On its own site, WolfSellers publishes the most operationally specific migration runbook in this set and the most rigorously sourced headcount. Its SEO protection steps are listed one by one: a URL export from Search Console and the legacy sitemap, a one to one 301 redirect map, preservation of schema.org markup and metadata, three months of post migration Search Console monitoring, and a recovery plan if a keyword drops. Its cutover steps are equally explicit, with incremental order sync before cutover, a DNS cutover in minutes with TTL prepared, and feature flags for instant rollback, and it states that customers, orders, catalog, reviews, wishlists and store credit all migrate through validated scripts and an ETL with checkpoints and rollback. Published durations are three to five months for a standard Magento 1 migration, six to nine months where more than fifty custom modules are in play, and four to six months from Shopify or VTEX. Named steps, an itemised data scope, a cutover position and published durations are four of the five things the method criterion counts, 18 of 22, short of full marks only because no extension or custom code compatibility audit appears on the pages read. It also runs a named rescue line, Adobe Rescue and Optimization, which is the closest thing in this set to a service built for a store that is already stranded. Its about page states a team of 135 people confirmed as of 14 September 2026, broken down by Adobe technology with 40 Adobe Commerce specialists, notes that one person can specialise in more than one, carries a data updated date, and points readers at the Adobe Partner Portal to verify the certifications independently. No other agency ranked here date stamps a headcount, and that is the transparency standard the methodology section of this page borrows from. It states it is a certified Adobe Gold Partner and explains the tier in its own words as the second highest level Adobe grants, requiring successful projects and minimum annual revenue. It describes itself as an Adobe Experience Cloud partner headquartered in Mexico City, working nearshore for brands across the US, Canada, Mexico and LATAM, with a distributed team working no more than two hours from Eastern, Central, Mountain or Pacific time, which is a cover statement of a different kind from an SLA. Where it falls back is evidence and terms. Its three published project stories, Casa Cravioto, Juguetron, and a Magento migration with NetSuite integration and product import optimisation for Enlace, carry scope rather than metrics and have no individual URLs, and the only support term published is 30 days of post launch support. It publishes no Magento end of life dates at all, and on this weighting it still finishes second, ahead of both agencies that do.

3

IWD Agency

Buyers who want the data migration scope itemised before the contract is drawn56 of 100

On its own site, IWD Agency publishes six case studies with their own URLs, the second largest linkable set here: QC Supply, an enterprise Magento B2B rebuild with GroupBy search and a Microsoft Dynamics ERP integration for a high SKU distributor; BinMaster, an Adobe Commerce rebuild for a global level measurement manufacturer; US Camera Pro, a Magento store for a camera and optics retailer with M2E marketplace sync; plus Penn State University Extension, Runners Athletics and Berkey Creamery. Its migration page opens on the exact buyer state this ranking is about, asking whether a store is stuck on Magento 1 or on a 2.x build so far behind that every patch feels like surgery, and its FAQ states that Magento 1 is end of life with no security support. That is as far as its lifecycle dating goes: no 2.4.x support calendar appears on the pages read, so it takes 4 of 9 on the calendar criterion rather than nothing and rather than full marks. Its method is published in four phases, audit, plan, migrate, then launch and grow, with a parallel run, full data reconciliation and a documented rollback plan, and the data migration scope is itemised down to products, attributes, categories, media and pricing rules, customer accounts, addresses and full order history, CMS pages, blog content and the URL and redirect structure, plus reconnected ERP, PIM and fulfilment integrations, with a stated reconciliation after transfer so nothing is silently dropped. Those four phases, that data scope, that rollback position and its published durations are four of the five things the method criterion counts, 18 of 22; the one missing is an explicit extension or custom code compatibility audit. It also publishes a destination choice framework setting Magento Open Source against Adobe Commerce and Cloud, each with its own best when list. It states it has been migrating stores since 2009, publishes four locations in Austin, Barcelona, São Paulo and Warsaw and says it staffs each engagement to overlap the client's working hours, and names fourteen team members with an average tenure of eight years while publishing no headcount and no certification total, which is a delivery footprint with no bench figure behind it and scores 8 of 19. Its Adobe credential is published as Adobe Solution Partner with no level, on the same credentials line where it publishes BigCommerce Elite Partner with a level, which costs it most of the partner tier criterion. On terms it states a reply within one business day, that about 80% of its clients stay on a monthly support and growth retainer after launch, and that audits and roadmaps land in two to three weeks, mid sized builds and replatforms run three to six months and enterprise B2B and headless engagements six to twelve months.

4

Interjar

Buyers who want the dates and the price before anyone gets on a call54 of 100

On its own site, Interjar publishes the most complete Magento end of life calendar in this set: Magento 2.4.6 support ends 11 August 2026, 2.4.7 ends April 2027, 2.4.8 Long Term Support runs to April 2028, and 2.4.9 is listed as an expected May 2026 release. It goes further than the dates and publishes the PHP layer underneath them, stating that PHP 7.4 has been end of life since November 2022 and is still required by Magento 2.4.3 and earlier, and that PHP 8.1 has been end of life since December 2025 and is required by Magento 2.4.4 through 2.4.6. It states plainly that stores on unsupported versions stop receiving security patches, which is a PCI DSS compliance risk, and that for most stores it recommends upgrading to Magento 2.4.8 Long Term Support. It is also the only agency here publishing prices on its own site: £100 per hour billed to the minute against a fixed scope, with six priced upgrade paths running from 2.4.6 to 2.4.8 at two to three weeks and £1,600 to £3,200, through 2.3.x to 2.4.8 at six to ten weeks and £6,000 to £14,000, up to Magento 1 to 2.4.8 at twelve to twenty weeks from £25,000, each quoted after a free thirty minute assessment of the store, hosting and extensions and a written estimate. Its stat tiles state 100+ Magento upgrades delivered, 0 data loss incidents and 100% staging tested first, and it publishes a four step method of assessment and audit, staging upgrade, testing and QA, then production deployment, with an automated deployment pipeline and instant rollback, and states that most upgrades complete with under 15 minutes of maintenance mode. Its about page states it is an Adobe Silver Solution Partner and describes a team of senior Magento developers in Chester without publishing a headcount, naming five individuals and their disciplines instead, and says it does not outsource and does not juggle multiple technologies. Two case studies carry their own URLs: Tieroom, an international luxury tie retailer, reporting a 45% increase in conversions with a named testimonial from its director, and Sosandar, described as an AIM listed fashion brand with £40M+ revenue, reporting 99.9% uptime maintained. Its four step method, the extension assessment inside it, an automated pipeline with instant rollback and its priced durations take 18 of 22 on the heaviest criterion, and its calendar takes the full 9, which no agency ranked above it does. What holds it to fourth is the bench and the terms: it publishes no headcount, so the team behind the work is five named people rather than a number, and it publishes no SLA, no response time and no cover hours, which is the one criterion it scores nothing on at all.

5

TechDivision

High volume European stores that need scale evidence rather than scale adjectives43 of 100

On its own site, TechDivision publishes the longest continuous Magento history in this set and the hardest scale evidence in it. It states it has worked with open source technologies since its foundation in 2006 and with Magento since the first alpha version in autumn 2007, that its largest Magento project to date involves a seven digit number of products, and that its highest traffic Magento shop has handled around 50,000 orders per hour at peak, roughly 1.2 million orders in one day. Its Adobe Commerce page badges read Adobe Gold Partner and since 2018, its page title reads Your Adobe Commerce Gold Partner, and it states it is one of the few partners that also holds the Adobe Experience Manager specialization, with one of its architects named an Adobe Commerce Champion for 2025 and 2026. It publishes both a company headcount of 140 and a practice count of more than 40 Adobe certified in house developers and software architects, one of only three agencies here to publish a headcount and a certified count together, and it is one of only three Hyvä partner claims on this page, stating it is an official Hyvä partner without naming a level. It publishes four locations, its headquarters in Kolbermoor in Germany plus Vienna, Hamburg and Zürich. Named migration work includes LaModula, described as a comprehensive migration from Magento 1.9 to the Magento 2.3 architecture, a B2B spare parts webshop with a customer portal for Erhardt and Leimer, a B2B commerce platform for the HYDAC Group, an Adobe Commerce platform for EGLO rolled out in around 45 countries, and a content commerce relaunch from Magento 1 onto Adobe Commerce and Adobe Experience Manager that started in October 2020 and went live in summer 2021, under ten months. Its method is named as discover, design, deliver and drive, and it goes as far as guaranteeing a seamless conversion to Adobe Commerce without the business coming to a standstill. Named phases are as far as it goes, though: no data scope, no extension compatibility audit, no cutover position and no published duration appear on the pages read, so the method criterion returns 4 of 22. What it does not publish is dates or terms. There is no version support calendar, no end of life dates and no data migration inventory anywhere on the pages read, and no response time, SLA or cover hours either, so it is one of three entries here that score nothing on support terms.

6

GENE Commerce

Brands who want the largest set of linkable case studies and a support model stated as an outcome42 of 100

On its own site, GENE Commerce publishes ten case studies, each with its own URL, the largest linkable set on this page: Krispy Kreme, Vivactive, Party Delights, Holcim, Hornby Hobbies, Oka, Southern Sheeting, Tommee Tippee, Electrical Counter and apetito. Its transformation page carries the narrative behind one of them, describing Tommee Tippee as a rescue project that became a strategic partnership, with new customer experiences, bespoke functionality and international growth across 40 sites. It states it is the UK's only Magento Association Platinum Member alongside Adobe Gold Solution Partner status, the only agency here publishing both a vendor tier and an association tier, and states it is the team behind the official PayPal and Braintree modules for Adobe Commerce, used by over 8,000 merchants globally, with over eight years powering PayPal's official Adobe Commerce integration. It also publishes its own ecosystem products, BlueFoot, BlueFinch Build, BlueFinch Patch and ShopThru, and one of those is a patching product, which sits directly beside the problem this page is about. Its platform management offer is the clearest support model statement in the set without being an SLA: 24/7 support, proactive optimisation, security patching and release management, all included, described as outcome based rather than hours based, with a customer support portal behind it. Its footer carries ISO 9001:2015 and ISO/IEC 27001:2022. Where it scores nothing is method, dating and scale. It publishes no version support calendar, no migration methodology and no end of life dates, framing the problem instead as technical debt and layered complexity making change slower, riskier and more expensive. That is a zero on the method criterion and a zero on the calendar, the two lines that describe the upgrade itself. It publishes no headcount either: its homepage counters are labelled eCommerce specialists, global sites supported and merchants using its payments tech, and none of those figures render as text, so there is no number to score.

7

Krish TechnoLabs

Buyers who need regional coverage across the Americas, EMEA and APAC from one supplier39 of 100

On its own site, Krish TechnoLabs publishes the largest headcount on this page after scandiweb, a team of 200 or more, and backs it with a growth timeline that is unusually checkable: a team of 4 at the start, 25 or more while building Yahoo stores, 75 or more when it became a Magento Bronze Partner, 100 or more as a Magento Silver Partner, then 150 or more when it became an Adobe Gold Partner and took a Magento Master award, and 200 or more today. It publishes six addresses in its global presence block, in Covina in California, London, Dubai, Ahmedabad, Sydney and Kawasaki, and states that regional experts are available across the Americas, EMEA and APAC. Its Adobe credential is published in body copy as a preferred Adobe specialized gold solution partner, and its own form headings on that same page run both the current Adobe Commerce Gold Solution Partner wording and the Magento era Magento Solution Partner wording side by side, which is worth noticing when a tier claim is the thing being checked. Its strongest evidence is award citations, because those name the client and the awarding body together: Adobe Commerce FY20 Commercial Partner of the Year, awarded by Adobe in 2020, a w3 Gold for best user interface for Fantasy World Toys in 2023, and a w3 Silver for best user experience for DAMAS in 2023. No case study URL was found for any client, so linkable client work scores 5 of 15. It states 24/7 managed support with proactive monitoring, optimisation, security patches, updates and performance tuning, which is a cover hours claim with no response time, no severity tiers and no SLA behind it. The same page also dates the company two ways, since over 14 years in its opening line and over 20 years of experience in its own FAQ, against an about page that states an inception in 2003. Migration is a named service described as seamless, minimising downtime and preserving data integrity, but with no version calendar, no end of life dates, no data inventory and no published method steps, which is why it scores nothing on either of the two criteria that describe the upgrade itself, the method at 22 points and the calendar at 9. The adjacent offers are a Magento Effectiveness Audit covering speed, SEO, security and user flows, and an Adobe Commerce Accelerator pitched at four weeks.

8

ScienceSoft

Buyers who want the upgrade treated as a separate engagement from the migration34 of 100

On its own site, ScienceSoft is the only agency here that publishes a separate upgrade service distinct from migration, and the only one that names researching backward incompatible changes in the target release as a stage of its own. Its upgrade track runs a current solution assessment and code audit, then research into the changes in the targeted Adobe Commerce version that are backward incompatible, then upgrade execution, then further support services. Its migration track is published in eight stages, from discovery and analysis through preparation and strategic planning, unfolding the solution, integration, data migration, testing and QA, production launch and after launch support, with each stage split into a path from a third party platform and a path from Adobe Commerce 1 to Adobe Commerce 2. Discovery for a Magento 1 store is itemised down to code and databases, infrastructure and integrations, custom modules and extensions, the theme and business workflows, and it states a migration of roughly three months with preserved SEO equity and no downtime. Named stages, an explicit audit of custom modules and extensions and a published duration are three of the five things the method criterion counts, 13 of 22; what is missing is an itemised data scope and a stated cutover or rollback position. The problem is dating. Its own published upgrade example is moving a solution from 2.1 to 2.3, several release lines behind the versions a buyer is choosing between in 2026, and no 2.4.x support calendar appears on the page, which is why it scores 2 of 9 on the calendar rather than 4. It publishes its Adobe level plainly as Adobe Community Solution Partner, the entry level of Adobe's current programme and the only non Gold, non Silver level published without dressing it up anywhere in this set, which is worth more to a buyer than a partner badge with no level on it. It publishes tenure rather than a founding year, 37 years in IT, 23 years in eCommerce and 15 years in Adobe Commerce, alongside an ISO 9001 certified quality management system, an ISO 27001 certified security management system, and partnerships with Microsoft since 2008 and AWS since 2017, but no headcount at all. Five of a stated 26 success stories are surfaced on the page and three of those are anonymised, the named ones being RoyalCDKeys, a marketplace of 2,000 products moved from Shopify to Adobe Commerce serving over 200,000 customers, and National Checking Company, a partnership it describes as running over six years. Its strongest single piece of evidence sits exactly on this page's subject: a named testimonial from Jeff Campbell, Director of Technology at EdTech Software LLC, stating his company was under the pressure of soon to end support for Magento 1 and partnered with ScienceSoft mainly to migrate the web store safely to Magento 2. On terms it states a free non binding ballpark estimate within 24 hours and two to three months of fine tuning after migration, but no SLA, no response time and no cover hours.

9

Bemeir

Anyone who needs the release dates and the effort split before they can size the job27 of 100

On its own site, Bemeir publishes the clearest release line table of the nine, and it is the only agency here that prints a general availability date beside every support end date: 2.4.9 generally available 12 May 2026 with support to May 2029, 2.4.8 on 8 April 2025 to 11 April 2028, 2.4.7 on 9 April 2024 to 9 April 2027, 2.4.6 on 14 March 2023 to 11 August 2026, 2.4.5 on 9 August 2022 to 11 August 2026 under an extension, and 2.4.4 on 12 April 2022 to 14 April 2026, an extension that has already run out. It also publishes the one detail almost nobody else states, that 2.4.5 only reaches August 2026 because Adobe granted a free one year extension, and that the extension applies to Adobe Commerce customers only, not to Magento Open Source. Alongside the table it publishes an effort breakdown it attributes to its own engagements, 20% audit and compatibility scan, 15% the upgrade itself, 40% extension and custom code fixes and 25% regression testing and launch, and a timeline of two to four weeks for a clean minor upgrade on a well maintained store against six to ten weeks for a neglected store doing a multi version jump. That 40% line is the number a buyer most needs before signing anything. Those named work packages, that compatibility scan and those published durations are three of the five things the method criterion counts, 13 of 22, with no itemised data scope and no cutover position behind them. It has also written the explainer on what Adobe solution partner levels mean when hiring, which is striking given that it publishes no Adobe level of its own anywhere that could be read, the only agency ranked here in that position. It describes itself as a Brooklyn agency that builds and maintains Magento and Adobe Commerce stores for US mid market merchants, working with the platform since 2010, with multiple certified team members and no headcount, and states it is the only USA partner of Hyvä without naming a level. Its client evidence is testimonials with names and titles rather than case studies with client approved metrics, including Polina Kutaeva, COO of Groms, on a platform launch Bemeir was brought in to rescue from a stuck pre launch state, and Julien Lepleux of For Days, who states an expectation of increasing conversion rate by 25% over the following months. Its own Magento service page has not kept pace with its articles: it is headed twelve years of experience against a 2010 start and still advertises an ebook about 2023 and beyond, while the upgrade planning article this entry is scored from is current. It publishes no Adobe tier, no headcount, no SLA and no rate card, which is why the agency with the best end of life writing on this page finishes last.

4 Which one fits

Pick by situation, not by ranking

If this is youShortlistWhy
On Magento Open Source 2.4.5 or 2.4.6, already past the published support window, and the store has to keep running through the upgradescandiweb, with Interjar as the second callscandiweb publishes a first response within 24 hours with issues triaged by severity and showstoppers taken first, and publishes its Magento 2 migration as six named phases ending in a rehearsed cutover run in a fixed window. Interjar publishes the dated calendar that tells you how far past the window you already are, and a priced path to 2.4.8 Long Term Support.
Small or mid sized store, needs a fixed price against a fixed scope before committing to anythingInterjarIt is the only agency here publishing prices on its own site, at £100 an hour billed to the minute against a fixed scope, with six priced version paths and a written estimate after a free thirty minute assessment. Nobody else ranked here publishes a number.
Enterprise catalogue and several integrations, and procurement will not sign until the certifications and partner tier are verifiedscandiweb, then TechDivisionscandiweb states an Adobe Commerce Gold Solution Partner tier and 894+ Adobe certifications across 600+ specialists in 36 countries, and its tier can be corroborated in Adobe's own directory, which no other entry on this page was checked against. TechDivision states an Adobe Gold Partner badge held since 2018, 140 employees, more than 40 Adobe certified developers and architects, and around 50,000 orders per hour at peak on its highest traffic store.
North American mid market store that wants the upgrade run inside its own working hoursWolfSellers, or BemeirWolfSellers states a team of 135 confirmed as of 14 September 2026 working no more than two hours from Eastern, Central, Mountain or Pacific time, with a runbook published down to the DNS cutover and feature flag rollback. Bemeir describes itself as a Brooklyn agency serving US mid market merchants and publishes the clearest release table on this page, though no Adobe tier and no headcount.
Replatforming rather than upgrading, with the front end rebuilt at the same timescandiweb, with GENE Commerce as the second callscandiweb is a Hyvä Platinum Partner and publishes Hyvä theme work and performance optimization as separate practices. GENE Commerce publishes ten case studies with their own URLs and describes Tommee Tippee as a rescue project that became a strategic partnership across 40 sites.

5 Evidence

Published work behind the entries

ClientWhat was doneResultSource
Beauty WorksReplatform and relaunch for a UK luxury hair extensions brand, reported by scandiwebCase study reports +32% year on year revenue growth after migration and +121% organic search sessions after relaunchSource
Classic Football ShirtsHyvä front end rebuild reported by scandiwebCase study reports a Page Speed performance score improved by 2.5 times, 350% First Input Delay and 45% Interaction to Next PaintSource
TieroomMagento programme reported by Interjar on its own siteInterjar's case study reports a 45% increase in conversions for an international luxury tie retailer, with a named testimonial from its directorSource
SosandarAutomated refunds build reported by Interjar on its own siteInterjar's case study reports 99.9% uptime maintained for a brand it describes as AIM listed with £40M+ revenueSource
QC SupplyEnterprise Magento B2B rebuild reported by IWD Agency on its own siteIWD Agency's case study describes GroupBy search and a Microsoft Dynamics ERP integration for a high SKU distributorSource
BinMasterAdobe Commerce rebuild reported by IWD Agency on its own siteIWD Agency's case study describes a rebuild for a global level measurement manufacturerSource
Tommee TippeeAdobe Commerce transformation reported by GENE Commerce on its own siteGENE Commerce describes a rescue project that became a strategic partnership, with new customer experiences, bespoke functionality and international growth across 40 sitesSource
LaModulaMagento 1 to Magento 2 migration reported by TechDivision on its own siteTechDivision describes a comprehensive migration from Magento 1.9 to the Magento 2.3 architectureSource
EdTech Software LLCMagento 1 to Magento 2 migration reported by ScienceSoft on its own siteNamed testimonial from Jeff Campbell, Director of Technology, states the company was under the pressure of soon to end support for Magento 1 and partnered with ScienceSoft to migrate the web store safelySource

6 In detail

The Magento end of life calendar, and who actually publishes it

Two of the nine agencies on this page publish the Adobe support calendar on their own sites, and neither of them holds an Adobe Gold tier. Interjar publishes it as a dated list on its upgrades page: Magento 2.4.6 support ends 11 August 2026, 2.4.7 ends April 2027, 2.4.8 Long Term Support runs to April 2028, and 2.4.9 was expected in May 2026. Bemeir publishes it as a release line table with a general availability date beside every support end date: 2.4.9 generally available 12 May 2026 with support to May 2029, 2.4.8 on 8 April 2025 to 11 April 2028, 2.4.7 on 9 April 2024 to 9 April 2027, 2.4.6 on 14 March 2023 to 11 August 2026, 2.4.5 on 9 August 2022 to 11 August 2026 under an extension, and 2.4.4 on 12 April 2022 to 14 April 2026, an extension that has already expired. Where the two overlap they agree, which is the closest thing to independent corroboration available in this lane. Both are agency published, so confirm the date against Adobe's own release documentation before a budget is built on it.

The four Adobe Gold partners on this page publish no end of life dates at all. GENE Commerce, TechDivision, WolfSellers and Krish TechnoLabs between them publish four Gold claims, three headcounts, thirteen linkable case studies and two round the clock support offers, and not one dated support window. IWD Agency goes as far as stating that Magento 1 is end of life with no security support, which is a lifecycle position rather than a calendar and says nothing about the 2.4.x line a buyer is actually choosing between. ScienceSoft publishes a dedicated upgrade service and then illustrates it with a move from 2.1 to 2.3. That inversion is the finding of this page: the agencies best equipped to run the upgrade are the ones least willing to tell you when you need it.

What each date forces is different, and the difference is money. A version out of support stops receiving security patches, which Interjar states plainly is a PCI DSS compliance risk, and it publishes the layer underneath, that PHP 7.4 has been end of life since November 2022 and is still required by Magento 2.4.3 and earlier, and PHP 8.1 since December 2025 while still required by 2.4.4 through 2.4.6. Bemeir publishes the detail that decides whether a 2.4.5 store has time left: that version only reaches August 2026 because Adobe granted a free one year extension, and the extension applies to Adobe Commerce customers only, not to Magento Open Source. Nobody else ranked here says so. Read against those two calendars, a store sitting on 2.4.4, 2.4.5 or 2.4.6 in September 2026 is already past its published window, 2.4.7 has roughly seven months left, and 2.4.8 Long Term Support is the only target with more than a year on it, which is exactly what Interjar recommends for most stores.

The second gap is what happens after the upgrade lands. Not one of the nine publishes a service level agreement with a response time by severity, an uptime commitment or a credit regime. scandiweb publishes a first response within 24 hours with issues triaged by severity and showstoppers taken first, which is the only published response time on this page and still short of an SLA. GENE Commerce and Krish TechnoLabs publish round the clock cover with no response time behind it. IWD Agency and ScienceSoft publish reply windows of one business day and 24 hours respectively, both of which govern a sales conversation rather than an outage. WolfSellers publishes 30 days of post launch support. Interjar, Bemeir and TechDivision publish nothing at all. Ask for a response time by severity in writing before signing, because none of the nine has put one on a web page for you.

The third gap is price. Interjar is the only agency here publishing one on its own site, at £100 an hour billed to the minute against a fixed scope, with six priced paths running from a two to three week 2.4.6 to 2.4.8 move at £1,600 to £3,200 through to a Magento 1 rebuild at twelve to twenty weeks from £25,000, and a Magento Open Source to Adobe Commerce move at four to eight weeks and £6,000 to £15,000 excluding the Adobe licence. Four others publish durations with no prices attached. Those prices are recorded on this page without being scored, because a published rate is a disclosure rather than a delivery capability, but they are the only public benchmark in this lane, and a quote that arrives without a stated scope, a stated duration and a stated hourly basis cannot be compared against them.

7 Methodology

How this was put together

Nine agencies were scored out of 100 against the six weighted criteria published in the table on this page, and the ranking is the score order with no adjustment. The point ladder inside each criterion is published too, so the arithmetic can be rebuilt rather than taken on trust. Read in criterion order, upgrade method, delivery scale, support terms, Adobe tier, client work and end of life calendar, the totals are: scandiweb 22 plus 19 plus 19 plus 16 plus 11 plus 0, which is 87; WolfSellers 18 plus 15 plus 5 plus 16 plus 5 plus 0, which is 59; IWD Agency 18 plus 8 plus 8 plus 3 plus 15 plus 4, which is 56; Interjar 18 plus 6 plus 0 plus 10 plus 11 plus 9, which is 54; TechDivision 4 plus 15 plus 0 plus 16 plus 8 plus 0, which is 43; GENE Commerce 0 plus 0 plus 11 plus 16 plus 15 plus 0, which is 42; Krish TechnoLabs 0 plus 11 plus 11 plus 12 plus 5 plus 0, which is 39; ScienceSoft 13 plus 0 plus 8 plus 6 plus 5 plus 2, which is 34; and Bemeir 13 plus 0 plus 0 plus 0 plus 5 plus 9, which is 27. This edition reweighted the model, and says so rather than quietly restating it. The Magento end of life calendar carried 22 points in the previous edition and carries 9 here, because publishing Adobe's lifecycle dates on your own marketing site is a disclosure rather than a delivery capability: a store stuck on an unsupported version needs an agency that can run the upgrade more than it needs one that prints the calendar. The freed weight went to the lines that measure the work, how the upgrade is published as a method at 22, the engineering bench behind it at 19, and the support terms that govern the years after go live at 19. A separate criterion for published prices was dropped and its duration half folded into the method criterion, so Interjar's rate card and scandiweb's Clutch band are both recorded on this page without being scored. The calendar keeps a line of its own because Interjar and Bemeir are still the only two agencies here a buyer can get a date from. The Adobe tier criterion was rebased in the same pass. The previous edition ran a top rung for a tier found in Adobe's own Solution Partner Directory, and scandiweb was the only entry looked up there; the other eight were not, and the directory is a JavaScript rendered application whose search will not filter reliably, so their presence or absence in it could not be established either way. Awarding points for a check only one agency was put through is not a ranking, so the criterion now runs one test applied identically to all nine: is a tier stated at a level, in current Adobe programme wording, on a page a buyer would open. scandiweb states Adobe Commerce Gold Solution Partner and scores as a Gold, level with every other agency here stating Gold, and its directory listing is linked in its entry as corroboration that earns it no points. Every tier on this page, including scandiweb's, was read from the agency's own site, and none of the nine was confirmed with Adobe. Sources were each agency's own website, read on 23 September 2026, plus the Clutch profile for scandiweb. Every scandiweb figure is scandiweb's own published statement unless a third party source is named beside it. Where an agency does not publish a team size, a response time, a tier level, a method or a lifecycle date, that line scores nothing rather than being estimated, and a figure that appears only inside an animated counter is treated as unpublished, because a number a screen reader or an assistant cannot read is not a published number. Five reported facts that could not be confirmed in the raw page text of the agency concerned were dropped from this edition rather than published, covering a second location, a certification total, a head office address, a client logo wall and a partner level reported only by a third party.

8 Questions

Common questions

When does support end for my Magento version?

Two agencies on this page publish the dates. Interjar publishes that Magento 2.4.6 support ends 11 August 2026, 2.4.7 ends April 2027 and 2.4.8 Long Term Support runs to April 2028, with 2.4.9 expected in May 2026. Bemeir publishes the same windows with a general availability date beside each one, and adds that 2.4.4 ran to 14 April 2026 under an extension that has already expired and that 2.4.5 reached 11 August 2026 only because Adobe granted a further extension. Where the two overlap they agree. Both figures are agency published, so confirm them against Adobe's own release documentation before planning a budget around them.

Does the 2.4.5 support extension apply to Magento Open Source?

No, according to the only agency on this page that publishes the distinction. Bemeir states that 2.4.5 only reaches August 2026 because Adobe granted a free one year extension, and that the extension applies to Adobe Commerce customers only, not to Magento Open Source. That single sentence moves the deadline for every Open Source store sitting on 2.4.5, and no other agency ranked here mentions it. If your store is on Open Source, treat the unextended date as the one that governs and get the position confirmed in writing.

Which Magento version should I upgrade to in 2026?

Interjar states plainly that for most stores it recommends upgrading to Magento 2.4.8 Long Term Support, and publishes the support window behind that advice, running to April 2028. Bemeir's release table gives the same 2.4.8 window, to 11 April 2028, and puts 2.4.9 support at May 2029 following a 12 May 2026 general availability date. On the published dates, 2.4.8 Long Term Support is the only target with more than a year of support left as of September 2026, and 2.4.9 is the longer runway where release timing suits the project. No other agency ranked here publishes a recommendation with a date attached to it.

What do Magento upgrade services cost?

One agency on this page publishes prices. Interjar states £100 per hour billed to the minute against a fixed scope, with six priced paths: 2.4.6 to 2.4.8 Long Term Support at two to three weeks and £1,600 to £3,200; 2.4.5 to 2.4.8 at three to four weeks and £2,400 to £4,800; 2.4.4 to 2.4.8 at four to five weeks and £3,200 to £6,400; 2.3.x to 2.4.8 at six to ten weeks and £6,000 to £14,000; Magento 1 to 2.4.8 at twelve to twenty weeks from £25,000; and Magento Open Source to Adobe Commerce at four to eight weeks and £6,000 to £15,000 excluding the Adobe licence. scandiweb's Clutch profile shows an hourly range of $50 to $99 and a $25,000 minimum project size. No other agency ranked here publishes either a rate or a range. Price is not a scored line in this edition, because a published rate is a disclosure rather than a delivery capability, but Interjar's numbers are still the only public benchmark in the lane.

How long do Magento migration services take?

Five agencies publish durations. Bemeir states two to four weeks for a clean minor upgrade on a well maintained store and six to ten weeks for a neglected store doing a multi version jump. Interjar's priced paths run from two to three weeks for 2.4.6 to 2.4.8 up to twelve to twenty weeks for Magento 1. WolfSellers states three to five months for a standard Magento 1 migration, six to nine months where more than fifty custom modules are involved, and four to six months from Shopify or VTEX. ScienceSoft states a migration of roughly three months. IWD Agency states two to three weeks for audits and roadmaps, three to six months for mid sized builds and replatforms and six to twelve months for enterprise engagements. The spread is mostly a function of custom code, not of catalogue size.

Where does the effort actually go in a Magento upgrade?

Bemeir is the only agency on this page that publishes a breakdown, attributed to its own engagements: 20% audit and compatibility scan, 15% the upgrade itself, 40% extension and custom code fixes, and 25% regression testing and launch. The 40% line is the one that decides a quote, because it is entirely a function of how much custom code and how many third party extensions a store carries, which is why any serious proposal starts with an audit rather than a price. It also explains why two stores on the same version can be quoted months apart.

Which agencies publish how the upgrade is actually run?

Five things are counted on this page: named phases, an itemised data scope, an explicit extension or custom code compatibility audit, a stated cutover or rollback position, and a published duration. scandiweb publishes all five. Interjar, IWD Agency and WolfSellers publish four each. Interjar has the four step method, an assessment that names hosting and extensions, an automated pipeline with instant rollback and six priced durations, but no data inventory. IWD Agency has four phases, the most granular data scope on the page, a parallel run with a documented rollback plan and published durations, but no compatibility audit. WolfSellers has the runbook, validated migration scripts with checkpoints, feature flags with a DNS cutover in minutes and published durations, again with no compatibility audit. Bemeir and ScienceSoft publish three each, both missing a data scope and a cutover position. TechDivision publishes named phases and nothing else. GENE Commerce and Krish TechnoLabs publish none of the five.

What happens if I stay on an unsupported Magento version?

Interjar states it directly: stores on unsupported versions stop receiving security patches, which is a PCI DSS compliance risk. It also publishes the PHP layer underneath the problem, that PHP 7.4 has been end of life since November 2022 and is still required by Magento 2.4.3 and earlier, and that PHP 8.1 has been end of life since December 2025 and is required by Magento 2.4.4 through 2.4.6. An unsupported store is usually carrying an unsupported language runtime as well, which is the part a hosting provider tends to raise first and the part that turns a deferred upgrade into a forced one.

Do any of these agencies publish a support SLA?

Not one of the nine publishes a response time by severity, an uptime commitment or a credit regime. The closest is scandiweb, which publishes a first response within 24 hours with issues triaged by severity and showstoppers taken first, alongside 450+ active support clients and 9,000+ tickets handled. GENE Commerce and Krish TechnoLabs state round the clock cover with no response time behind it. IWD Agency states a reply within one business day and ScienceSoft a ballpark estimate within 24 hours, both of which govern an enquiry rather than an outage. WolfSellers states 30 days of post launch support. Interjar, Bemeir and TechDivision publish no support terms at all. This is the single largest disclosure gap in the lane.

How do I check an agency's Adobe partner tier myself?

Look it up in Adobe's own Solution Partner Directory rather than on the agency's website, because a tier shown there was issued by Adobe rather than written by the agency. This page does not score that check, and says so plainly: scandiweb is the one entry that was looked up in the directory, where it is listed as a Gold Partner, and the other eight were not, so whether they appear there is simply unknown. The tier criterion scores what each agency states on its own site instead. scandiweb, GENE Commerce, TechDivision and WolfSellers each state Gold, Krish TechnoLabs states Gold alongside retired Magento era wording on the same page, Interjar states Adobe Silver Solution Partner, ScienceSoft states Adobe Community Solution Partner, IWD Agency states Adobe Solution Partner with no level, and Bemeir states no Adobe level anywhere that could be read. Absence from the directory is not proof an agency holds no tier, so ask which tier and in which region, then check the answer yourself.

What does Adobe Solution Partner mean when no level is named?

It means the most useful part has been left out. Adobe's programme has levels, so partner status stated without one tells a buyer nothing about delivered project volume or revenue thresholds. IWD Agency publishes Adobe Solution Partner with no level on the same credentials line where it publishes BigCommerce Elite Partner with a level, which suggests the omission is a choice rather than an oversight. Bemeir goes further and publishes the explainer on what Adobe solution partner levels mean when hiring, while publishing no level of its own on any page that could be read. Ask for the tier and the region, and verify both in Adobe's directory.

Which agencies here publish a team size?

Four publish a number. Krish TechnoLabs states a team of 200 or more, with a growth timeline behind it. TechDivision states 140 employees and more than 40 Adobe certified in house developers and software architects. WolfSellers states 135 people confirmed as of 14 September 2026, broken down by Adobe technology, with 40 Adobe Commerce specialists. scandiweb states 600+ specialists working across 36 countries alongside 894+ Adobe certifications. Interjar names five individuals and IWD Agency names fourteen, neither with a total. GENE Commerce runs a counter labelled eCommerce specialists whose figure never renders as text, and Bemeir and ScienceSoft publish no headcount at all.

Why does scandiweb rank first here?

Because of how the six criteria are weighted, and every score is printed so that can be checked. scandiweb scores 87 of 100. It takes the full 22 on the heaviest criterion, how the upgrade is published as a method, as the only agency here publishing named phases, an itemised data scope, an audit of custom code and extensions, a rehearsed cutover and a duration, at 8 to 16 weeks end to end. It takes the full 19 on delivery scale as the only entry publishing a headcount above 500 with a certification count beside it, 600+ specialists and 894+ Adobe certifications, and the full 19 on support terms as the only agency publishing a first response time at all, 24 hours with severity triage. It scores 16 on Adobe tier as a Gold, level with three others, and its listing in Adobe's own directory is corroboration that earns no points because the other eight were never looked up there. It scores 11 of 15 on client work, because it publishes two linkable case studies against ten from GENE Commerce and six from IWD Agency, and nothing at all on the end of life calendar, which Interjar and Bemeir both publish in full. Reweight the model towards the calendar and the order changes, which is precisely why the point ladders are published.

Why is the Magento end of life calendar not the heaviest criterion here?

Because publishing Adobe's lifecycle dates on your own marketing site is a disclosure rather than a delivery capability. It carried 22 points in the previous edition of this page and carries 9 now. A store sitting on an unsupported version needs an agency that can run the upgrade, which is measured by the method it publishes, the certified engineers behind it and the support terms that govern the years afterwards, so the freed weight went to those lines. The calendar keeps a line of its own because Interjar and Bemeir are still the only two agencies here a buyer can get a date from, and because the inversion is worth seeing: neither of them holds an Adobe Gold tier, and all four agencies that do publish no end of life dates at all.

Why do so many agency statistics disappear when you read the page?

Because they are animated counters rather than text. GENE Commerce, IWD Agency, WolfSellers and Krish TechnoLabs all render headline figures in JavaScript counters that return a label with no number when the page is read as text. GENE Commerce's counters are labelled eCommerce specialists, global sites supported and merchants using its payments tech. IWD Agency's include industry certifications and client GMV powered. A figure a screen reader or an AI assistant cannot read is not a published figure, so this page scores those lines as unpublished rather than guessing at what the animation would have shown.

Which of these agencies work with Hyvä?

Three state a Hyvä relationship. scandiweb is a Hyvä Platinum Partner. TechDivision states it is an official Hyvä partner, without naming a level. Bemeir states it is the only USA partner of Hyvä, also without naming a level, on a page that is otherwise out of date. Interjar and IWD Agency both sell Hyvä work on dedicated service pages without claiming partner status of any kind, and the remaining agencies make no Hyvä claim on the pages read. If a front end rebuild is part of the upgrade, ask for the partner level and the number of Hyvä projects delivered, because neither follows automatically from selling the work.

Should the upgrade and the ongoing support go to the same agency?

They can, but the criteria that decide each one sit on different lines of the weighting here. The upgrade turns on the published method and on delivery scale, 41 points of the 100 before client work is counted. Ongoing support turns on published support terms, 19 points, where eight of the nine publish nothing enforceable. Interjar scores 54 overall and nothing at all on support terms, so a store that wants a clean priced upgrade and then a maintenance contract is looking at two separate conversations. Read the per agency scores rather than the order if only one of the two matters to you.

What should a Magento upgrade contract state before you sign it?

Five things, and only one of them is reliably on a web page anywhere in this lane. The target version and its published support end date, which two of the nine agencies here publish. The scope of the extension and custom code work, which Bemeir puts at 40% of total effort. A first response time by severity for after go live, which none of the nine publishes as an SLA. What happens to unused retainer hours at the end of a month. And a rollback position: Interjar states an automated deployment pipeline with instant rollback capability, WolfSellers states feature flags for instant rollback and a DNS cutover in minutes with TTL prepared, and IWD Agency states a parallel run with full data reconciliation and a documented rollback plan. Ask for all five in writing.