Key takeaways
- Visual Merchandiser, Live Search and Product Recommendations are Adobe Commerce features and are not in Magento Open Source. Which edition you are on changes the entire parity conversation, and most migration guides don't make the distinction.
- Magento category rules are not evaluated in real time. They apply when the category is saved, so new products and stock changes need a re-save. Teams often do not realise how much manual upkeep this was until it is gone.
- Each Magento category takes one rule, and its conditions read product attributes such as price, quantity, colour and SKU. Performance signals like gross profit, conversion rate or in-stock variant ratio are not available as conditions.
- Shopify's 2026 collections release handles membership well: multi-source collections combine conditions, hand-picked products, other collections and app sources, with variant-level targeting. What neither platform does natively is order a collection by several business signals at once.
- Adobe Commerce brands migrating for lower total cost should price the merchandising replacement deliberately. Finding it during UAT is the expensive way.
Before anything else, work out which Magento you are actually leaving. On Adobe Commerce you are giving up Visual Merchandiser, Sensei-powered Live Search and AI product recommendations: licensed features that stay behind with the licence. On Magento Open Source you never had them, and whatever you built instead is an extension or custom code that probably nobody has documented.
Same migration on paper. Different loss entirely. Most guides don't make the distinction, which is why so many parity spreadsheets get filled in wrong.
What you share with every other Magento brand is a category page that does more than Shopify's does out of the box, and a team that has spent years tuning it. Layered navigation, attribute-driven category rules, position ordering, per-attribute search weight. None of it arrives with the product export.
Magento merchandising on Shopify: what maps, what does not
The pill on each row says how Shopify native handles that capability on its own, before any app.
| Capability | On Magento | Shopify native | The gap | With Kimonix |
|---|---|---|---|---|
| Category rulesNative: ahead | One rule per category with multiple conditions, reading attributes such as price, quantity, colour, SKU and dates. Adobe Commerce (Visual Merchandiser). | Multi-source collections (2026 release): conditions, hand-picked products, other collections and app sources combined, with variant-level targeting. | Shopify is ahead of both here. It evaluates as products change, and is not limited to one rule per collection. Neither reads performance signals such as gross profit or conversion rate. | One set of filters combining attributes, metafields and computed metrics, testable against a catalog average or median, not just a fixed value. Membership applies to collections Kimonix creates or takes over. |
| Rule evaluation timingNative: ahead | Not real time. Products match when the category is saved, so new products and stock status changes need each category re-saved. | Automated collections update as products change. | Shopify is genuinely better here. The manual re-save habit does not need replacing. | Scheduled re-sort, cadence by plan: roughly 6 hours on the top plan, 12 and 24 on lower ones, plus an on-demand Update. Batched because it recomputes a weighted score over a lookback window, which is not per-event work. |
| Product position orderingNative: at parity | Drag and drop positioning per category, plus automatic sort by stock level, age, colour, name, SKU or price. | Manual sort, or one of six fixed sort orders. | Similar shape, and on both platforms automatic sort resets manual positions. | Pins hold the positions you set, by typed position number or drag, and everything unpinned sorts around them. |
| Multi-signal sort | Automatic sort applies one criterion, for example stock level or price. | One criterion at a time. | Neither platform can weight profit, conversion rate and stock depth together. This is a gap you carry across, not one the migration creates. | Sorts on a library of 100+ parameters, blended into one weighted score. Each sorter carries a weight of 1 to 100 and a direction, for example units sold at 100, conversion rate at 70, in-stock variant ratio at 40. |
| Layered navigationNative: no equivalent | Attribute-driven faceted filtering. Available in both Magento Open Source and Adobe Commerce. | Filters via the Search & Discovery app. | Shopify filtering is shallower, and heavily customised layered navigation rarely transfers cleanly. This is a genuine gap with no clean answer. | Not covered. Kimonix Agentic Search is conversational search, not faceted filtering, so plan facets separately. |
| Live SearchNative: no equivalent | Semantic, personalized search powered by Adobe Sensei. Adobe Commerce only. | Basic native search, extended by the Search & Discovery app. | No native semantic or personalized search on Shopify. | Kimonix Agentic Search is the closer analog: a separate shopper-facing app running conversational on-site search that answers questions and can add products to cart. |
| Product RecommendationsNative: no equivalent | Behaviour-based recommendation units powered by Adobe Sensei. Adobe Commerce only. | Basic related products. | Little merchant control, and recommendations sit apart from category logic. | Recommendation elements share the strategy schema used for collections, so the same sorters, filters and boosts drive both surfaces, so two systems cannot disagree on one page. |
| Related, up-sell and cross-sellNative: at parity | Manually or rule-assigned per product. Both editions. | Related products, plus apps. | Manual assignment does not scale to a large catalog on either platform. | [Related products](/platform/cross-selling) driven by the same strategy engine plus page context, with availability as a lever you set: demote or exclude out-of-stock, or use in-stock variant ratio to push down products missing sizes. |
| Merchandising A/B testing | Not native. Usually an extension or a separate testing tool. | None for collection sort order. | Neither platform proves a merchandising change worked. | Head-to-head test of one sort strategy against another on live traffic, scored per variation on views, conversion rate, sales and profit, with the winner applied on completion. |
Two things are true, and the order matters. Shopify's automated collections beat Magento's save-to-apply rules outright, and that chore disappears on day one. But both platforms still order a collection by one signal at a time. Picture a 4,000-product catalog heading into a season. You want the lines that convert, at a decent margin, with sizes still in stock, near the top. Magento made you pick one of those three. Shopify makes you pick one of those three. Neither was ever going to weigh all of them.
First question: Open Source or Adobe Commerce?
This determines most of what follows, and it's worth settling before anyone opens a parity spreadsheet.
On Adobe Commerce, merchandising is substantially built in. Visual Merchandiser gives category rules and drag-and-drop positioning, Live Search provides Sensei-powered semantic search, and Product Recommendations generates behaviour-based units. All three are licensed features, all three stay behind when you leave, and none has a native Shopify equivalent. The replacement cost is real and belongs in the migration budget. Discovering it during UAT is the expensive way.
On Magento Open Source, none of those three exist. Layered navigation does, and so do category position ordering and related product assignment, but anything more sophisticated was almost certainly an extension or custom code. The good news is that there is less licensed capability to replace. The complication is that custom merchandising code tends to be undocumented, and the developer who wrote it has often moved on.
A useful check: if your merchandising depends on extensions from the Adobe Commerce Marketplace, list them now. Extension parity is a separate exercise from platform parity and it is routinely missed.
What genuinely gets better on Shopify
It would be easy to write this page as a list of losses, and that would not be honest. Two things improve.
Collection membership becomes continuous. Magento matches products to a rule-based category when that category is saved. Add a product to the catalog and it does not appear until someone re-saves. Change stock status and automatic sorting does not reflect it until someone re-saves. Shopify's automated collections evaluate as products change, so a chore disappears. Worth knowing that a merchandising layer trades some of that freshness back: Kimonix recomputes membership and order on a scheduled cycle, roughly every six hours on the top plan and less often on lower ones, plus an Update button when you need it immediately. The reason is that it is doing different work. Re-testing a simple attribute condition is cheap enough to run on every product change; recomputing a weighted score built from 90 days of sales, traffic and margin is not. You are choosing between a fresher simple rule and a slower rich one.
The operational burden drops. Hosting, patching, extension conflicts and upgrade cycles are the reason most Magento brands start looking, and that relief is real. Nothing below is an argument against migrating.
The thing to plan for is narrower than "merchandising", and it is a question of granularity. Shopify decides membership well and refreshes it promptly, then orders what is inside on a single key. A merchandising layer is a different order of control: a library of 100+ parameters, each tunable from 1 to 100, filters that can test against the catalog median instead of a fixed number, pins that coexist with automated ordering, per-shopper and per-market variation, and an A/B test to settle which version sells. A large catalog usually needs that, and no amount of membership logic substitutes for it.
Three ways to handle the merchandising gap
Port the logic into Shopify Functions
If your Magento merchandising was custom code, the instinct is often to rewrite it as custom code. Shopify Functions can express sort logic, and for a handful of stable rules that is defensible. Weigh it against why you are migrating: brands leaving Magento to escape developer dependency and upgrade cycles rarely want their merchandising back in a deploy pipeline.
Use automated collections and accept one sort signal
For a focused catalog this is a perfectly reasonable answer, and Shopify's automated collections are better than Magento's rule engine on timing. The test is how many signals actually drive your ordering today. If the honest answer is stock level and not much else, native is enough and you should not buy anything.
Add a merchandising layer
If the catalog is large and the ordering needs to reflect several things at once, Kimonix ranks each collection on a weighted blend drawn from a library of 100+ parameters, each one weighted by you, runs product recommendations from the same engine, and includes A/B testing so a change gets measured, not argued about. For Adobe Commerce brands it also replaces the Sensei-powered pieces that do not travel.
The practical appeal for Magento teams is that the rules sit in an interface, not a codebase, which is usually the specific dependency the migration was meant to end.
A worked example from an enterprise replatform
The closest documented parallel on our side is a Salesforce Commerce Cloud migration, not a Magento one, and it's worth reading for the shape of the problem, not the platform. KARL LAGERFELD moved to Shopify with complex category and sorting logic that had no native destination, handled merchandising as a layer separate from the commerce build, and went live with around 100 category and listing pages.
What transfers to a Magento context is the sequencing: merchandising was treated as an architectural decision made early, not a configuration task left until after cutover. Afterwards the business team managed merchandising across markets without routing changes through developers.
Read the full KARL LAGERFELD case study.
Settle these before the build starts
Which edition are you on, and which licensed features are you actually using?
Visual Merchandiser, Live Search and Product Recommendations are the three that leave with the licence.
List your merchandising extensions.
Extension parity is separate from platform parity and is the most commonly missed line on a Magento migration plan.
How deep is your layered navigation, and how much of it is customised?
Heavily tuned faceting is among the least portable things you own.
Who has been re-saving categories, and how often?
That answer tells you how much of your merchandising was manual upkeep dressed as automation, which usually reframes what you actually need to replace.
How a Magento migration actually runs
Magento migrations are the best-documented route onto Shopify, partly because they are the most common and partly because Magento stores tend to be heavily customised, which makes them expensive. Published estimates for professional projects commonly run from the low tens of thousands into six figures, with complex enterprise builds higher still.
The broad sequence is discovery and parity, catalog and customer data extraction, theme and storefront build, integrations to ERP, PIM and OMS, redirect mapping, then testing and cutover. The redirect work deserves particular attention on Magento because layered navigation generates a large surface of crawlable URLs that has no equivalent on the other side.
For the migration itself, Shopify's own material is the best free starting point, and an experienced partner is worth more than any guide.
Discovery and parity
Which edition you're on decides the scope. Visual Merchandiser, Live Search and Sensei recommendations leave with an Adobe Commerce licence.
Merchandising gets decided here, or not at all
Extension audit
List every merchandising extension. Extension parity is separate from platform parity and is the line most often missed.
Data extraction
Catalog, customers and orders. Magento's schema is well understood, so tooling exists for this.
Storefront and theme build
Rebuilt from scratch. Heavily customised layered navigation rarely survives the trip.
SEO and redirect mapping
Bigger than the product count suggests, because layered navigation generates a large surface of crawlable URLs.
Testing and cutover
UAT, then go live. Merchandising problems found here get launched with.
- Shopify: Magento to Shopify Migration, The Complete Guide
- Shopify: Ecommerce Replatforming and Migration Guide
- Shopify Help Center: Migrate to Shopify
Frequently asked questions
What happens to my Magento category rules when I migrate to Shopify?
+
They do not transfer, but the concept does. Magento category rules assign products to a category from attribute conditions such as price, quantity, colour or SKU, with one rule per category. Shopify's automated collections work similarly and evaluate continuously, where Magento only matches products when the category is saved. Conditions built on business signals, as opposed to product attributes, such as gross profit or conversion rate, are not available natively on either platform.
Does Shopify have layered navigation like Magento?
+
Not to the same depth. Layered navigation is available in both Magento Open Source and Adobe Commerce and filters on product attributes. On Shopify, filtering comes from the Search & Discovery app and is shallower, particularly on large catalogs with many attributes. Heavily customised layered navigation is one of the least portable parts of a Magento storefront, so it's worth scoping early.
Is Visual Merchandiser available in Magento Open Source?
+
No. Visual Merchandiser is an Adobe Commerce feature, as are Live Search and Product Recommendations, both powered by Adobe Sensei. Magento Open Source includes layered navigation, category position ordering and related product assignment, but not those three. This distinction matters on a migration because Adobe Commerce brands are replacing licensed capability, while Open Source brands are usually replacing extensions or custom code.
What replaces Adobe Sensei product recommendations on Shopify?
+
Shopify provides basic related products natively, which is generally not comparable to Sensei-powered recommendation units. Brands that relied on Adobe Commerce Product Recommendations usually select a Shopify app during the migration, not after it. The consideration worth weighing is whether recommendations and collection ordering run on the same logic, since separate systems tend to contradict each other on the same page.
How much does a Magento to Shopify migration cost?
+
Published estimates for professional projects commonly range from the low tens of thousands to six figures, with complex enterprise builds higher. Magento stores are usually among the more expensive migrations because they tend to be heavily customised. Scope it with an experienced partner, and include the replacement cost of any Adobe Commerce licensed features you use, since those leave with the licence.
Will I lose SEO migrating from Magento to Shopify?
+
Only if redirects are handled poorly, which is the single most common cause of post-migration traffic loss. Magento deserves extra attention here because layered navigation generates a large surface of crawlable URLs with no direct Shopify equivalent, so the redirect map is bigger than the product and category count suggests. Treat redirect mapping as a first-class workstream, not a launch-week task.
Related reading
- Kimonix collection sorting
- Product recommendations
- Related products and cross-selling
- Merchandising A/B testing
- KARL LAGERFELD case study
- Pricing
Planning the move?
If you are scoping a Magento or Adobe Commerce migration and the merchandising column is still open, it is cheaper to settle it now than to rebuild it after cutover.
We can walk your parity spreadsheet with you, row by row.
Book a demo with us today!