How to Import Products from Ecwid to Shopify (3 Methods That Work)

If your catalog already lives on Ecwid (Lightspeed eCom) and you are opening a Shopify store, the hard part is not finding products. It is rebuilding titles, options, and images without breaking variants. You can import products from Ecwid to Shopify with a remapped CSV upload, a public product URL importer, or careful manual rebuilds. This guide walks through all three so you can pick the path that matches your catalog size and how much cleanup you are willing to do.

Ecwid by Lightspeed states it has over 1 million registered merchants in 175 countries, and third-party trackers still count roughly 151,000 live Ecwid stores as of 2026 Q3. That footprint is why so many operators treat Ecwid as the current storefront (or the cart widget on an existing site) and Shopify as the next operating system. Owning a Shopify storefront means you stop bolting checkout onto a page builder and start running Markets, native checkout, and apps in one admin. If you are also planning a WooCommerce to Shopify product transfer or an Amazon product catalog move, the same discipline applies: import the product shell first, then rewrite for Google.

Why Do Ecwid Merchants Move Product Catalogs to Shopify?

Most Ecwid merchants open Shopify when they outgrow an add-on cart, need deeper apps, or want a full branded storefront instead of a widget on WordPress or a site builder. They are rarely deleting the Ecwid store on day one.

Running both during a transition is normal. Ecwid keeps the URLs and paid traffic you already earned while Shopify becomes the place you send email, ads, and new markets. A clean Shopify catalog lets you use native collections, checkout, and apps without another plugin stack.

There is also a practical ops reason. Ecwid uses hierarchical categories and a CSV row type system (product, product_option, product_variation). Shopify uses flat collections, Handles, and up to three option names per product. Importing the catalog shell saves hours. Restructuring options and metafields is still your job.

Another quiet reason is staffing. Widget carts often depend on whoever built the parent website. Shopify shifts day-to-day catalog work toward merchants who can edit products without a developer deploy.

Hot take: full-store migration apps sell peace of mind. The merchants who keep rankings treat a remapped product CSV plus a separate 301 redirect plan as the real source of truth, then use automation only where the spreadsheet would waste a week.

Can You Export a Product CSV Directly From Ecwid?

Yes. Ecwid's admin can export your whole catalog or selected products as CSV. That file is built for Ecwid re-import. It is not Shopify-ready. You still need remapping before Products > Import will accept it cleanly.

Per Ecwid's export docs, go to Catalog > Data Import & Export, scroll to Export data, and click Export Catalog (or Export Selected from Catalog > Products). The export typically includes names, SKUs, descriptions, prices, images, categories, options, and variation rows. Ecwid's column names and row types do not match Shopify's Handle, Title, Option1 Name/Value layout.

That gap is why a raw Ecwid export uploaded straight into Shopify creates duplicate products or broken variants. Shopify groups variants with a shared Handle. Ecwid variation rows share a parent product but do not include a Shopify Handle. Without grouping, each variation can become its own product. If you already live in spreadsheets, our walkthrough on importing products to Shopify from a CSV without errors covers the failure modes before you hit Upload.

Also set expectations early: product import tools move catalog data. They do not move customers, orders, or reviews. Treat products and everything else as separate migrations with separate tools, not one checkbox.

How Do You Import Products From Ecwid to Shopify Using a Remapped CSV?

CSV is the right method when you need bulk control, custom metafields, or a catalog too large to click through page by page. You export from Ecwid, rebuild a Shopify product CSV, then upload it from Products > Import.

Shopify's official docs are clear on the hard limits: your product CSV cannot exceed 15 MB, and for new products the Title column is required (Handle is also required when you add variants). Image URLs must be publicly reachable over HTTPS. Keep every variant row for a product under the same Handle, or Shopify will split the family. You can add up to 250 images per product through the CSV image fields when those URLs are public.

Suggested workflow:

1. Export the catalog from Ecwid and open the file in Google Sheets or LibreOffice (preserve UTF-8).
2. Separate product rows from option and variation rows using Ecwid's type column, then flatten options into Shopify Option1/Option2/Option3.
3. Open Shopify's sample product CSV and copy only the headers you need.
4. Generate a Handle per parent product, then place every variation row under that Handle.
5. Map columns: Title (from product_name), Body (HTML), Vendor, Type, Tags (flatten category paths), Variant SKU, Variant Price, Image Src, Variant Grams.
6. Flatten Ecwid category trees. Shopify has no nested categories. Use Product Type for the leaf name and Tags for parent paths.
7. Convert weights into grams as an integer if your Ecwid export uses kilograms or pounds.
8. Strip Ecwid-only widget HTML and broken relative image paths. Prefer absolute HTTPS image URLs that still resolve while Ecwid is live.
9. Upload under Products > Import, review the preview, then import.

CSV imports cannot be canceled once they start, and Shopify does not keep a friendly import history for rollback. Test five option-heavy SKUs first. If the file is over 15 MB, split it and keep parent/variant/image rows together by Handle.

One more CSV trap: sorting the file in Excel can reorder rows and break which image belongs to which variant. If you need to filter, re-sort back into Handle groups before upload. When an option value changes on an existing product during CSV update, Shopify can recreate variants and break apps that stored the old variant IDs. Prefer creating new products cleanly, then editing in admin for small fixes.

How Do You Import Ecwid Products With a Public URL Importer App?

URL import is the fastest path when you only need a subset of live product pages and those pages are publicly reachable. Paste a product URL, preview the listing, then push it into Shopify as a draft or active product.

Migratify is built for product URL and storefront imports into Shopify. Per Migratify's URL import docs, named sources include any Shopify store, Amazon, Etsy, Lazada, Daraz, BigCommerce, plus many other public websites. Ecwid is not listed by name. If your Ecwid product pages are public (no captcha wall, no login gate), treat them as a public website URL and test one product before you commit the catalog.

