If you run a real store, you already know the Products list exports cleanly. The surprise comes the day you try to export your collections and realize the admin treats them as a second-class object. This guide covers exactly what you can pull natively, the sharp edge that quietly drops your collection data, and how to do a clean migration — framed for an operator who cares which collections actually make money, not just which ones exist.
What "export collections" actually means in Shopify
There are two different things people mean, and Shopify handles them very differently.
The first is exporting the products that belong to a collection — a filtered slice of your catalog. Shopify does this natively. The second is exporting the collections themselves — the container, its type (manual or automated), and the conditions that populate a smart collection. Shopify does not do this natively.
Confusing the two is where merchants lose hours. You export what looks like your "Bestsellers" collection, import it into a new store, and discover you shipped a pile of products with no collection wrapping them.
Exporting the products in a collection (the native path)
This is the method that works with zero apps. Go to Products, filter the list by the collection you want, select the matching products, and click Export. Shopify's own export flow supports exporting the current page, all products, selected products, or products matching your active search and filters, per the Shopify Help Center export documentation.
A few limits worth knowing before you build a workflow on this. The product CSV can't exceed fifteen megabytes — "Your product CSV can't exceed 15 MB" — so large catalogs split into multiple files, according to the Shopify guide to using CSV files. That same documentation is where the critical gotcha lives.
Here is the sentence that bites: collections won't export in a product CSV. You can assign a product to a collection during import, but the export file carries no collection column back out, per the Shopify using-CSV-files documentation. So "export the collection" via the product CSV is a one-way trip — products come out, collection membership does not.
If your goal is simply to hand a supplier, freelancer, or marketplace feed the list of SKUs in one collection, this native export is enough. If your goal is to recreate the collection elsewhere, it is not — read on.
Exporting the collections themselves (what it takes)
Because the admin has no native collections export, moving the collections as objects means one of two routes.
Route one — rebuild by hand. Export the products per collection, import them into the target store, then recreate each collection manually and re-add the products (or re-enter the smart conditions). Tedious, but free and fully under your control.
Route two — a third-party collections export app. Apps such as Matrixify, EZ Exporter, and various "Collections Import Export" listings generate a collection-level CSV that includes the title, description, type, and assigned products. These are third-party tools, not Shopify features — vet them like any app that touches your catalog, and test on a handful of collections before you trust a full migration.
Either way, understand what does and doesn't travel. Smart (automated) collections are defined by conditions — a legacy smart collection can hold up to sixty selection conditions matched on an all-or-any basis, per the Shopify smart collections documentation. Those conditions are the valuable part; a product list is not the same thing as the rule that regenerates it.
The gotchas that cost operators real time
Collection type is a one-way door. On the legacy model you can't convert an automatic collection to a manual one after creation — "You can't change an automatic collection to a manual collection," the Shopify legacy manual collections documentation says; the workaround is building a new collection of the other type. Decide the type before you rebuild, not after.
Deletion is permanent. If a messy migration leaves you deleting collections to start over, know that "Deleted collections are permanently removed from your Shopify admin," per that same legacy collections documentation. There is no trash can.
The blank-column wipe on import. When you re-import products with "Overwrite products with matching handles" on, a column that is present but blank overwrites the existing value with blank, while a column that is missing entirely leaves it untouched, per the Shopify using-CSV-files documentation. Merchants erase 300 descriptions this way. The rule: delete columns you don't want to touch; never leave them in with empty cells, and always keep the pre-import export file.
The new collections model raises the ceiling. Stores on the newer model can have up to five thousand collections that contain conditions and up to one hundred collections that contain variant-level membership, per the Shopify collection types documentation. If you're migrating a large catalog, confirm which model each store is on — they behave differently.
If you also need to export the product data itself alongside collection membership, our walkthrough on exporting Shopify products with their collections covers the CSV column mapping in detail.
A worked example: migrating a 600-product POD catalog
Say you run a print-on-demand store with 600 live products and 24 collections, and you're spinning up a second regional store. You want the collections to arrive intact.
Here's the sane sequence. First, filter Products by each collection and export — or export all 600 at once if the file stays under the size cap. Second, import those products into the new store. Third, recreate your 24 collections: the 18 automated ones get their condition sets re-entered (tag equals hiking plus type equals tee), and the 6 manual ones get their products re-added.
Now the math that matters. If rebuilding one collection by hand takes you roughly eight minutes, 24 collections is about 24 × 8 = 192 minutes — a little over three hours of click-work. A collections export app that round-trips the CSV might cut that to 24 × 2 = 48 minutes plus setup. Whether the app is worth it depends on how often you migrate; for a one-time move, three hours of your own hands may beat learning and trusting a new tool.
The automated collections are the real prize to preserve. Rebuild them with conditions rather than as static manual lists, and every new design you upload with the right tags files itself — the same reason automated merchandising beats manual curation for any store adding products weekly.
The profit angle every export guide skips
Exporting collections is almost always a means to an end: migration, a product feed, or an audit. The question underneath it is usually "which collections are pulling their weight?" — and a CSV of titles and product handles answers none of that.
A product export tells you what's in a collection. It can't tell you the true per-order profit of the products in that collection after product cost, Shopify and payment fees, and the ad spend you pushed toward that collection's landing page. That's the number that decides whether a collection deserves prime navigation real estate or should be merged and retired.
This is where PodVector AI fits. Victor is an AI employee that works across your live store data — Shopify store operations, Meta Ads, Google Ads, Printify, Printful, Gelato, and Klaviyo — and computes true per-order profit so you can see which collections actually earn, not just which ones have the most products. Every write action Victor takes is approval-gated: he proposes, you approve, then it executes. He also delivers reports straight to your Google Drive, so the "which collections make money" view lands where your team already works. Victor is not a dashboard you log into and read — he's an operator who does the work and asks before committing it.
If merchandising follows margin for you, how you surface discounts on the product page is the next lever once you know which collections to push. You can put Victor to work on your store here.
FAQs
Can you export collections in Shopify natively?
Not as collection objects. Shopify lets you export the products inside a collection to CSV by filtering the Products list and clicking Export, per the Shopify export documentation, but the collection itself — its title, type, and smart conditions — does not export in that file, per the using-CSV-files documentation. To export the collections themselves you need a third-party app or a manual rebuild.
Will my smart collection conditions transfer if I export?
No, not through the native product CSV. The export contains products, not the conditions that generate a smart collection — and a legacy smart collection can carry up to sixty conditions, per the Shopify smart collections documentation. You have to re-enter those conditions in the target store or use an app that captures them in a collection-level CSV.
How do I import collections into another Shopify store?
Import the products first (CSV with "Overwrite products with matching handles" handled carefully), then recreate each collection and re-add products or re-enter conditions — or use a collections import/export app that does both in one file. Remember that collection type is fixed at creation and can't be switched later, per the legacy manual collections documentation, so choose manual versus automated before you build.
What's the file size limit on a Shopify export?
The product CSV can't exceed fifteen megabytes — "Your product CSV can't exceed 15 MB," per the Shopify using-CSV-files documentation. Large catalogs split into multiple files. If a single product has very large variant counts the file is emailed to you instead of downloaded directly.
Should I use an app to export collections or do it by hand?
For a one-time migration of a few dozen collections, a careful manual rebuild is often faster than learning and trusting a new tool. For frequent migrations, feed exports, or hundreds of collections, a vetted third-party export app pays for itself — test it on a small batch first, because the real work after any export is deciding which collections to keep, and that call should follow profit, not product count. Our guide to Shopify store operations covers how to run that decision.