Most direct-to-consumer brands are too small for Magento and Hyvä until roughly 8 to 10 million dollars in annual revenue, unless one of three triggers appears first: genuinely complex product configuration, real B2B or wholesale alongside retail, or multi-store operations across regions or brands. Below that line, and without those triggers, Shopify usually wins on total cost and time to launch.
That answer frustrates people who want a clean revenue number. The honest version is that size is a proxy, not the deciding factor. A 4 million dollar brand selling made-to-order furniture with hundreds of option combinations can outgrow Shopify faster than a 15 million dollar brand selling twelve SKUs of skincare. This guide gives you the revenue math, the complexity triggers that override it, and a way to tell which side of the line you are actually on.
Why “too small” is the wrong question
The question merchants ask is “am I big enough for Magento?” The question that predicts a good outcome is “does my catalog and my operation need things Shopify cannot do without fighting it?” Adobe Commerce and a Magento development build give you an open codebase, deep B2B primitives, and full control over data models. Those are assets only when you have a problem that needs them. When you do not, they are cost and complexity you pay for and never use.
Shopify optimizes for the common case: a catalog of standard products, a fast hosted checkout, and an app for every extension you might want. It is very good at that case. The moment your requirements sit outside it, you start bolting on apps, paying per-app monthly fees, and hitting platform limits you cannot code around. That transition point, not a revenue figure, is when Magento starts to pay for itself.
The revenue reality: where the money math flips
Total cost of ownership is the number that should drive the decision, and for most DTC brands it favors Shopify well past the point where founders assume they have “outgrown” it. Shopify Plus starts around 2,300 dollars per month on a three-year term and shifts to a variable fee of about 0.35 percent of sales once monthly GMV passes roughly 800,000 dollars, capped at 40,000 dollars per month. Shopify’s own comparison against Adobe Commerce claims a 29 percent lower total cost of ownership on average and a 40 percent faster launch, which is marketing but directionally consistent with what we see in real projects.
The reason is not licensing. It is the engineering function. An Adobe Commerce store needs hosting, a build pipeline, security patching, upgrades, and developers who understand the platform. Shopify absorbs all of that into the subscription. Below roughly 10 million dollars in revenue, the fully loaded cost of running that owned infrastructure usually exceeds what you save by escaping app fees and platform limits.
Here is how the bands tend to shake out for a retail-only DTC brand with no unusual complexity:
| Annual revenue | Typical best fit | Why |
|---|---|---|
| Under 3M | Shopify (standard or Advanced) | App fees are small, no need for owned infrastructure, speed to market matters most |
| 3M to 8M | Shopify Plus | Variable fee still cheaper than a platform engineering function, checkout conversion is strong |
| 8M to 15M | Shopify Plus, unless a trigger fires | The line where owned infrastructure starts to compete; complexity decides |
| 15M to 50M | Either, driven by complexity not size | Real evaluation territory; Magento wins when B2B, configuration, or multi-store are core |
| 50M+ with custom needs | Adobe Commerce and Hyvä | Owned infrastructure amortizes, custom logic and ERP depth justify the cost |
These bands assume a clean retail catalog. Move any of the three triggers below into the picture and the whole table shifts left, sometimes dramatically.
The three triggers that override revenue
Trigger 1: product complexity Shopify fights you on
Shopify handles variants well up to 100 per product and 2,000 SKUs per store on standard plans, with higher ceilings on Plus. It handles configurators badly. If your product needs dependent options, live price calculation across many dimensions, made-to-order rules, or bundles that recombine inventory, you will end up with a stack of apps that each own a slice of the logic and do not talk to each other cleanly. On Magento, that logic lives in one codebase you control. Brands that sell configurable furniture, custom apparel, industrial parts, or anything built to order hit this wall early, sometimes at 3 to 4 million dollars. If this is you, read our guide to building a product configurator on Magento and Hyvä before you assume Shopify apps will cover it.
Trigger 2: real B2B alongside your retail store
Selling wholesale to accounts with negotiated pricing, credit terms, and buyer hierarchies is where Adobe Commerce is genuinely hard to beat. Its native B2B module gives you company accounts, shared catalogs, requisition lists, and negotiable quotes without stitching apps together. Shopify added B2B to its paid plans, and it works for straightforward wholesale, but it breaks down when you need multi-level approval workflows, per-account catalogs, or tight ERP-driven pricing. If B2B is a real revenue line and not a side experiment, that alone can justify Magento at a size where a pure retail brand would stay on Shopify.
Trigger 3: multi-store across regions or brands
Running distinct storefronts for the US, Canada, and the EU with localized pricing, tax, content, and catalog, or running several brands off one operation, is native to Magento. One installation serves multiple websites, stores, and store views from a shared admin and codebase. Shopify Markets handles international selling well for a single brand, but multiple genuinely distinct storefronts or brands push you into multiple Shopify stores and duplicated effort. Our breakdown of multi-website and multi-store architecture on Hyvä covers how the scope model works in practice.
What Hyvä going free changes about the math
The old argument against Magento for smaller brands was partly frontend cost. Building a fast storefront meant Luma (slow) or an expensive frontend license. That changed on November 10, 2025, when Hyvä relicensed its theme to OSL3 and AFL3, making it free and open source, available on GitHub and through free Packagist keys. Checkout, Enterprise, and Commerce modules stay proprietary, but the core theme that produces the PageSpeed and Core Web Vitals results Luma never could is now free to use.
That lowers the entry cost of a modern Magento build and makes the “too small” line a little lower than it was two years ago, because a Hyvä frontend build no longer carries a recurring license just to be fast. It does not change the fundamental math, though. The engineering function is still the real cost, and free frontend code does not maintain, patch, or upgrade itself.
What moving too early actually costs you
Migrating a small brand to Magento before it needs the platform is a common and expensive mistake. The costs are not hypothetical:
- You take on hosting, security patching, and upgrade cycles that Shopify handled for you.
- You become dependent on developer availability for changes a Shopify merchant makes in the admin.
- You spend the migration budget and the months it takes, and get no new revenue capability in return, because you did not have a problem Magento solves.
- You inherit a larger attack surface and PCI responsibility that a hosted platform absorbed.
If you are moving because Shopify feels limiting in the abstract rather than because a specific requirement is blocked, that is a signal to wait. Move when a named requirement, not a feeling, cannot be met.
A decision framework you can apply this week
Work through these in order. Any single “yes” in the triggers section can outweigh a “no” on revenue.
- Is a specific requirement blocked on Shopify today, or projected within 12 months? Name it. If you cannot, you are not ready.
- Does that requirement fall under configuration, B2B, or multi-store? If yes, Magento is a real candidate regardless of size.
- Is your revenue above roughly 8 million dollars, or will it be within the year? If no and no trigger fired, stay and revisit.
- Do you have budget for ongoing platform engineering, in-house or through an agency retainer? If no, solve that before migrating, not after.
- Have you priced the fully loaded three-year cost of both paths, not just the migration? Our Adobe Commerce versus Shopify Plus three-year TCO model gives you the structure.
If you answered yes to a trigger and yes to budget, Magento and Hyvä are worth a real evaluation. If not, the disciplined move is to stay on Shopify and get more out of it.
If you are close but not certain
Two intermediate moves buy you time. First, exhaust Shopify’s own capabilities: metafields and metaobjects handle more custom data than most brands realize, and Plus adds scripting and higher limits. Second, when you do migrate, do it deliberately. Our practitioner guide to replatforming from Shopify to Adobe Commerce on Hyvä covers what data transfers, what you rebuild, and the metafield-to-attribute translation that surprises teams.
As the first US-based Hyvä Gold partner, Bemeir has run this decision with brands on both sides of the line, and the honest recommendation is often to stay put. We build on Shopify, BigCommerce, and Shopware as well as Magento, so the advice is not “everything should be Magento.” It is “match the platform to the problem.” You can read more about how we work on the about Bemeir page, and our depth of technology and integration partners is part of why a Magento build can absorb requirements a hosted platform cannot.
FAQ
What revenue do you need before Magento makes sense for a DTC brand?
For a retail-only brand with a standard catalog, roughly 8 to 10 million dollars in annual revenue is where owned infrastructure starts to compete with Shopify Plus on total cost. Below that, unless product complexity, B2B, or multi-store requirements force the issue, Shopify almost always costs less when you include hosting, developers, and maintenance.
Is Hyvä worth it for a small store now that it is free?
Hyvä being free removes the frontend license that used to make a fast Magento storefront more expensive, so it lowers the entry cost. It does not remove the real cost, which is running the platform: hosting, patching, and upgrades. A small store still needs a reason to be on Magento at all before a free frontend matters.
Can I run B2B and DTC on the same Shopify store, or do I need Magento?
Shopify supports B2B on its paid plans and it works for straightforward wholesale. If your B2B needs multi-level order approval, per-account catalogs, negotiable quotes, or ERP-driven pricing, those are native to Adobe Commerce and awkward or impossible on Shopify. Real B2B alongside retail is one of the clearest reasons to choose Magento at a smaller size.
How long does a Shopify to Magento and Hyvä migration take?
For a mid-sized DTC catalog, plan on several months rather than weeks, covering catalog export and remapping, theme rebuild on Hyvä, integration rework, and a careful cutover. The timeline depends far more on integration and customization depth than on catalog size, so scope those first.
What is the biggest mistake brands make with this decision?
Migrating on a feeling rather than a blocked requirement. If you cannot name the specific thing Shopify will not let you do, you are buying cost and complexity with no return. Move when a concrete requirement, not a general sense of limitation, forces the change.
