Moving off Recharge? Nobody signs up again.
Appstle, Bold, Loop, Skio, WooCommerce and custom builds too. A Subi migration specialist runs the import, so billing dates, plans, and discounts come across as they already are.
Happy brands who've migrated to Subi
What actually happens when you switch
Our team runs your migration and stays on it after cutover. Here is each step, and what your subscribers see while it runs.
A specialist maps your current setup
Before anything is touched, a migration specialist goes through the plans, billing intervals, discounts, and edge cases on your current app, then tells you plainly what moves across as it is and what needs a decision from you first.
You export, we check the data
We walk you through exporting your subscription data from your current provider, then check every customer, order, schedule, and discount against what Subi needs before a single contract is created.
We handle payment methods before anything imports
A payment method your old platform cannot hand over is one of the common ways a migration breaks, so we re-vault Stripe, Braintree, and PayPal tokens before any contract is created. Authorize.net cards cannot be moved across, and your specialist plans for those with you on the call. A missing or malformed column fails the file check before anything is imported, so it is fixed with your specialist rather than found afterwards.
We import, then stay on it
Contracts are recreated with their existing billing dates, products, and discounts, and built in a staging flow before they go live. Anything that does not import cleanly comes back to your specialist, not to you.
Subi imports from Recharge, Appstle, Bold, and the rest
Whichever of these you are on today, and custom or legacy setups too. Your specialist confirms your source on the first call.
Recharge
The source we see most often. Subi has a dedicated Recharge importer, so plans, billing dates, and discounts map across directly instead of being rebuilt by hand.
Appstle
Appstle subscriptions come across as an export. Your specialist maps the plan, interval, and discount columns onto Subi contracts before anything is created.
Bold
Bold and other long-running setups migrate the same way: export, audit, map, import, with each subscriber's existing billing schedule preserved.
Loop, Skio, WooCommerce, Stripe, and custom builds
If your subscriptions can be exported, they can be mapped. Bring the export to the first call and your specialist will tell you what moves and what does not.
What changes, and what does not
The honest version: what your subscribers experience, and what only your team notices.
Nobody re-subscribes
Your customers are not asked to sign up again. Their subscription continues on the schedule they already have.
Billing dates stay put
Existing billing dates come across exactly, so the move does not pull a charge forward or push one back.
A person owns your migration
Every Subi migration is run by a specialist on our team rather than handed to you as a self-serve importer. You have one name to ask.
One app instead of four
Subscriptions, memberships, and bundles all run in Subi, with loyalty programs on the Subi plan and above, so the switch is also the chance to drop the stack around your old app.
Migration FAQ
The questions merchants ask us before they switch, answered the way we answer them on the call.
Can I migrate from Recharge, Appstle, or Bold?
Yes. Subi imports from Recharge, Appstle, Bold, Loop, Skio, WooCommerce, and Stripe, as well as custom and legacy setups. Your specialist confirms your source during the first call.
Will my subscribers be charged during the migration?
No. The import moves your data and schedules without triggering any charges, and existing billing dates are preserved exactly.
Do my customers have to re-enter their card?
Where the source platform can hand over the payment method, it comes across with the contract and renewals continue untouched. Where it cannot, the contract is still created active and only those customers receive a single request to add a card, so nobody is dropped silently.
What happens to a subscriber whose last payment failed?
We try to re-vault their card before the import, using a Stripe, Braintree, or PayPal token from your old platform. If that does not work, the contract is flagged as an error rather than created, and your specialist works through those with you by hand before you go live.
How long does the whole thing take?
It depends on data volume and complexity. Your specialist gives you a timeline before you commit to anything.
Is there downtime for my store or my customers?
Your store never goes down. Contracts are built in a staging flow and only go live once they check out, and where one does not, it comes back to your specialist to work through with you before you go live.