Migrating from a legacy PIM
This guide covers moving from a legacy PIM (or spreadsheet-led catalog) into CataZenta — without losing channel mappings or approval history you care about.
Principles
| Principle | Why |
|---|---|
| Model first | Map source families → CataZenta families before bulk load |
| Channels early | Completeness only works when channels exist |
| Pilot then scale | 50–200 SKUs prove mappings before full cutover |
| Parallel run | Keep old PIM read-only until first channel export succeeds |
Phase 1 — Discovery (week 1)
- Export attribute and family definitions from the source system (CSV or API).
- List channels you publish to today and locales per channel.
- Document variant rules (axes, parent/child).
- Inventory assets — folder structure, naming, rights metadata.
- Note connectors you must keep (Amazon, Shopify, ERP).
Deliverable: mapping spreadsheet — source attribute code → CataZenta attribute code, with locale/channel flags.
Phase 2 — Foundation (weeks 2–3)
Follow Catalog fundamentals:
- Attribute groups and attributes
- Product families + variant structures
- Category tree
- Channels and completeness thresholds
- DAM folders and link rules
Do not import 100k SKUs before families validate on 10 sample products.
Phase 3 — Pilot load (week 4)
| Data | Approach |
|---|---|
| Products & variants | API or import job — Create product |
| Attributes | Bulk update — Update attributes |
| Assets | DAM upload + link assets |
| Categories | Assign during import |
Validate completeness on each target channel for every pilot SKU.
Phase 4 — Syndication proof (weeks 5–6)
- Configure connector (e.g. Amazon).
- Run export to channel.
- Fix mapping errors from job results.
- Compare live listing or staging feed to source PIM.
Phase 5 — Cutover (weeks 7+)
- Freeze writes in legacy PIM
- Final delta import
- Switch merchandisers to CataZenta UI
- Enable workflows and Zen AI for net-new enrichment
- Optional: MCP for agent automation post-cutover
Legacy PIM concept mapping
| Legacy PIM concept | CataZenta approach |
|---|---|
| Families / product types | Product families — same idea |
| Attribute groups | Attribute groups |
| Channels / locales | Channels with per-locale values |
| Categories | Category tree + channel mappings |
| Rules (completeness) | Family + channel completeness |
| Reference entities / associations | Model as families or attributes per your data — plan with solutions team |
| API | REST v1 — API reference |
Many legacy PIMs offer large connector marketplaces; CataZenta emphasizes native Amazon/Shopify flows, API/MCP, and AI. Map connector gaps during evaluation.
What to migrate vs rebuild
| Usually migrate | Often rebuild |
|---|---|
| SKU codes, titles, bullets | Broken attribute mappings |
| Approved copy per locale | One-off spreadsheet columns |
| DAM masters | Duplicate low-res assets |
| Category assignments | Unused legacy attributes |
Help from CataZenta
Enterprise migrations include workspace setup, mapping workshops, and connector validation. Request a demo and mention your source PIM.
Related
- Migration guide — general checklist
- Why CataZenta
- Choose your path
- PIM migration with CataZenta: how a sample-batch migration works, on catazenta.com