Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To migrate WooCommerce to FluentCart, install the FluentCart Migrator on the same WordPress site, run its migration stages in order, verify representative records, then reconnect payments and rebuild settings that do not transfer. FluentCart says the process copies WooCommerce data without changing the source store; still, make a fresh backup and rehearse on staging before touching a live store.
What the migration transfers—and what it does not
Use FluentCart’s official migration inventory to decide whether the built-in Migrator covers your store’s needs before you start.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
A Sixteenth-Century Anthem Book | $17.49 | Buy on Amazon |
| Data or configuration | Migration behavior |
|---|---|
| Products | Published, private, and draft products, including categories, attributes, variations, and supported bundle relationships, are included. |
| Customers | Customer identity and address information transfer. Records are deduplicated by email, and a separate stage includes registered customers who never placed an order. |
| Orders and payments | Orders include line items, taxes, shipping amounts, fees, discounts, transactions, refunds, and notes. Checkout-draft orders are excluded. |
| Subscriptions | Recurring products require WooCommerce Subscriptions. The documentation says that without it, the subscription count is zero and orders are treated as one-time payments. |
| Shipping configuration | Shipping zones, methods, and rate rules do not transfer. Historical shipping amounts transfer, but the selected shipping method name does not. |
| Gateway credentials | API credentials are not copied; reconnect payment gateways in FluentCart. |
| Tax configuration | Tax data is generated for FluentCart’s model, which is not a one-to-one copy. Review tax settings after migration. |
| Custom statuses and data | Custom statuses can be read when their registering plugin remains active. An unrecognized status may map to On Hold; an unavailable status plugin can leave orders inaccessible and logged as failed. Export important custom product or order data separately. |
| Bundle or grouped order lines | Bundle and grouped structure within individual order line items is flattened. |
| Product assets | Local files are copied into FluentCart storage; remote assets retain their original URL. |
WooCommerce blocks, shortcodes, and links are not automatically replaced. Plan to update cart, checkout, and account pages, as well as notification templates, and verify downloadable files.
Free tools Windows power users keep installed
One-click scans. No signup required.
Before you begin
Back up and rehearse
Take a fresh database backup and, if possible, rehearse the migration on staging. The Migrator is documented as read-only against WooCommerce, but a backup gives you a rollback path if the destination needs repair. FluentCart’s overview describes Developer Mode as a way to reset and rerun a staging migration; confirm its availability and behavior in your installed version before relying on it.
#1 Best Overall
Check the requirements
- WooCommerce 3.0 or later must be installed and active, with at least one product.
- FluentCart and the FluentCart Migrator addon must be installed and active on the same WordPress site as WooCommerce.
- You need WordPress administrator access.
- If you have recurring products, install and activate WooCommerce Subscriptions.
- For larger stores, FluentCart’s overview recommends a PHP memory limit of 256 MB.
The official walkthrough documents these requirements in its migration guide and migration overview.
Run the migration with the WordPress admin wizard
- Install the addon. In FluentCart settings, open Features & addon and download and activate the Migrator. Alternatively, upload its ZIP through Plugins in WordPress. Confirm WooCommerce remains active.
- Open the Migrator. Select FluentCart Migrator from the WordPress sidebar.
- Select WooCommerce and run the compatibility check. Choose the detected WooCommerce source. The check verifies that WooCommerce is active and reports its version; the documented minimum is 3.0. Resolve any failed check before proceeding.
- Review the source inventory. Compare the displayed counts for products, orders, customers, transactions, coupons, and subscriptions (when available) with WooCommerce. Check the listed payment gateways and order statuses. If a prior run is detected, inspect its state before resuming.
- Run the migration stages in order. Keep the required stages enabled for a complete migration. The wizard processes products, tax rates, coupons, orders/payments/customers, missing customers, then recount and verification. Products are migrated before orders that refer to them; recount and verification run last.
- Wait for completion and inspect logs. Failed orders are logged rather than necessarily stopping the whole run. Check the failed-order log and troubleshoot individual records before cutover.
Use WP-CLI for terminal-based or large migrations
FluentCart also documents a WP-CLI workflow, positioned for stores with thousands of orders or operators who prefer the terminal. Its migration command is:
wp fluent_cart_migrator migrate_from_woo --allThe documentation describes paged processing and resumable stages. Review the WP-CLI migration instructions for command-specific prerequisites and recovery details before running it on production.
Verify records before switching the store
Do not treat a completed run as proof that every important record is correct. Compare records in FluentCart with their WooCommerce source counterparts, including the fields that matter to your fulfillment and accounting workflows.
- Products: check categories, prices, variations, stock, and downloadable assets.
- Orders: check totals, line items, tax, shipping amount, discounts, payment status, customer data, and transaction IDs.
- Refunds: confirm representative refund records and amounts.
- Subscriptions: confirm billing interval, next renewal date, status, and collection method.
Include examples that cover a simple purchase, a variable product, shipping and tax, a coupon, a partial refund, and a subscription renewal. Also compare migrated counts against the inventory you recorded before starting.
Finish the cutover work
- Reconnect payment gateways. Re-enter credentials in FluentCart. The guide advises reconnecting the same Stripe and PayPal accounts and matching test or live mode; FluentCart selects keys according to an order’s mode.
- Recreate shipping. Add the live shipping zones, methods, and rates manually. Historical shipping charges in old orders do not identify the selected method.
- Review tax behavior. Compare FluentCart’s tax settings with your applicable requirements and test a representative checkout.
- Replace store-facing WooCommerce elements. Update blocks, shortcodes, cart, checkout, and account links, then review notification templates.
- Test downloadable products. Confirm local files are present in FluentCart storage and remote assets still resolve at their original URLs.
- Keep WooCommerce data available. Do not remove the original records immediately; retain access until the new store has been verified in practice.
Troubleshoot failed orders
Start with the Migrator’s failed-order log, which is the documented place to identify specific records and remediation. If a failed order uses a custom status, make sure the plugin that registers that status is active so WooCommerce can expose the source order to the migration. An unrecognized status may be mapped to On Hold, so inspect affected orders instead of assuming their prior state carried over unchanged. See FluentCart’s migration troubleshooting guidance for additional failure handling.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
