Move off a legacy PIM
Leaving your old PIM? Move a sample batch first.
Import a batch from your old PIM’s CSV or Excel export, run the agents, then test a publish.
From one big switch to batches.
TodayOne big switch, with the whole catalog moving at once.
With CataZentaStart with one batch imported from your old PIM’s CSV or Excel export.
TodayGaps in old data show up after the switch.
With CataZentaRun agents on that batch to flag gaps, duplicates and category placement issues.
TodayHow listings will turn out stays a guess until launch day.
With CataZentaPublish that batch to a Shopify development store and see each SKU’s result, or build a CSV or Excel feed.
How it works
One batch first. Then the rest.
Three steps on your own products.
01Import
Import a representative batch.
Use a CSV or Excel export from your PIM. Keep the mapping for later batches.
02Review
Run the agents, review the suggestions.
Suggestions wait in one queue by default. Duplicates come back as findings.
03Publish
Test a publish first.
Send the batch to a Shopify development store and see each SKU’s result, or export a CSV or Excel feed. On your live Shopify store, a push would create new products rather than update yours.
Agents and publishing come with PIM Hub.
Holds the families, attributes and category trees you set up before the first import.
Suggest fixes that wait for approval by default.
Publishes the first batch to a Shopify development store, or builds a feed.
Good to know
Before you switch.
Still curious? Email the founders
Do you import from Akeneo, inRiver or Salsify directly?
Not directly. Set up your families, attributes, attribute options and category trees in CataZenta first: imports bring in products and variants, not the data model. Then export products from your current PIM as CSV or Excel files and import them with a saved column mapping. Columns with a language suffix, such as DESCRIPTION-en_US, get suggested matches. Columns that also name a channel, such as description-en_US-ecommerce, are mapped by hand. Each row can name the family, variant family and categories it belongs to. Imports bring in product data, not images: upload images to the DAM add-on, then attach them to products.
Can both systems run in sync?
Not as a live sync. While you move, re-import newer exports from your old PIM as often as you need: products with the same product code are updated, and new codes become new products.
Do variants come across?
Yes, one level deep. Products and variants import through separate profiles, each with its own saved column mapping, and each import has its own result and error files. Each variant sits under one parent product, so plan to map a two-level model, such as Akeneo’s product models and sub-models, to one parent and its variants.
Can we pilot the agents with you?
Yes, through the design partner pilot: 6 to 8 weeks with the founders, running the agents on a sample of your own products, free of charge. It covers a sample, not a managed migration.
Related reading How to evaluate a PIM in 2026: test it on your own catalog
Start with one batch, then move the rest.
Once we connect, we load a sample of your products.
