Ecwid → to Shopify

Ecwid to Shopify: the store, the website around it, and the URLs in between

Ecwid is rarely a website on its own. Most Ecwid stores are a widget embedded in a WordPress, Wix, Squarespace or hand-built site, and the rest run on Ecwid’s Instant Site. That makes an Ecwid to Shopify migration two jobs at once: moving the store data, and deciding what happens to the website the store lives inside. This guide covers both, along with the URL problem that catches most Ecwid stores out, based on how we run these projects.

Why stores leave Ecwid

Ecwid, owned by Lightspeed since 2021, is a sound product for adding a shop to an existing site. The reasons to move tend to arrive as the store grows:

• Two systems to maintain. An embedded store means a website platform, its plugins and hosting, plus Ecwid on top. Every design change, speed problem or plugin update involves both, and neither vendor owns the whole page.
• Pricing. Ecwid replaced its free plan with a paid entry plan in 2025 and raised prices on its paid plans in March 2026. Product counts are capped by plan below the top tier, so a growing catalog pushes stores up the ladder.
• Checkout and conversion. Shopify’s checkout, with Shop Pay and checkout extensions, is the reason many owners give. Ecwid’s checkout is solid, but the tools around it are fewer.
• Apps and integrations. Ecwid has an app market, but the larger ecommerce stack (Klaviyo flows, Recharge, Gorgias, Loop, the review apps) is built Shopify-first.
• SEO on embedded stores. Stores embedded on older setups still serve hash-bang URLs, and even clean URLs sit inside a host page the store does not control. A native Shopify store owns its own product pages, titles and structured data.

To be fair to Ecwid, if you only sell a few dozen products on an existing site and it works, moving may not pay for itself. We say so in the survey when that is the case.

What migrates from Ecwid to Shopify

Ecwid provides CSV exports for the catalog, orders and customers, and a REST API available on any paid plan. Between them, most of the store can be carried across.

Data	Source on Ecwid	Moves to Shopify?
Products, SKUs, prices, stock, weights, categories, images	Catalog export (CSV) or the REST API	Yes. Categories become Shopify collections, and nested categories are rebuilt as collections plus navigation.
Options and variations	The newer catalog export for stores created after May 2023; the REST API for everyone else, because the legacy export does not include variations	Yes, with mapping. Ecwid variations become Shopify variants. Shopify allows three options per product, so products with more selection options are restructured first.
Checkbox options, text fields, date pickers, file uploads	Product options and input fields	Rebuilt. These are not variants on Shopify; they move to a product options app or line item properties.
Customers and addresses	My Sales, Customers, export (CSV) or the API	Yes, with marketing consent carried exactly as recorded.
Customer passwords	Not exportable	No, from any platform. Customers set a new password or use Shopify’s passwordless sign-in.
Orders	My Sales, Orders, export (CSV) or the API	Yes, as real Shopify orders with original numbers, dates and a paid transaction. Refunds and tracking numbers are handled separately (see Tools).
Digital products	Files attached to products	Yes, re-uploaded to a digital delivery app. Ecwid files can be far larger than Shopify’s app allows, so large files are checked first.
Subscriptions	Recurring subscriptions via Stripe or Lightspeed Payments	Rebuilt as plans on Shopify. Saved payment methods rarely transfer, so subscribers usually re-enter card details.
Discount codes and gift cards	Discounts and gift card records	Recreated on Shopify from the lists.
Pages, blog and design	The host website or Instant Site	Pages and blog posts are moved; the design is rebuilt on a Shopify theme, usually Horizon.

Ecwid URLs, redirects and the hash-bang problem

Ecwid store URLs depend on how and when the store was embedded, so the first task in any audit is finding out which forms Google has indexed. The common patterns:

• Hash-bang URLs on older embeds: /store/#!/My-Product/p/123456, with categories in the matching /c/ form.
• Clean URLs on the WordPress plugin and custom sites with clean URLs enabled: /store/My-Product-p123456 and /store/My-Category-c123.
• Query-based URLs on some custom sites: /shop?store-page=My-Product-p123456.
• Instant Site URLs: /products/My-Product-p123456, or a custom slug such as /products/my-product.

Shopify uses /products/handle and /collections/handle. Clean and query-based URLs can be 301-redirected in the normal way, and we map each one using the numeric product or category ID in the URL, which is more reliable than matching names.

Hash-bang URLs are different. Everything after the # is a fragment, and browsers never send fragments to the server. A request for /store/#!/My-Product/p/123456 reaches the server as /store/, so no server-side redirect, including Shopify’s URL redirects, can tell which product was requested. We handle these in two ways. If the old host site stays online on another address, we place a small JavaScript redirect on the old store page that reads the fragment and sends visitors to the matching Shopify product. If the domain moves to Shopify, we add the same script to the Shopify theme on the page that replaces /store. Either way, /store/ itself gets a redirect to the new catalog. Clean URLs still work on stores that switched to them, so both forms are usually in search results and both get mapped.

Tools

