Platform
Do you need to migrate to Shopify's new collections? A decision guide
There's no deadline and existing collections keep working, so who actually needs to act on Shopify's 2026-07 collections change? A clear answer for merchants, theme developers, and app developers.
Bas Lefeber
Founder, learnshopify.dev · July 8, 2026 · 4 min read
Every platform change arrives with the same background hum of anxiety: "do I have to do something, and what breaks if I don't?" Shopify's new source-based collections model in the 2026-07 Admin API is a big change, so the anxiety is understandable. The good news is that the honest answer for most people is "nothing, right now." The important news is that for a specific group, the answer is "yes, and quietly, before it bites you." This guide sorts out which group you are in.
The headline facts
Per Shopify's migration guide, there is no announced deadline and no removal date for the legacy model. Existing collections keep working indefinitely, and older API versions still read and write legacy-shaped collections. Migration is voluntary: you do it to use new features, or because an app you rely on does. The one hard edge is that collections using new capabilities are invisible (they return 404) to older API versions.
If you're a merchant: do nothing
This is the simplest case and it covers the most people. Your existing collections keep working. There is no migration to run, no setting to flip, no deadline on a calendar. The new capabilities (sub-collections, rules blended with manual picks, exclusions, variant edits) arrive as new options when you build collections, not as a forced change to the ones you already have.
The only thing worth doing is knowing the new powers exist so you stop working around limits that no longer apply. If you have been maintaining a manual "All Sale" list or paying an app just to force one product into a rule-based collection, the sub-collections guide shows the native way to retire that workaround.
If you build themes: mostly nothing, with one thing to verify
The migration guide does not list theme developers as needing code changes, and that matches what Shopify's Merchandising team said in the developer-preview thread: variant-scoped collections are meant to render with no theme changes required. Your existing collection templates keep working.
The one caveat is timing, not code. Storefront rendering of variant-scoped collections was rolling out gradually, so if a client wants a variant-level edit ("shop the red") live on their storefront, verify it renders correctly on that specific store before you promise it. That is a five-minute check, not a migration. The full detail is in variant-level collections and the storefront.
A worthwhile audit even if nothing forces you
While you are here: confirm your product cards derive swatches and price ranges from the product's actual variants, not from a metafield string or hardcoded values. Cards that already reason about variants will benefit automatically when variant scoping goes live; ones that fake it won't. That is good hygiene regardless of this change.
If you build apps: yes, and here's how urgent
App developers are the real audience for the word "migrate." How much you need to do depends on what your app touches. Here is the honest triage.
| Your app… | Do you need to act? | Why |
|---|---|---|
| Doesn't touch collections | No | Nothing to do. |
| Reads collection product lists | Yes: bump version | Your read code may not change, but on an old API version, collections using new features 404 and vanish from lists. Move to 2026-07 so you see the whole catalog. |
Reads ruleSet | Yes: migrate code | Rules moved into a conditions source inside the sources array. Replace ruleSet reads with sources queries. |
| Writes collections | Yes: migrate code | collectionCreate / collectionUpdate move to the collection: argument, and add/remove folds into selections. See the field map. |
| Ships a Function (discount, cart transform, validation) | Yes: check membership logic | With variant-scoped collections, read membership from the variant, not the product: a product can be 'in' a collection for only some of its variants. |
Filters by collection_type | Yes: replace it | The custom-versus-smart distinction is gone, so the collection_type filter goes with it. |
The trap hidden in 'non-breaking'
"Non-breaking" means the old path stays open, not that you can ignore this. The moment any merchant on your app builds a collection with an exclusion or a variant target, an app still on an old API version stops seeing that collection: no error, no warning, just a silent 404 and a sync that drifts out of truth. If your app reads or writes collections at all, bumping to 2026-07 is the cheap insurance that prevents a support ticket you will struggle to reproduce.
So: do you need to migrate?
- Merchant? No. Enjoy the new options when you want them.
- Theme developer? No code change. Verify variant-scoped rendering on the target store before you rely on it.
- App that ignores collections? No.
- App that reads or writes collections? Yes. At minimum bump to the 2026-07 Admin API so new-model collections don't silently disappear; migrate your field and mutation shapes if you read rules or write collections.
There is no rush the platform is imposing on you. But "no deadline" is not "no consequences." The consequence for an app that reads collections and stays on an old version is invisible data loss that grows as merchants adopt the new features. That is a worse failure than a loud deprecation, precisely because nothing tells you it is happening. When you are ready for the mechanics, the field-by-field migration guide walks through every mapping.
Learn this properly · free lesson
Where should this data live: tag, metafield, or metaobject?
The judgment underneath every migration like this: knowing where each piece of merchant data actually belongs. Practice it against a live store. Free, in your browser.
Try this lesson — freeSources: Shopify Dev, Migrate to flexible collections and Use the new collections model; and the developer-preview community thread.
Frequently asked questions
Is there a deadline to migrate to Shopify's new collections model?
No. Shopify's migration guide states no removal date or deprecation deadline for the legacy model. Existing collections keep working indefinitely and older API versions continue to read and write legacy-shaped collections. Migration is voluntary: you do it to access new features or to support an app built on the new model.
Do merchants need to do anything about the new collections model?
No. Existing collections keep working with no action required. The new capabilities (sub-collections, blending rules with manual picks, exclusions, and variant targeting) appear as new options when building collections, not as a forced migration.
Which apps must migrate to the 2026-07 collections API?
Any app that reads or writes collections should act. Apps reading a collection's product list should at least bump to the 2026-07 Admin API, because collections using new features return 404 to older versions. Apps that read ruleSet, write collections, ship Functions, or filter by collection_type also need code changes to their field and mutation shapes.
What happens if my app doesn't migrate?
Nothing breaks loudly, which is the danger. An app on an older API version cannot see collections that use new capabilities (multiple sources, exclusions, sub-collections, or variant targeting): they return 404 and drop out of list results. As merchants adopt the new features, an un-migrated app silently syncs an increasingly incomplete view of the catalog with no error to signal it.
Start free
Ready to become a Shopify developer?
You just read how it works. Now write it yourself: real tickets from a live store, in an editor where the storefront updates as you type. Module 1 is free, no card.
Free · No credit card · Your first win in minutes
About the author
Bas Lefeber, Founder, learnshopify.dev
Bas builds learnshopify.dev, where developers learn production-grade Shopify theme development against a live storefront. He writes about Liquid, theme architecture, and the parts of the job that still matter now that AI writes the code.
Keep going in the curriculum
