VANKPA
The short answer
Catalog migration is a data project before it is a storefront project. Clean product identifiers, variants, categories, images, and descriptions before importing them. A smaller test migration helps reveal problems while the current store remains available.
Create a field map
Identify which system owns each field: SKU, product name, price, inventory, attributes, and product URL. Do not assume two platforms use the same meaning for a similar column. Record required fields and transformation rules. A consistent product identifier gives the team a way to reconcile old and new records.
Separate cleanup from import
Remove accidental duplicates and resolve contradictory product information in an approved source file. Keep discontinued products and unpublished drafts distinct from active listings. Preserve a copy of the original export so changes can be traced. Editing values manually in several systems creates uncertainty about which version is authoritative.
Rehearse with variety
Test simple products, multiple variants, missing images, unusual characters, and items with special shipping rules. Compare totals and inspect individual records. A file importing successfully does not prove the catalog is correct. Staff should review descriptions and prices, while the implementation team checks mappings and image references.
Control the cutover
Decide when product edits pause, how late changes will be captured, and who authorizes release. Reconcile the final import with the approved source and verify important product URLs. Keep the rollback material accessible until the store is stable. The exact sequence depends on the selected platforms and the amount of live activity.
When to take the next step
Prepare the catalog before the visual store redesign reaches final approval. Product structure affects filters, variant selection, and navigation. If staff disagree about naming or categories, resolve those definitions in the source data. A design cannot consistently present a catalog whose underlying records have incompatible rules.
- MerchandiserApproves data
- DeveloperMaps fields
- StaffInspect test import
- OwnerApproves cutover
Adapt these responsibilities to your team and project scope.
Before you start
- Choose one authoritative catalog file.
- Test representative variants and image paths.
- Capture changes made after the first export.
Questions clients ask
Is a successful CSV import enough?
No. Validate prices, variants, images, categories, and customer-facing pages after import.
Should duplicate products be deleted automatically?
Only under agreed rules. Similar names can represent different products or variants, so uncertain matches need review.
Turn the question into a plan
Discuss your next step.
Bring your current setup and the requirements above to a project conversation.