Replatforming to Ecwid: Standard row conversion rules

Migrate Shopify to Ecwid is the database workflow of exporting product listings and variations from Shopify and importing them into the Ecwid e-commerce platform.

Ecwid allows you to embed product catalog widgets across multiple websites and blogs. If you are moving your catalog from Shopify to Ecwid, exporting your products as a spreadsheet allows you to populate your Ecwid catalog in bulk.

Aligning Headers for Ecwid Imports

Format your spreadsheet columns to match Ecwid's required template:

• Modify `Title` to `Name`.
• Map `Body (HTML)` to `Description`.
• Map `Variant Price` to `Price`.
• Map `Image Src` to `Image URL`.

Executing the Import

First, use a local browser tool to export shopify products to csv cleanly. Modify the column headers in your editor, and import the file to Ecwid to build your catalog.

Practical Migration Workflow

A good migration starts with a clean source export, not with the import screen of the destination platform. For Replatforming to Ecwid: Standard row conversion rules, treat the Shopify catalog as a structured dataset: products, variants, option names, prices, image URLs, inventory fields, tags, vendors, SEO fields, and descriptions all need to be reviewed before anything is uploaded elsewhere. This reduces failed imports and makes it easier to spot missing variant relationships before customers see the new store.

Fields to Review Before Importing

• Product identity: Preserve handles, titles, vendors, product types, and tags so redirects, collections, and filters can be rebuilt predictably.
• Variant structure: Check option names, option values, SKUs, barcodes, weights, compare-at prices, and inventory policies before mapping them to the new platform.
• Media assets: Export image URLs with their product and variant associations so galleries, thumbnails, and color-specific images stay connected.
• Content fields: Review body HTML, SEO titles, SEO descriptions, and metafield-like content that may need a custom field in the destination system.

Step-by-Step Process

1. Export the full Shopify catalog and keep an untouched backup copy of the original CSV or Excel file.
2. Create a working sheet where destination columns are added beside the original Shopify columns.
3. Normalize option names, empty values, currencies, weight units, and product status values before importing.
4. Run a small test import with five to ten products that include simple items, multi-variant items, sale prices, and multiple images.
5. Compare the imported products against the source storefront and fix mapping issues before processing the full catalog.

Quality Checks That Prevent Rework

After the first import, check whether variants appear under the correct parent product, whether prices match the original store, and whether image order is preserved. Pay special attention to products with more than one option because flat files can accidentally split color, size, and material combinations into separate products. Also confirm that special characters in descriptions and titles display correctly after import.

Common Mistakes

• Importing directly from a raw export without cleaning blank option values or duplicate handles.
• Forgetting to preserve SKU formatting, especially SKUs that begin with zeros.
• Mapping image URLs without checking variant-specific image relationships.
• Testing only simple products and missing errors that appear on bundled, configurable, or multi-option products.

Example Spreadsheet Layout

For Replatforming to Ecwid: Standard row conversion rules, keep one tab for the untouched export, one tab for cleaned Shopify fields, and one tab for the destination mapping. Add columns for import status, required edits, image checks, and notes. This makes the migration reviewable by developers, operators, and content teams without changing the source data.

FAQ

Should every Shopify column be imported? No. Import only the fields your destination platform supports, but keep the original export as a reference in case a missing field becomes important later.

What should be tested first? Test products with multiple variants, sale prices, long descriptions, and several images because they expose most mapping problems early.

Next Steps

To put Replatforming to Ecwid: Standard row conversion rules into practice, start with one focused Shopify store and one clearly defined question. For example, decide whether you are checking prices, validating product ideas, preparing a migration, or cleaning catalog data. Export the catalog, review the fields that matter to that question, and write down the decision you will make from the result.

After the first pass, repeat the same workflow on a second store or a later snapshot. Comparing two clean exports is usually more useful than collecting a large amount of messy data. Keep your spreadsheet simple, document the filters you used, and save the raw export separately so your analysis can be checked or repeated later.