TL;DR: Shopify admin does not give most merchants a complete one-click export of every collection field (rules, SEO, metafields, templates) the way product CSV export works. For backup, audit or migration, export collections with a spreadsheet workflow. Collections Import Export Pro is built for that. Keep versioned files before any redesign or store copy.
Figure (COLLECTIONS-001-A1): Spreadsheet showing exported Shopify collection columns including title handle and rules
Steps at a glance
- Decide which fields you need (titles, handles, rules, SEO, metafields, templates).
- Count collections in admin so you can validate the file later.
- Export with a collections import/export app (or document any native workaround you still use).
- Download CSV or XLSX.
- Open the file without breaking IDs (watch Excel auto-formatting).
- Confirm row counts match admin.
- Spot-check manual vs automated (smart) collection rule columns.
- Store a dated backup before imports, theme changes or migrations.
Quick answer
Use an export when you need a portable copy of collection structure. Collections Import Export Pro’s App Store listing includes exporting collections with rules, metafields, SEO metadata and templates. Free plans may limit monthly records. Re-check the listing before promising unlimited exports.
Exports are for structure and metadata. They are not a substitute for product catalogue backups. If you also need products, run a product export (or your usual product migration tool) as a separate step.
What a collection export should include
Depending on your project, you may need:
- Title, handle, body HTML / description
- Collection type (manual vs automated)
- Automated conditions / rules
- SEO title and meta description
- Template suffix
- Image references
- Metafields
- Sort order / published state
Do not invent column names in published docs. Pull a real export from a test store and document those headers use the header row from a real export on your test store — do not invent columns. Until that file exists, treat any example columns below as illustrative labels only.
Before you export, write the job in one line: “backup before import”, “audit SEO titles”, “migrate to store B”, or “rebuild automated rules after a vendor rename”. The job decides which fields must be present and which you can ignore.
Native Shopify options and limits
Shopify’s product CSV export is well documented. Collection structure is different: merchants often cannot dump every rule and SEO field through the same product CSV path.
Practical native options people try:
- Manually copying collection settings (does not scale)
- Using the Admin API with a developer or middleware
- Theme or app-specific exports that only cover what that tool cares about
For agency migrations and large catalogues, a dedicated collections spreadsheet tool is usually the honest path. Link current Shopify help docs at publish time after URL verification.
If Shopify has added a new native collections export by your publish day, document it with a dated screenshot and still keep a spreadsheet workflow for metafields/rules if the native path is incomplete.
Export with Collections Import Export Pro
Canonical app name: Collections Import Export Pro (site sometimes says “Collection Import / Export Pro”).
Pattern (confirm labels in your install):
- Install or open Collections Import Export Pro.
- Choose Export for collections.
- Select which record types/fields you need if the UI offers field picking.
- Run the export and download CSV or XLSX.
- Archive the file as
collections-export-YYYY-MM-DD.xlsxin a shared drive with access limited to ops/merch. - Note the admin collection count and the file row count in the same ticket or changelog.
Respect plan limits (for example free monthly record allowances on the listing). If you are exporting a large catalogue near a limit, check the allowance before a migration weekend.
Image/data required before publish: real export screenshot and a redacted sample file: shopify-collections-export-csv-example.webp plus companion sample in output/assets/delivered/COLLECTIONS-001/.
Worked example: reading the export
Illustrative rows (replace with real headers from your sample):
| title | handle | collection_type | rule_summary | seo_title |
|---|---|---|---|---|
| Acme Home | acme-home | automated | Vendor equals Acme Home | Acme Home |
| Summer Sale | summer-sale | manual | (membership list) | Summer Sale 2026 |
Validation checklist:
- Row count ≈ collection count in admin (account for header rows and any skipped types).
- Automated collections show rule data; blank rule cells on “automated” rows are a red flag.
- Handles match storefront URLs (
/collections/handle). - SEO fields present if you requested them.
- Template suffixes match theme files you still use.
- At least one manual and one automated collection spot-checked end to end.
Opening the file safely (Excel and Sheets)
Excel often “helps” by converting long numeric IDs, barcodes-as-text, or handles that look like dates. Prefer XLSX from the app when available, or import CSV via a wizard that forces text columns. In Google Sheets, paste or import carefully and freeze the header row before filtering.
Do not sort the live working file without keeping an untouched archive copy. Sorting is fine for audits; corruption is harder to undo if the archive was overwritten.
Which method should you choose?
| Need | Prefer |
|---|---|
| One-off copy of a few titles | Manual |
| Full rules + SEO + metafields | Collections Import Export Pro |
| Ongoing multi-store sync | App + documented process |
| Developer-owned pipeline | Admin API scripts |
| Pre-import safety net | Always export first (see COLLECTIONS-002) |
Common mistakes and troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Row count ≠ admin count | Filtered export or extra header/meta rows | Re-export; document what the app includes |
| Rules missing | Field not selected / plan limit / wrong type | Confirm field picker and listing capabilities |
IDs look like 1.23E+14 |
Excel auto-format | Re-open as text / use XLSX |
| Handles do not match live URLs | Edited file after export | Compare to untouched archive |
| Metafields blank | Not included in export scope | Re-run with metafields selected |
Other pitfalls:
- Exporting after a bad import with no prior backup
- Assuming product CSV includes collection rules
- Editing live without a “before” file
- Storing the only copy in a personal Downloads folder
Frequently asked questions
Can I export Shopify smart collection rules to CSV?
That is a primary reason to use a collections export app. Confirm rule columns in your live export sample before publishing field documentation. Automated (smart) rules are only useful on a destination store if product tags, vendors and other condition fields still match.
Does Shopify admin export collections natively like products?
Not in the same complete way for most merchants. Treat dedicated export tools or APIs as the scalable options and verify any new native features on publish day.
What is the difference between CSV and XLSX for collections?
Both can work. XLSX often survives Excel better. CSV is simpler for git/diff workflows. Pick one convention per team and stick to it for imports so mapping stays familiar.
Should I export before a theme redesign?
Yes. Theme work often coincides with collection cleanup, template suffix changes and navigation edits. A backup export is cheap insurance and makes rollback discussions factual instead of speculative.
How often should I schedule collection exports?
For quiet catalogues, before any bulk import, migration or major merchandising rewrite is enough. For agencies running weekly changes across clients, a dated export before each import batch is the safer habit. Align frequency with how painful a bad import would be.
Do exports include which products sit in manual collections?
That depends on whether membership columns are part of your app’s export format. Do not assume membership is present. If your migration depends on manual membership, confirm with a sample file before go-live.
Next steps
Continue with import: How to import Shopify collections in bulk (COLLECTIONS-002). App landing: Collections Import Export Pro. App Store: apps.shopify.com/collection-import.
Shopify origin: https://www.aperitive.io/blogs/articles/how-to-export-shopify-collections-to-csv-or-excel