Here is the practical sequence with Migratify:

1. Install the app from the Shopify App Store and open the Import page.
2. Paste a direct Ecwid product URL (not a category page, search result, cart, or checkout link). Use the + button for several URLs if you are batching.
3. Confirm the product preview, then set import options (draft vs active, collection, Magic Edit, price multiplier).
4. Start migration and wait for the job to finish. Only one import runs at a time.
5. Confirm the product in Shopify before you publish, especially options mapped into variants.

Plan limits matter if you are testing. Migratify's Free plan allows up to 5 products in total (not per month). Standard is $14/month with unlimited imports, and Plus is $29/month for heavier Magic Edit usage. Migratify also requires a paid Shopify plan; stores still on Shopify's trial need to upgrade before importing.

What usually comes across on a successful public URL import: title, description, images (with variant images when the source provides them), options, price and compare-at price, SKU and barcode, tags (up to 30 per product), vendor, and product type. Videos on the source page are not imported, and Migratify does not import customers, orders, or reviews.

If the URL fails validation, or the page is behind a captcha/login, do not force URL paste. Use the remapped CSV path for owned Ecwid catalogs, or try Migratify's Chrome extension flow only when the product page can be opened and captured in desktop Chrome. We compared broader tool choices in our roundup of the best Shopify store migration apps.

When Does Manual Copy Make More Sense Than an Importer?

Manual copy is slower, but it wins when you only need a handful of hero SKUs rewritten for SEO. Paste nothing wholesale. Rebuild the page as a Shopify product.

Use manual entry when:

• You are launching with fewer than about 20 SKUs and every page needs unique copy.
• The Ecwid listing is thin, widget-generated, or written for a site you will not keep.
• Options use more than three attribute groups and need a deliberate split into separate products or metafields.
• You care more about Google ranking than speed of catalog transfer.

Manual does not mean starting from a blank page with no research. Keep the Ecwid listing open, reuse accurate specs, download your own product photos, and write a 300 to 600 word description aimed at search queries Ecwid never ranked for outside its own domain.

A hybrid works well for mid-size catalogs: CSV-import or URL-import everything as drafts, then manually rewrite the top 10% of SKUs by revenue before you publish them. Leave the long tail as drafts until you have time, or until paid ads need those URLs live.

What Product Data Usually Transfers, and What Does Not?

Expect the product shell to move. Do not expect Ecwid-only widgets or non-product data to follow.

Usually transfers with a careful CSV remap or a successful URL import: title, description HTML, image set, option/variation values (within Shopify limits), prices, SKUs/barcodes when present, vendor, type, and a limited tag set.

Often needs hand work: SEO title and meta description, collection membership, inventory by location, weight/shipping profiles, attributes mapped into metafields, and gift options that were Ecwid add-ons.

Does not transfer via Migratify: customers, orders, reviews, gift cards, store settings, and source-page videos. Collections are not imported as objects either, though you can drop imported products into one existing manual collection during import settings.

Shopify raised the per-product variant ceiling to 2,048 variants for all merchants on October 15, 2025, but you still only get three option names per product. If an Ecwid product uses four or more option groups, split the product or demote extra attributes to metafields before you publish.

Also remember that Migratify imports products only. If your migration brief still lists customers or order history, use Shopify's native customer CSV tools or a dedicated full-store migration service for those pieces. Do not expect a product importer to become a platform clone. For marketplace-shaped catalogs, the same three-method pattern shows up in our guide on importing products from Shopee to Shopify.

What Should You Clean Up After an Ecwid to Shopify Product Import?

Publish nothing until you finish a cleanup pass. Platform imports create drafts that look finished and still convert poorly.

Run this checklist on a sample of imported products:

• Handles: Replace auto-generated or numeric leftovers with clean, readable slugs.
• Options: Confirm option names (Size, Color, Material) and that variants did not explode into duplicate products.
• Pricing and tax: Confirm the price Shopify displays matches how you intend to sell, including tax-inclusive vs exclusive habits from Ecwid.
• Images: Fix broken relative paths, set alt text, and attach the right image to each variant.
• Copy: Remove widget boilerplate and rewrite for Google and your brand voice.
• Inventory: Turn on tracking only when your numbers are real; do not invent stock from a stale export.
• Redirects: Map old Ecwid product URLs to new Shopify product URLs before you cut traffic over.
• Mobile PDP: Spot-check the first screen on a phone. Long pasted HTML often looks fine on desktop and broken on mobile.

For a deeper cleanup playbook covering duplicates, tags, and broken variants, use how to clean up product data after a Shopify migration. If you also need redirects after cutover, follow how to set up 301 redirects after a Shopify migration.

Should You Keep Ecwid Live After You Launch Shopify?

Yes, for most catalogs that already get traffic. Shutting Ecwid off on launch day usually cuts organic and referral revenue before Shopify SEO and ads catch up.

Run both channels with clear rules:

1. Keep Ecwid serving existing product URLs until redirects are verified.
2. Send owned traffic (email, social, brand search) to Shopify.
3. Sync inventory carefully so one channel cannot oversell the shared pool.
4. Differentiate Shopify copy so Google has a reason to rank your new domain pages instead of thin mirrors.

When the Shopify store converts paid and organic traffic on its own, you can retire the Ecwid cart or Instant Site. Until then, treat Ecwid as the legacy storefront and Shopify as the brand home.

If your next move is another platform catalog, the same three-method pattern applies. Use CSV when you own the export, use a public URL importer when pages are openly reachable, and rewrite hero products by hand when SEO matters more than speed. For same-platform copies, see how to migrate products from one Shopify store to another. For Lazada-style marketplace imports, see how to import products from Lazada to Shopify.