The biggest fear when switching from WooCommerce to YS CART is not being able to migrate historical data cleanly. This import bridge fully transfers customers, products, and orders—including digital download permissions—into YS CART, and it's designed to be "safe to run a second time": importing again won't create duplicate records.

Elf-style guidance, six steps to completion

The import wizard guides you through the upload and import process step-by-step in the correct order: "Environment Check → SQL Backup → Customers → Products → Orders → Complete." It also provides manual mode for managing job records, backups, and restores. After exporting the ZIP package from the source site, simply upload it. You can import multiple different source sites in sequence—orders are identified by "Source Site + Source Order Number" and will not overwrite each other.

Even large sites can be moved: REST continues to run in batches

Import resumable REST batch jobs: Continue from breakpoints after interruption, no fear of timeouts. Order dates normalized to UTC, country and postal code automatically cleaned, historical custom statuses covered (even if the original plugin is disabled). Digital download entitlements will be tied back to the correct customer and order; used download counts will not be reset.

Features

Six-step Elf Import

Environment check → SQL backup → Customer → Product → Order → Complete. The order is correct.

Rest Batch

Batch processing of large amounts of data, with interrupted and resumed runs, eliminating concerns about host timeouts.

Re-collection idempotence

Existing data will not be duplicated; re-importing will refresh the source metadata.

Digital Download Rights Migration

Downloadable files, number of downloads, and expiration dates are correctly linked to the customer and order.

Multi-source site support

Orders are identified by "origin station + origin order number," and multiple station consolidations do not overwrite each other.

Data normalization

Order time to UTC, country/zip code auto-cleaning, including custom statuses.

Screenshots

Changelog (Latest)

This version accumulates the fixes from 0.7.14, 0.7.15, and 0.7.16 (the first two versions were not released separately).

Fixed

0.7.16 — Switched to atomic source imports from Core

Products, attributes, downloadable products, and persistent source identitiesSubmit togetherThis instruction is provided by Core 2.61.5; old Cores without a catalog transaction owner maintain their original import path.
First read the product identity of Core, then look at the retained legacy mapping; legacy upsert and variant download writers still each hold map column identities.
Stop the entire batch when the original submission results cannot be verified.At the same time, stop the background automatic polling loop, keeping the current cursor and the expiring job lock for reconciliation. Uncertain batches will not be treated as successful to continue running.

0.7.15 — Batch count no longer resets to zero

When entering the variant stage, retain the total counts of processed/success/error from the previous batch of items; only the variant cursor is reset to zero, and completed item rows will no longer disappear from the job count.

0.7.14 — Rejected product updates are considered errors

YS CART treats product update rejection as import error: existing transactions have altered attributes, mappings, and digital downloadsBeforeRollback, that column is no longer counted as a success.

Changed

The shipping kit boundaries are now declared by `export-ignore` in `.gitattributes`, and no longer exist only in the packaging scripts. This version is file-for-file identical to v0.7.13 (63 files), with only code changes.

FAQ

Do both sides need to have the add-on installed simultaneously?

Source WooCommerce site export ZIP package, target YS CART site to install this plugin and upload for import; also supports direct migration within the same site (when both systems are on the same site).

What if the transfer is interrupted and the connection is lost?

The job is a continuously runnable batch design, returning to the wizard will resume from the breakpoint; each job has a record that can be checked.

Will running it a second time create a duplicate order?

No. Orders are identified by the source site + source order number. Remittances only update existing data (idempotent).

Subscriptions and variable products?

Product includes variations and corresponding specifications; special types (e.g., subscriptions) will be converted according to the corresponding table, and pre-import environment checks will list any important notes.