TL;DR: To move collection structure between Shopify stores, export collections (with rules and SEO fields where needed) from the source, ensure destination products/tags/vendors exist for automated rules, then import and validate. Collections Import Export Pro supports spreadsheet-based collection migration workflows; it does not replace product migration.
Figure (COLLECTIONS-003-A1): Checklist for migrating Shopify collections from a source store to a destination store
Migration checklist (at a glance)
- Inventory collections on the source store (counts by manual vs automated).
- Export collections with rules and SEO metadata.
- Migrate or confirm products, vendors and tags on the destination first.
- Map handle conflicts and naming differences.
- Import into the destination store (small batch first).
- Validate product membership counts for automated collections.
- Update navigation menus to point at new collection URLs.
- Spot-check storefront templates and SEO fields.
- Keep dated source exports as rollback insurance.
Quick answer
Treat collection migration as a structure move. Products must already be present (or migrated separately) for automated collections to populate. Pair this guide with the export and import tutorials (COLLECTIONS-001 / COLLECTIONS-002).
A successful migration is not “import returned OK”. It is matching membership, handles, SEO fields and menus on the destination after QA. Build time for that validation into the cutover plan.
What transfers cleanly vs what breaks
| Asset | Usually transferable via spreadsheet apps | Watch-outs |
|---|---|---|
| Titles, handles, descriptions | Yes | Handle collisions |
| Automated rules | Yes if columns supported | Destination data must match |
| SEO title/description | Yes if exported | Re-index timing |
| Manual membership | Depends on product IDs/SKUs in file | ID mismatch across stores |
| Menu links | Separate menu export/import if available | Broken URLs after handle changes |
| Collection images | Sometimes URL-based | Re-upload may be needed |
| Template suffixes | Often as a field | Theme must include that template |
Prerequisites (both stores)
Before you touch import on the destination:
- Staff access on source and destination with permission to manage collections
- Collections Import Export Pro (or your chosen tool) installed where needed - Product migration complete enough for automated rules to resolve, or a clear plan for a second membership pass
- Theme on destination includes any collection templates referenced by suffix
- Written handle policy: preserve exact handles for SEO, or accept new handles plus redirects
- Shared folder for dated exports (
source-collections-YYYY-MM-DD.xlsx) - Freeze window agreed so merchandisers stop editing collections mid-migration
Source store: export and audit
- Note total collections in admin; split approximate counts of manual vs automated.
- Export via Collections Import Export Pro.
- Save
source-collections-YYYY-MM-DD.xlsx. - Flag collections you will not migrate (tests, seasonal dead ends, app-generated clutter).
- List handles that must stay identical for SEO/redirect reasons.
- Spot-check rule columns for the highest-traffic automated collections.
- Note any collections that depend on metafields or tags not yet present on the destination.
See also: export tutorial when published (COLLECTIONS-001).
Destination store: prerequisites
Before import:
- Products exist (or a product migration is complete)
- Vendor/tag/product-type values match rule expectations (spelling and casing)
- Theme collection templates you reference exist
- Staff understand unpublished vs published state
- Existing destination collections reviewed for handle collisions with the incoming file
If automated rules reference vendors that do not exist yet, collections import “successfully” but stay empty. Fix product data first, or temporarily leave those collections unpublished until vendors are normalised.
Handle and SEO mapping
Create a simple mapping sheet for anything that cannot stay identical:
| source_handle | destination_handle | redirect needed? | notes |
|---|---|---|---|
| acme-home | acme-home | no | preserve |
| ss24-sale | summer-sale | yes | rename for clarity |
If you change handles, plan redirects and menu updates in the same cutover checklist. Migrating SEO title/description without preserving handles still leaves old URLs stranded unless redirects exist.
Import and validate
- Install/configure Collections Import Export Pro on the destination.
- Import a 5-collection pilot file that includes both manual and automated examples if both exist.
- Check admin counts vs source for those five (membership within an agreed tolerance).
- Fix sheet issues (rules, handles, encoding).
- Import the remainder in batches if the catalogue is large or plan limits apply.
- Crawl key URLs on the storefront (desktop and mobile).
- Confirm template assignments on a sample of collections.
- Submit updated sitemap / request indexing only after QA.
App landing: Collections Import Export Pro. App Store: collection-import.
Worked example: staging → production
| Step | Owner | Done? |
|---|---|---|
| Export 120 collections from staging | Ops | |
| Confirm 4,800 products already in production | Ops | |
| Normalise 3 vendor spelling mismatches | Merch | |
| Pilot import 5 brand collections | Ops | |
| Full import | Ops | |
| Compare automated membership ±5% tolerance | Merch | |
| Update header Brands menu | Merch | |
| Spot-check SEO titles on top 10 collections | SEO | |
| Archive export files | Ops |
Image: shopify-collection-migration-checklist.webp (Claude Design OK).
Membership tolerance tip: a small variance can be leftover draft products or market-specific catalogues. Investigate outliers before re-importing the entire file.
Menus and related content
Collection migration often leaves menus pointing at old handles. If you also migrate navigation, use the app’s menu features when available or rebuild critical links manually. Do not claim menu migration in this article’s steps until verified for your app version. Related backlog: COLLECTIONS-009 / COLLECTIONS-011.
Also check homepage sections, mega-menus and campaign landing pages that hard-code collection URLs. Structure can migrate while the storefront still links to staging handles.
Common mistakes and troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Empty automated collections | Products/tags/vendors missing on destination | Fix product data; re-validate rules |
| Handle conflicts | Destination already has that handle | Map/rename; confirm update behaviour |
| Menus 404 | Handles changed; menus not updated | Update navigation; add redirects |
| Wrong template look | Template suffix missing on theme | Add template or clear suffix |
| SEO titles blank | SEO columns not in import | Re-export/re-import with SEO fields |
| “Success” but wrong membership | Rule operators differ / casing | Compare source vs destination product fields |
Other pitfalls:
- Importing collections before products
- Skipping pilot batch
- No source backup
- Assuming empty automated collections mean import failure when product data is simply incomplete
Frequently asked questions
Can I copy smart collections between Shopify stores?
Yes via export/import of rules when your tool supports condition columns. Validate membership after products exist. “Smart” and “automated” refer to condition-based collections; confirm the label your admin and export file use.
Do collection migrations move the products themselves?
No. Migrate products first (or in parallel with a product tool). Collections organise products; they are not a product database dump.
How do I keep SEO titles and descriptions?
Include SEO fields in the export/import mapping and spot-check high-traffic collections after go-live. Preserving handles matters as much as preserving meta copy if you want existing URLs to keep working.
What should I validate after import?
Counts, handles, rules, SEO fields, templates, menus and a mobile storefront pass on top collections. Add a feed/channel spot-check if collections drive merchandising in those channels.
Should staging and production use the same app plan limits?
Check record allowances before a full run. A pilot can succeed on a free allowance while the full file needs a higher plan or multiple days. Do not discover that during cutover.
Can I migrate only automated collections first?
Yes, and many teams do. Migrate automated brand/category rules first, validate membership, then bring manual campaign collections once merchandising signs off. Keep separate pilot files so failures stay contained.
Next steps
Export guide (COLLECTIONS-001), import guide (COLLECTIONS-002), then optional portfolio migration checklist (PORTFOLIO-006). Product page: collection-import-export-pro.
Shopify origin: https://www.aperitive.io/blogs/articles/how-to-migrate-shopify-collections-between-stores