Add-on Platform Compatibility

Add-on Platform Compatibility

Every Add-on requires support from both Source and Target platforms. If either side is unsupported, that Add-on cannot run for the path. A successful connection does not establish Add-on eligibility.

Standard Add-ons

For functions, prices, and limits, see the Add-on reference.

• ☑ means the Add-on is supported for that side or Source setup within the Standard compatibility scope.
• ☐ means it is unsupported for that side or Source setup.
• The active migration remains authoritative for the exact fields, operators, mappings, tables, columns, and Value Types exposed for configuration.

Source compatibility

Source Platform or Source setup	Data Filter	Data Transformation	Advanced Data Mapping	Advanced Database Mapping	Data Update
3DCart	☑	☑	☑	☐	☑
AbanteCart	☑	☑	☑	☑	☑
AbleCommerce	☑	☑	☑	☑	☑
Adobe Business Catalyst	☑	☑	☑	☑	☑
Adobe Commerce	☑	☑	☑	☑	☑
AmeriCommerce	☑	☑	☑	☐	☑
AspDotNetStorefront	☑	☑	☑	☐	☑
Bagisto	☑	☑	☑	☑	☑
Big Cartel	☑	☑	☑	☑	☑
BigCommerce	☑	☑	☑	☐	☑
Bluepark	☑	☑	☑	☐	☑
Clover	☑	☑	☑	☐	☑
CommerceHQ	☑	☑	☑	☐	☑
CS-Cart	☑	☑	☑	☑	☑
CSV	☑	☑	☑	☑	☑
CubeCart	☑	☑	☑	☑	☑
DJ-Catalog2	☑	☑	☑	☑	☑
Drupal	☑	☑	☑	☐	☑
Easy Digital Downloads	☑	☑	☑	☑	☑
EasyStore	☑	☑	☑	☑	☑
eBay	☑	☑	☑	☐	☑
Ecwid	☑	☑	☑	☐	☑
EKM	☑	☑	☑	☑	☑
ePages	☑	☑	☑	☐	☑
eShop	☑	☑	☑	☑	☑
Gambio	☑	☑	☑	☑	☑
GoDaddy	☑	☑	☑	☑	☑
Helcim Commerce	☑	☑	☑	☐	☑
HikaShop	☑	☑	☑	☑	☑
Interspire	☑	☑	☑	☑	☑
J2Store	☑	☑	☑	☑	☑
Jigoshop	☑	☑	☑	☑	☑
JooCart	☑	☑	☑	☑	☑
Joomla!	☑	☑	☑	☑	☑
JoomShopping	☑	☑	☑	☑	☑
Jumpseller	☑	☑	☑	☐	☑
LemonStand	☑	☑	☑	☐	☑
Lightspeed eCom (C-Series)	☑	☑	☑	☐	☑
Lightspeed eCom (E-Series)	☑	☑	☑	☐	☑
Lightspeed Retail (R-Series)	☑	☑	☑	☐	☑
Lightspeed Retail (S-Series)	☑	☑	☑	☐	☑
Lightspeed Retail (X-Series)	☑	☑	☑	☐	☑
LiteCart	☑	☑	☑	☑	☑
Loaded Commerce	☑	☑	☑	☑	☑
Magento	☑	☑	☑	☑	☑
Maropost	☑	☑	☑	☐	☑
MijoShop	☑	☑	☑	☑	☑
Miva Merchant	☑	☑	☑	☐	☑
Neto	☑	☑	☑	☐	☑
nopCommerce	☑	☑	☑	☑	☑
OpenCart	☑	☑	☑	☑	☑
osCMax	☑	☑	☑	☑	☑
osCommerce	☑	☑	☑	☑	☑
OXID eShop	☑	☑	☑	☑	☑
PinnacleCart	☑	☑	☑	☐	☑
Plentymarkets	☑	☑	☑	☐	☑
PrestaShop	☑	☑	☑	☑	☑
QuickBooks	☑	☑	☑	☑	☑
Quickbutik	☑	☑	☑	☐	☑
Salesforce	☑	☑	☑	☐	☑
Shift4Shop	☑	☑	☑	☐	☑
Shop-Script	☑	☑	☑	☑	☑
ShopBase	☑	☑	☑	☐	☑
Shopify	☑	☑	☑	☐	☑
Shopp	☑	☑	☑	☑	☑
Shopware	☑	☑	☑	☑	☑
ShopWired	☑	☑	☑	☐	☑
Square	☑	☑	☑	☐	☑
Squarespace	☑	☑	☑	☑	☑
Storeden	☑	☑	☑	☐	☑
Storenvy	☑	☑	☑	☑	☑
SunShop	☑	☑	☑	☑	☑
Sylius	☑	☑	☑	☑	☑
Ubercart	☑	☑	☑	☐	☑
Upgates	☑	☑	☑	☐	☑
Vend	☑	☑	☑	☐	☑
VirtueMart	☑	☑	☑	☑	☑
Volusion	☑	☑	☑	☑	☑
VTEX	☑	☑	☑	☐	☑
Weebly	☑	☑	☑	☑	☑
Wix, API	☑	☑	☑	☐	☑
Wix, File Upload	☑	☑	☑	☐	☑
Wizishop	☑	☑	☑	☐	☑
WooCommerce	☑	☑	☑	☑	☑
WordPress	☑	☑	☑	☑	☑
WP EasyCart	☑	☑	☑	☑	☑
WP eCommerce	☑	☑	☑	☑	☑
X-Cart	☑	☑	☑	☑	☑
XLS	☑	☑	☑	☑	☑
XML	☑	☑	☑	☑	☑
xt-Commerce	☑	☑	☑	☑	☑
Yahoo	☑	☑	☑	☑	☑
Zen Cart	☑	☑	☑	☑	☑

