Skip to main content

Migration overview

Moving catalog data into CataZenta from spreadsheets, legacy PIM, or ERP exports.

Common sources​

SourceApproach
SpreadsheetImport profile + CSV/XLSX job
ERP exportScheduled file drop (SFTP) or API middleware
Another PIMExport CSV from old system → map columns → import job
MarketplaceUsually outbound only; use PIM as master after cutover

Phase 1 — Model​

  1. Define product families and attributes in CataZenta.
  2. Map old columns → new attributes (spreadsheet matrix).
  3. Plan category trees (internal vs Amazon/Shopify).

Phase 2 — Load​

  1. Pilot import (100–500 SKUs).
  2. Validate families, variants, and locales.
  3. Fix import job errors via job items.

Phase 3 — Enrich​

  1. Completeness rules per channel.
  2. DAM migration (bulk upload + link).
  3. Zen AI or editors fill descriptions.

Phase 4 — Syndicate​

  1. Connections to dev stores / Amazon sandbox.
  2. Export profiles and test jobs.
  3. Production cutover with monitoring.

Attribute mapping tips​

  • One SKU column → variant identifier
  • Separate columns per locale for translated text
  • Do not import channel-specific IDs as PIM primary keys unless needed for mapping table

Getting help​

CataZenta professional services can assist with mapping workshops and cutover planning.