What the migration covers
We separate Ecwid’s store data from the surrounding website and its content. The project defines whether that website remains in place or becomes part of the Shopify rebuild.
Catalog, options and inventory
We inspect the Ecwid catalog export and map names, SKUs, descriptions, prices, images, categories, and available option data. A trial import checks the products with variations or custom purchase choices. Stock is reconciled against the agreed source of truth before launch.
Customer and order records
Ecwid provides separate exports for customers and orders. We agree which fields and history the destination needs, then select an appropriate import route. Reconciliation covers customer associations, order totals, option values, and fulfillment status so old records remain distinguishable from new purchases.
Host website and product links
For an embedded store, we review the host website’s navigation, product links, and content alongside the Ecwid data. A Shopify storefront may replace the shop while the surrounding website remains. We agree domain and URL ownership, then map old product entry points to their new destinations.
Sales channels and store behavior
Payment, shipping, marketing, fulfillment, and sales-channel connections need destination configuration. We check which systems use Ecwid product identifiers and how the Shopify identifiers will replace them. Recent orders, inventory changes, and outstanding fulfillment work are included in the final handoff.