Install, configure, and run your Ecwid to WooCommerce migration.
These docs cover the complete Ecwid2Woo setup path: WordPress installation, Ecwid API credentials, sync mode selection, migration safety, and common troubleshooting steps.
Install the plugin in WordPress.
Ecwid2Woo is a WordPress plugin. It runs in your own WordPress admin and writes catalog data into WooCommerce.
Download the plugin
Go to the Ecwid2Woo download page and download the current ZIP file. Keep the ZIP intact for WordPress upload.
Upload in WordPress
In WordPress, open Plugins > Add New > Upload Plugin. Select the Ecwid2Woo ZIP, install it, then activate it.
Confirm WooCommerce is active
Ecwid2Woo runs inside WordPress and writes into WooCommerce. Activate WooCommerce before connecting Ecwid credentials.
Open E2W Sync settings
In the WordPress admin, open E2W Sync > Settings. Enter your Ecwid Store ID and API token, save, and test the connection.
Create credentials with read permissions.
Ecwid2Woo only needs read access to your Ecwid catalog and store profile. The token is stored in WordPress settings and used by your site during sync.
Where to find it
In Ecwid, open Apps > My Apps > API. Copy the Store ID and create an API token for the store you are migrating. Copy the generated token immediately because Ecwid may not show it again.
Required fields
Choose the right sync path.
Most first-time migrations should start with Full Sync. Use the individual modules for staged imports, updates, or troubleshooting.
Full Sync
Use this for a first migration. It imports categories first, then products, variations, images, stock, prices, SKUs, weight, and dimensions.
Category Sync
Use this when you need to build or repair the WooCommerce category hierarchy before importing products.
Product Sync
Use this for targeted product imports, product updates, or bulk product sync after categories are already in place.
Placeholders
Use this to review temporary category placeholders and sync metadata created while preserving category relationships.
How Ecwid2Woo protects long migrations.
The plugin is designed for interrupted, restarted, and low-resource migrations where retries are normal.
Fix the common migration issues first.
Most failed starts come from token permissions, server limits, or running products before categories.
Connection test fails
HTTP 403 from Ecwid
Timeouts or 503 errors
Products import into the wrong categories
When you need more help.
Use GitHub for public bugs and feature requests. Use the contact form when the details are private.