CSV, XLS, and XML are Custom Migration Source setups with Products-only included scope. Use the required CSV, XLS, or XML Product file structure; additional entity structures require explicit Custom scope and are not enabled by adding another file.

Target compatibility

This table lists supported Target Platforms.

Target Platform	Data Filter	Data Transformation	Advanced Data Mapping	Advanced Database Mapping	Data Update
3DCart	☑	☑	☑	☐	☐
Adobe Commerce	☑	☑	☑	☑	☑
AmeriCommerce	☑	☑	☑	☐	☐
Bagisto	☑	☑	☑	☑	☑
BigCommerce	☑	☑	☑	☐	☐
Cafe24	☑	☑	☑	☐	☐
CS-Cart	☑	☑	☑	☑	☑
EasyStore	☑	☑	☑	☑	☑
eShop	☑	☑	☑	☑	☑
Gambio	☑	☑	☑	☑	☑
J2Store	☑	☑	☑	☑	☑
Joomla!	☑	☑	☑	☑	☑
Jumpseller	☑	☑	☑	☐	☐
Loaded Commerce	☑	☑	☑	☑	☑
Magento	☑	☑	☑	☑	☑
OpenCart	☑	☑	☑	☑	☑
osCMax	☑	☑	☑	☑	☑
osCommerce	☑	☑	☑	☑	☑
Phoca Cart	☑	☑	☑	☑	☑
PrestaShop	☑	☑	☑	☑	☑
Shift4Shop	☑	☑	☑	☐	☐
Shopify	☑	☑	☑	☐	☐
Shopware	☑	☑	☑	☑	☑
ShopWired	☑	☑	☑	☐	☐
Square	☑	☑	☑	☐	☐
Squarespace	☑	☑	☑	☐	☐
Storeden	☑	☑	☑	☐	☐
VirtueMart	☑	☑	☑	☑	☑
VTEX	☑	☑	☑	☐	☐
Wix	☑	☑	☑	☐	☐
WooCommerce	☑	☑	☑	☑	☑
WordPress	☑	☑	☑	☑	☑
X-Cart	☑	☑	☑	☑	☑
Zen Cart	☑	☑	☑	☑	☑

Legacy names share compatibility within the same platform family

3DCart and Shift4Shop use the same underlying platform architecture, as do Maropost and Neto. The separate names improve recognition in the platform selector; they do not create a different compatibility model within each pair.

Direction examples

Check each Add-on for the selected Source → Target direction. Support for the reverse direction must be checked separately.

Migration direction	Add-on	Platform compatibility	Reason
OpenCart → WooCommerce	Advanced Database Mapping	Compatible	Both platforms support this Add-on.
Volusion → WooCommerce	Advanced Database Mapping	Compatible	Volusion supports the Source role; WooCommerce supports the Target role.
Wix using API → WooCommerce	Advanced Database Mapping	Not compatible	Wix does not support this Add-on as a Source.
Wix using File Upload → WooCommerce	Advanced Database Mapping	Not compatible	File Upload does not change the Wix Source support flag.
WooCommerce → Shopify	Data Filter, Data Transformation, Advanced Data Mapping	Compatible	All three are supported on both sides, subject to available data and fields.
WooCommerce → Shopify	Advanced Database Mapping	Not compatible	Shopify does not support this Add-on as a Target.
WooCommerce → Shopify	Data Update	Not compatible	Shopify does not support Data Update as a Target.
XML → Shopify	Advanced Database Mapping	Not compatible	XML Source support cannot compensate for unsupported Shopify Target capability.
WooCommerce → Shopware	Data Update	Compatible	Both sides support Data Update; prior-migration record and field eligibility still apply.

These examples show platform support only. Advanced Database Mapping still requires compatible database locations and Value Types. Data Update still requires selected supported fields on records previously migrated by Next-Cart whose Target counterparts exist.

Apply the compatibility check

1. Confirm the Source Platform, connection method or edition where applicable, and Target Platform in Connect Stores.
2. Check the same Add-on column in both tables. Compatible refers to platform support; the required data and fields must also be supported.
3. For Advanced Database Mapping, check schema and Value Type compatibility.
4. Configure only the controls available in the active migration.

Next Steps

Use Add-ons after platform and scope compatibility is established.