Switching to Asteris Cart — migrate safely
Migration philosophy
Asteris Cart does not import or rewrite your store data. Your products, orders and customers stay in WooCommerce. What you are moving is configuration — which cart and checkout behaviours are active, and how they are set. That makes migration lower-risk than a data migration, provided you back up and test first.
It also means honesty about scope. Asteris Cart does not build funnel pages and does not run email or SMS automation. Some features — order bumps, post-purchase upsells, abandoned-cart recovery — arrive in later versions, not v1.0. Where your current plugin does something Asteris Cart does not yet do, each guide says so plainly rather than pretending otherwise.
The safe path (every migration)
- Back up the database and files. Non-negotiable before any plugin change.
- Work on staging first if you have one. If not, choose a low-traffic window.
- Install Asteris Cart and enable Safe Mode so it does not touch the storefront yet.
- Configure the modules that replace your current plugin’s features.
- Disable Safe Mode and test checkout end to end — a real test order through your live gateway in test mode.
- Deactivate the old plugin once you have confirmed the replacement works.
- Keep the old plugin installed (deactivated) until you are certain. Safe Mode and the retained plugin are your two rollback paths.
Choose your guide
- Migrate from CartFlows →
- Migrate from FunnelKit → — includes WooFunnels, now FunnelKit-branded
- Migrate from CheckoutWC → — the closest match, both classic hooks
FAQ
Will migrating affect my existing orders? No. Orders stay in WooCommerce; Asteris Cart reads them via HPOS-compatible APIs. Back up first as standard practice.
Does Asteris Cart replace everything my plugin does? Not always. It does not build funnels or run email automation, and some features arrive in later versions. Each guide lists the gaps.
Can I roll back? Yes. Safe Mode restores vanilla WooCommerce, and keeping your previous plugin installed gives a second rollback path.