Magento Open Source and Adobe Commerce work: Magento 1 to 2 migrations, 2.4.x upgrades, B2B builds, and performance rescues. Most of it sits under an NDA. Here is what a published case contains and how to check us in the meantime.
Enterprise ecommerce comes with lawyers. Almost every Magento contract we sign has an NDA attached, and the merchants who do not sign one usually still decline to publish revenue figures next to their store name. That is the main reason this page is thinner than the work behind it.
The other reason is that we hold ourselves to publishing a case only when the client has approved the numbers and we can link the live store. No mockups, no invented percentages, no "leading retailer" with the logo blurred out.
What follows is what our Magento projects involve, what goes into a case when a client clears one, and what you can check today. If you want to see how we document an ecommerce project, the Shopify to WooCommerce migration and the Aria Fashion build are both public with real figures.
No Magento cases published yet. Check back soon — we ship multiple per month.
Magento 1 reached end of life in June 2020 and stores are still running on it, so M1 to M2 migration remains live work. Alongside that: 2.4.x version upgrades on stores that fell three minor releases behind, performance work on catalogues where category pages take eight seconds, and B2B builds using company accounts, shared catalogues and quote workflows. Adobe Commerce and Magento Open Source overlap heavily on the engineering side, and we work on both.
We will also tell you when Magento is too much platform for your business. A store doing a few hundred orders a month with a simple catalogue is paying for hosting, developer time and upgrade cycles it does not need. That conversation happens on the first call, not after the invoice.
The brief and the commercial constraint. Magento edition and exact version, PHP, Elasticsearch or OpenSearch, Redis, Varnish, and where it is hosted. Every third party extension we kept, replaced, or wrote, named. Catalogue size in SKUs and attribute count, because on Magento that is what drives everything. Real budget band and real calendar time with overruns stated. Post-launch Core Web Vitals, conversion, and Search Console data from the merchant's own property. Then a section on what we would do differently.
Where an NDA blocks the brand, we sometimes publish the architecture and the numbers without the name, if the client allows it. Where it blocks everything, the case stays off the site.
Read the ecommerce cases we can publish. The Shopify to WooCommerce migration covers 1,840 SKUs, the redirect map, and the hosting cost change. The catalogue and SEO problems on a Magento move are the same shape, at a larger scale.
Ask for a reference call. Thirty minutes with a past client before you sign anything. Merchants who cannot be named in public are frequently happy to speak to a peer in private.
Start with a paid audit. You get a written report on your store's performance, extension conflicts, upgrade blockers and security posture, with a prioritised fix list. It is the cheapest way to find out whether you want to work with us at all.
Magento services lists scope and pricing per service, and packaged solutions covers the fixed-price versions, including the M1 to M2 migration pack. If B2B is what brought you here, Magento for B2B goes into company accounts, shared catalogues and quote flows properly.
Nearly every Magento project we take is covered by an NDA, and we publish a case only once the merchant has approved the figures and agreed we can link the live store. Write-ups go up as those approvals arrive. We are not going to pad the page with "a leading retailer" and a percentage you cannot check.
Not in writing, but usually on a call. We can walk through architecture decisions, custom module code, before and after performance profiles, and the migration plan, without naming the merchant. What we will not do is send a deck you can forward, because that is exactly what the NDA covers.
Yes. We arrange 30 minute reference calls before a contract is signed and try to match the client to your situation, so an M1 to M2 migration prospect speaks to someone who has been through one. We ask the client first and never share a contact without permission.
Both. The rebrand renamed the paid edition to Adobe Commerce and left Magento Open Source as the free one, and the underlying codebase is shared, so most engineering work transfers directly. The differences that matter in practice are B2B features, page builder, and the hosted infrastructure on the paid tier. We will tell you honestly whether your requirements justify the licence.
Magento 1 stopped receiving security patches in June 2020, so you are running unsupported code that handles card data. The realistic options are a migration to Magento 2, a move to a different platform such as WooCommerce or Shopify, or paying for third party patching while you decide. We audit the store first, because the answer depends on catalogue size, extension debt, and how much custom checkout logic is in the way.
Three to six months is typical for a mid-size catalogue with a normal extension load. It is a rebuild rather than an upgrade: the data migrates, the theme and the extensions do not. Anyone quoting you six weeks without seeing the store is guessing. We scope it in a paid audit and then quote a fixed price against that scope.
30 minutes with a senior engineer. No salespeople. We respond within one business day with a brief outline.
Send a project brief →
