Category & Collection Mapping

Why Category & Collection Mapping needs Custom Migration

Category trees, nested paths, and collection rules vary widely between Magento, Shopify, WooCommerce, PrestaShop, and others. Custom category & collection mapping merges, splits, or remaps taxonomies so merchandising and SEO-friendly navigation stay coherent on the new store.

Who this customization is for

• Merchants flattening deep Magento trees into Shopify collections
• Teams preserving Woo/PrestaShop hierarchies with custom parent rules
• SEO owners protecting category landing URLs
• Merchandisers redesigning navigation during the move

Common use cases

• Flattening deep Magento category trees into Shopify collections
• Preserving WooCommerce or PrestaShop hierarchies with custom parent rules
• Reassigning products when source categories do not exist on the target
• Building manual or rule-based Shopify collections from source membership
• Cleaning duplicate or legacy categories during the move

What Cart2Cart customizes

We design a category/collection blueprint with your merchandising goals, map product assignments, and validate storefront navigation on sample paths before Full Migration.

Platform considerations

Shopify collections are not identical to Magento categories; automated vs manual collections change how assignments work. Custom Migration encodes your intended IA instead of dumping a raw tree.

Note: The Target platform may require installing additional apps, plugins, or add-ons when a capability is not available by default. Custom Migration can map and import the data, but those Target-side apps/plugins often need to be installed and configured so the feature works in admin and on the storefront.

The best way to make sure everything is mapped correctly is to run a Demo Migration with your real Source platform data, then carefully check how entities look on the Target store before Full Migration.

Checklist for evaluating this customized migration

• Decide keep, flatten, merge, or redesign the category/collection tree.
• Document product assignment rules for multi-category items.
• Identify SEO-critical category URLs that need redirects.
• Plan Shopify collection type (manual vs automated) if applicable.
• Walk key navigation paths on Demo before Full Migration.

How to apply for this customization

1. Open Custom Migration or book a Migration Expert.
2. Share platforms and whether you prefer to keep, flatten, or redesign the tree.
3. Provide a category export or sitemap priorities if you have them.
4. We propose mapping rules, Demo-check key paths, then migrate with approved structure.

Self-service Additional Options vs Custom Migration

Categories migrate as a core entity. Shopify Automated Collections are a Wizard Additional Option. Custom Migration is for tree redesign, merges/splits, and merchandising rules beyond that option.

• Migrate Source categories into Shopify Automated Collections — Self-service: Convert source categories into Shopify automated collections in the Wizard for eligible pairs. Choose Custom Migration when: Custom Migration for flattening deep trees, manual collections, multi-assignment rules, or non-Shopify targets needing IA redesign.
• Preserve category IDs on Target Store — Self-service: Keep category IDs when supported (typically with Clear Target data). Choose Custom Migration when: Custom Migration when navigation must change and IDs alone are not enough—pair with SEO URL / 301 planning.

Availability depends on your Source → Target pair—confirm checkboxes in the Migration Wizard Entities / Additional Options step. See the Additional Options guide and Additional Options FAQ for pair-specific details. If Wizard options are not enough, schedule a Custom Migration call.

Already ran a self-service migration?

Yes—you can still apply this Custom Migration after a Wizard (self-service) run. Cart2Cart can restart migration with the customized rules; the Target store typically needs Clear current data on Target Store before Migration (or an equivalent cleanup of the entities from the previous self-service migration) so customized results are not mixed with the old import. Share your Source/Target carts and what already moved—Migration Experts will confirm the safest clear-and-rerun plan before Full Migration. Schedule a call if you already completed a Demo or Full Wizard migration and need customization next.

Case studies from real Custom Migrations

Cart2Cart Migration Experts have delivered custom work related to Category & Collection Mapping across 175 recorded customization projects spanning 50 Source→Target platform pairs. Below are pairs we see most often, the entities typically involved, and sample data volumes when available.

Platform pairs already in focus

• Magento → Shopify — 38 customization projects
• WooCommerce → Shopify — 27 customization projects
• Magento → WooCommerce — 13 customization projects
• PrestaShop → Shopify — 11 customization projects
• BigCommerce → Shopify — 7 customization projects
• Wix → Shopify — 6 customization projects

Entities commonly customized

• Products — seen in 114 related projects
• Categories — seen in 94 related projects
• Customers — seen in 81 related projects
• Orders — seen in 77 related projects
• Coupons — seen in 21 related projects

How much data was migrated

Among projects with recorded store size, median migration volume is about 11.3K records, with larger builds reaching roughly 137.8K at the 90th percentile and peaks near 1.8M. Exact counts depend on products, customers, orders, and related entities in scope.

Sample projects

• Magento → Shopify — ~371.3K records migrated
• Magento → WooCommerce — entities: Orders 175.5K, Customers 62.1K, Products 1.4K, Reviews 336 — total volume ~239.4K
• BigCommerce → Shopify — entities: Orders 85.6K, Customers 33K, Products 32.8K, Manufacturers 577 — total volume ~152.3K
• WooCommerce → Shopify — entities: Orders 110.8K, Products 18.2K, Customers 14.6K, Categories 147 — total volume ~144.4K

Every store is different—share your Source/Target carts and entity scope on a Migration Expert call and we will estimate a similar Custom Migration path.

What we need to scope category & collection mapping

Category depth, shared assignment rules, and how collections are built (manual vs rules) differ widely—even between two Shopify or WooCommerce stores. Your tree shape and merchandising rules must be inspected, not guessed.

Ideal input is staging or production access to walk the category tree and product assignments. A DB dump of category tables can substitute when live access is blocked; restoring and mapping that dump usually involves a deposit before we deliver a firm Custom Migration estimate.

Tip: Initial data-structure analysis is much more efficient when you prepare exact examples of the important attributes and fields on the Source, plus how each should be mapped on the Target store (sample products/customers/orders with field names, values, and desired Target destinations). Clear examples reduce discovery time and help Migration Experts quote and implement the customization accurately.

FAQs

Can products stay in multiple categories?

Yes when the target supports multiple assignments/collections. Rules are part of the mapping spec.

Should we redesign navigation during migration?

Often yes if the source tree is legacy debt. Migration is a natural cleanup window.

Do category URLs need redirects too?

If organic category landings matter, yes—pair this with SEO URL & 301 Custom Migration.

Plan categories before launch day—talk to Cart2Cart.