This post covers the X-Series-specific parts of a Shopify-to-E-Series move. For the URL formats Ecwid uses, how to build a redirect map, and how to implement redirects across different hosting setups, read How to Migrate to Ecwid Without Losing SEO. Most of it applies directly here.

Why an X-Series merchant should consider this

The case is consolidation, not features. E-Series syncs products, inventory, customers, and gift cards directly with your X-Series register: one catalog, one customer record, one reporting view. On Core or Plus, E-Series Business is already in your subscription, so canceling Shopify removes that monthly bill outright.

The trade-off is Shopify's app ecosystem. If you've wired half a dozen Shopify-specific apps into fulfillment, marketing, or accounting, inventory them first. Some have direct E-Series equivalents, some don't, and some have rougher ones that need extra setup. For a brick-and-mortar retailer whose web store supports the physical business, consolidation usually wins. For a Shopify-first business that happens to use Lightspeed at the till, it usually doesn't.

What's different from a generic Ecwid migration

Three things are X-Series specific.

Catalog source: Shopify or X-Series POS

For most Ecwid migrations, you're moving from the old platform's catalog into Ecwid directly. For an X-Series merchant, the better default is to skip Shopify entirely and sync E-Series from the retail POS.

If your X-Series catalog is the source of truth (accurate stock, clean product data, correct pricing), turn on the X-Series ↔ E-Series sync and let it pull products in. You bypass the CSV-export-and-clean step entirely. Migrate from Shopify only if your Shopify catalog has data that POS doesn't (web-only products, web-specific descriptions, variants the till never sees), and even then, consider bringing those into X-Series first and syncing afterwards. Otherwise you're committing to permanent manual reconciliation between POS and web.

Terminology mapping

Shopify and E-Series use the same product model with different labels. Shopify "collections" are E-Series "categories." Options work the same way in both. A Shopify "variant" (a specific Size + Color combination) is a "combination" in E-Series. The CSV mapping is mostly mechanical.

What doesn't translate: Shopify metafields, custom attributes, and anything backed by a Shopify-specific app. Inventory those before migration. Some can be recreated as E-Series product attributes or option labels; others need to live in Lightspeed Retail's product fields and reach E-Series via the sync.

Customer and order data

Shopify customer records (email, name, addresses) export and import cleanly. Order history does not. E-Series has no place to store historical Shopify orders and no standard import path for them.

Pick a clean break date, export your full Shopify order and customer history, and archive it before canceling. You'll need it for tax records, returns, customer service questions about old purchases, and any analysis you do later. This is the part of the migration that's hardest to undo, so do it before you cancel Shopify, not after.

The redirect part

Every Shopify product and category URL changes when you move to E-Series. Whether you keep your rankings depends on whether redirects are in place before the domain switch. The full breakdown of Ecwid URL formats, how to build a redirect map, and how to implement redirects on Lightspeed-hosted Instant Site versus an embedded setup is in How to Migrate to Ecwid Without Losing SEO.

Shopify URL patterns are regular enough that wildcard rules cover most of the work. /products/* to your E-Series product path and /collections/* to your category path handle the bulk of the catalog, with individual rules only where the slug actually changed. For a catalog with hundreds or thousands of SKUs, this is what makes the migration tractable instead of painful.

If your E-Series store is embedded on WordPress, Wix, Squarespace, or a custom site, the platform's redirect tools can't target specific Ecwid product URLs (they're JavaScript-rendered views, not server-side pages). Redirect & 404 Manager handles the storefront-level piece for embedded stores: CSV import for the bulk redirect map, wildcard rules, and a 404 dashboard for catching missed redirects after launch. It uses JavaScript redirects rather than server-side 301s, which is weaker than a 301 in principle but the only practical option for embedded stores and far better than letting old URLs return 404s. It doesn't replace server- or DNS-level redirects where you have access to those.

Pre-migration checklist

Before you touch either platform:

  • Export your Shopify product catalog and your full order/customer history. Archive the order export, since you can't reimport it later.
  • Decide the catalog source: migrate from Shopify, or sync from X-Series POS.
  • Inventory Shopify metafields, custom apps, and anything that doesn't have an obvious E-Series equivalent.
  • Pull organic traffic by URL from Google Search Console (Performance > Pages). This list is what your redirect map has to cover.
  • Schedule go-live for a quiet weekday evening, not the run-up to a seasonal peak.

Migration steps

The migration follows the standard Ecwid shape: set up the new store, migrate the catalog, build the redirect map, implement redirects, go live, monitor. The canonical post covers each step in detail. A few X-Series-specific notes:

Setting up E-Series

Activate from your Lightspeed Retail dashboard. If you're embedding in an existing site, install the E-Series widget there. If you're using the Lightspeed-hosted storefront, point your domain at it. Keep Shopify live throughout.

Catalog migration

Either turn on the X-Series ↔ E-Series sync (preferred when POS is the source of truth) or import a cleaned Shopify CSV (when web has data POS doesn't). Once products exist in E-Series, record the product IDs. You need them to finish the redirect map.

Going live

Point your domain at E-Series, spot-check a handful of old Shopify URLs to confirm redirects fire, update your XML sitemap, and use Google Search Console's Change of Address tool if your domain changed.

Canceling Shopify

Wait at least 30 days after go-live, ideally until organic traffic has stabilized. You may discover missing redirects, missing product data, or a customer service question that needs the Shopify admin. Once you cancel, that access is gone.

Common Shopify-to-E-Series mistakes

Not exporting Shopify order history before canceling

This is the hardest one to recover from. Order history doesn't transfer; if you cancel without the export, it's lost for tax and customer service purposes.

Migrating the Shopify catalog when X-Series is already clean

The sync path is shorter, avoids CSV reconciliation, and prevents permanent POS/web drift. Default to sync unless you have a specific reason not to.

Skipping wildcard redirects

Shopify's URL patterns are regular enough that two or three wildcard rules cover most of the catalog. Hand-typing hundreds of redirects when the patterns are predictable is painful and error-prone.

Forgetting category pages

Most merchants map /products/* and forget /collections/*. Collection pages often carry a meaningful share of organic traffic and link equity.

The short version

For an X-Series merchant on a separate Shopify store, the move to E-Series is a consolidation play first and an SEO project second. The consolidation case rests on one bill instead of two, one catalog instead of two, and X-Series-native sync. The SEO part is the same redirect mechanics any Ecwid migration needs, plus three X-Series-specific decisions: where the catalog comes from, what Shopify data doesn't transfer, and when to cancel Shopify.

If you're running E-Series as an embedded store and need to handle the migration redirects, Redirect & 404 Manager on the Ecwid App Market does the storefront-level redirect work that platform tools can't. 14-day free trial, $5.99/month after, all features included.