Cart2Cart and LitExtension both list Ecwid as a source for Shopify migrations, covering products, customers and orders. We are a Cart2Cart partner and use it where it fits. Either tool is fine for a first pass on products and customers. The gaps are predictable: they do not carry shipment tracking numbers, they tend to import refunded orders as plain paid orders, and their redirect options build targets from guessed slugs rather than the URLs Google has actually indexed, which matters a great deal with Ecwid’s several URL forms. Neither tool moves the host website. We finish those parts ourselves: tracking and refunds from the API, redirects from a crawl and the Search Console export, and the site content by hand or script.

How we run it

1. Audit. We export the catalog, orders and customers, pull the same data from the API, and crawl the host website as well as the store: pages, blog, indexed URL forms, apps and sales channels. You get a written scope with a fixed price.
2. Build in a free development store. As a Shopify Plus Partner we build in a Shopify development store, so you pay Shopify nothing until launch. Theme, checkout, payments, shipping and taxes are set up before any data arrives.
3. Catalog. Products, variants, collections, images and SEO fields, with option-heavy products restructured to fit Shopify’s three-option model and input fields rebuilt.
4. Customers. Records, addresses, tags and consent.
5. Orders. Original numbers and dates, paid transactions, refunds as refunds, and fulfillments with tracking numbers.
6. The host site’s pages and blog. Content from WordPress, Wix, Squarespace or Instant Site is moved into Shopify pages and blog articles, with images rehosted.
7. Redirects. A 301 for every clean, query-based and Instant Site URL, the JavaScript handler for hash-bang URLs, and a test of each one before launch.
8. Sample, then full import, with reconciliation. A sample of awkward records for your sign-off, then the full run, with every source row accounted for.
9. Cutover with a delta sync. Orders and customers created since the full run are brought across, then DNS moves. Ecwid stays active until Shopify is confirmed.
10. Post-launch SEO evaluation. Once Google has re-crawled the store and the first real analytics exist, we review coverage, redirects hit, 404s and rankings, and fix what the data shows.

Cost and timeline

Ecwid migrations start at $2,500 for stores under 500 products and 5,000 orders ($3,500 for larger stores), and typically take six to eight weeks. Moving the host website’s content as well, rebuilding subscriptions, and reconnecting integrations are quoted as a fixed price after the audit rather than billed by the hour. Payment terms are 50% to begin and 50% once the store is live and you are fully satisfied with the figures.

Embedded store or Instant Site: what changes

An Instant Site store is the simpler case. The site and store are one Ecwid product, the pages are few, and the URLs are already clean, so the migration is mostly data and redirects. An embedded store adds a second platform. The website may have years of blog posts, landing pages and plugin-driven features, and its own hosting and domain setup. The audit tells us which pages earn traffic, which plugins do real work, and whether the domain points at the website host, Ecwid, or both. That decides the cutover plan more than the store data does.

Keep WordPress and add Shopify, or move everything?

Many Ecwid stores run inside WordPress, and owners often ask whether they can keep the site and swap the store. It is possible: Shopify’s Buy Button can sell on an outside site, or the store can move to a subdomain such as shop.example.com while WordPress stays on the main domain. The cost is the same one you have today, two platforms to run, plus a split between the content and the product pages for SEO. For most stores we recommend moving everything to Shopify, with the blog moved into Shopify’s blog, so there is one site, one theme and one domain. Where a WordPress site is large or heavily customized, keeping it is a reasonable choice, and our WordPress to Shopify guide covers the full move.

Subscriptions, digital goods and sales channels

Subscriptions. Ecwid’s recurring subscriptions run through Stripe or Lightspeed Payments on its higher plans. On Shopify they become Shopify Subscriptions or an app such as Recharge. We recreate each plan and billing interval, then plan the move of active subscribers with you, since payment details usually have to be re-entered.

Digital goods. Ecwid allows very large downloadable files. Shopify’s free Digital Downloads app caps files at 5 GB, so larger files are split, compressed or moved to a delivery app built for bigger files.

Sales channels. Ecwid connects to Facebook, Instagram and TikTok, and to Amazon and eBay through partner apps. Each channel is reconnected on Shopify after the catalog is final, never before, because a sync against an unfinished catalog creates duplicates. Ad catalogs and product feeds are pointed at the new product IDs at the same time.

What you get at handover

• A reconciliation ledger for products, variants, customers and orders that accounts for every source row.
• The redirect map, with the status each old URL returned in testing, including the hash-bang handler.
• A consent report showing how many customers came across subscribed, and on what basis.
• A list of what was rebuilt rather than imported: input fields, subscriptions, discounts and gift cards.
• A recorded walkthrough of the Shopify admin for your team.

Questions we settle in the survey

• Is the store embedded, and in which platform, or is it an Instant Site?
• Which URL forms are indexed: hash-bang, clean, query-based or Instant Site?
• Does the website move to Shopify too, or stay where it is?
• How much order history do you want to keep?
• Do you sell subscriptions, digital files or made-to-order items with input fields?
• Which sales channels, apps and payment methods are connected today?

Frequently asked questions

If you are planning the move, the migration survey takes about ten minutes and gives us what we need for a first assessment. If your Ecwid store sits inside WordPress, read our WordPress to Shopify guide, and if you use Lightspeed for retail, see our Lightspeed to Shopify guide.