Clean SKU and Variant Data Before a Store Migration

Catalog migration is a data project as much as a website project. A new theme will not repair duplicate SKUs, inconsistent variant names or missing images. Cleaning the source catalog first makes the import test meaningful and reduces post-launch surprises.

Define the product model

Separate a parent product from each purchasable variation. Map fields such as SKU, parent ID, attribute name, value, price, stock, image, URL and status. Keep one source of truth for each field. If a size has its own stock and price, the target platform must represent that relationship accurately.

Audit the source before mapping

Export the catalog and identify duplicate identifiers, missing values, invalid image links, inactive items and options with inconsistent spelling. Decide which records are retired rather than transferring every historical artifact. Document exceptions instead of silently guessing.

Run a representative sample import

Choose a simple product, a multi-variant item, an out-of-stock item and an item with special delivery rules. Compare the imported product and checkout outcome with the source record. Then test search, filters, inventory and order emails. Megvi’s published Fyonka case confirms a migration involving 6,000 variations across 1,500 SKUs; it does not by itself prove a ranking or conversion uplift.

Worked decision example

Illustrative catalog row: one parent shirt has three sizes and two colors. Each sellable option needs a stable identity, while the parent supplies shared copy and images. If the source uses “Large,” “L” and “large” for the same size, normalize the value before import and log the mapping. Import that item first, then check the variant selector, stock, image and order line. Do not treat an import count alone as evidence that the catalog works.

Practical review checklist

• Is every sellable variant uniquely identifiable?
• Are the parent-child relationships preserved?
• Can staff correct an imported item using the handover instructions?

Where to go next

Fyonka migration case · ecommerce website service · ecommerce migration checklist