YS CART WooCommerce Import
Woo customers/products/orders/download permissions can be fully migrated to YS CART, with continued operation, re-exporting, etc.
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)
Fix
remove vendored YS Plugin Hub Client Invalid WooCommerce HPOS compatibility declaration inside.
Problem
This declaration calls `FeaturesUtil::declare_compatibility( 'custom_order_tables', __FILE__ )` with its own vendor file path,
but `vendor/yangsheep/ys-plugin-hub-client/ys-plugin-plugin-hub-client.php` is not a registered plugin main file,
WooCommerce `FeaturesController` therefore inEach request Record one:
```
FeaturesController: Invalid plugin file '.../vendor/yangsheep/ys-plugin-hub-client/ys-plugin-hub-client.php' for feature 'custom_order_tables'.
```
Noise washes away the `plugin-woocommerce` log channel, buries the real error messages, and causes extra disk I/O.
Scope of impact
Does not affect the transaction, order, or payment process.
Amend the law
The declaration is invalid because it points to a non-registered file.Never took effectremove zero-change behavior - no plugins will become "incompatible with HPOS" because of this;
HPOS compatibility should be declared by each plugin itself.
- vendor loader diff: `+0/-13` (this declaration block only; activation hook/autoloader/schema fallback/`ys_hub_client_loaded` all retained)
- bundled Hub Client versionDeliberately maintain `2.0.2`Only remove dead code, without introducing subsequent version's center naming and menu normalization behaviors
packaging
- `ys-cart-woocommerce-import-v0.7.11.zip` (90 entries)
- SHA-256: `929FA04AA6AF2A8292AC070B00CC32B90DB89B89AFAB05EF8269ADB252DF675E`
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.
