How to migrate from CartFlows to Asteris Cart
Before you start
- Back up the database and files. Always.
- Use a staging site if you have one. If not, pick a low-traffic window.
- Keep CartFlows installed (you will deactivate, not delete, until the switch is confirmed).
- Read the gaps below before committing — some CartFlows features have no v1.0 equivalent.
What does not have a v1.0 equivalent
Honest first, because it decides whether you should migrate at all:
- Funnel canvas / funnel pages — Asteris Cart does not build these. If your store runs CartFlows funnels, keep CartFlows for that part, or wait for a later version.
- Order bumps — ship in Asteris Cart v1.2, not v1.0.
- Post-purchase upsells / downsells — v1.2.
- A/B testing — v1.4.
If your use of CartFlows is mostly the checkout itself, migration makes sense now. If it is the funnel builder, it does not yet.
Module-by-module mapping
| CartFlows feature | In Asteris Cart |
|---|---|
| Optimised checkout | Multi-Step Checkout (Pro) + Field Editor |
| Cart / side cart | Side Cart |
| Express payments | Express Checkout + per-zone kill switch |
| Countdown / urgency | Urgency Timer (real server-side expiry) |
| Trust elements | Trust Badges |
| Funnel pages | no v1.0 equivalent — keep CartFlows or wait |
| Order bumps / upsells | v1.2 — not yet |
Step by step
- Back up the database and files.
- Audit CartFlows. Write down the features you actually use and tick them against the mapping table.
- Install Asteris Cart and enable Safe Mode so it does not touch the storefront yet.
- Configure the replacing modules — checkout, side cart, express, urgency, trust badges.
- Disable Safe Mode. Run a full test order on staging or in a low-traffic window, through your live gateway in test mode. Confirm the order completes and any pixel events fire.
- Deactivate CartFlows. Do not delete it yet.
- Verify over a day or two. If anything misbehaves, re-enable Safe Mode (vanilla WooCommerce returns) or reactivate CartFlows. Both are valid rollbacks.
See how Safe Mode works → · Compare Asteris Cart and CartFlows →
In-progress orders
Orders remain in WooCommerce, so deactivating CartFlows does not move or rewrite them. Asteris Cart reads orders through HPOS-compatible APIs. If CartFlows stored custom order meta you depend on for reporting, note those keys before deactivating, since that data belongs to CartFlows rather than WooCommerce core.
FAQ
Does Asteris Cart replace CartFlows funnels? No. It does not build funnel pages. Keep CartFlows for funnels, or wait for a later version.
What about order bumps and upsells? Those arrive in v1.2. Do not switch for them yet.
Will my orders be affected? No. Orders stay in WooCommerce; Asteris Cart reads them via HPOS-compatible APIs.
How do I roll back? Enable Safe Mode for vanilla WooCommerce, or reactivate CartFlows. Keep CartFlows installed until you are certain.
Sources
- Asteris Cart roadmap (order bumps v1.2, A/B v1.4): file 04
- CartFlows feature set: file 05 [attach docs cite at publish]