Move your billing without a migration project.
Export from the platform you use now, import with a dry run that shows every row before anything is written, run one billing cycle beside the old system, then switch charging on at a renewal. Pick your platform for the exact steps, including what happens to the saved cards.
Chargebee exports everything a move needs as CSV, and for most gateways the saved cards already live in your own account. The whole move is an export, a dry run and one parallel billing cycle.
Leaving Stripe Billing does not mean leaving Stripe. yRecurring runs on your existing Stripe account, so the cards, the customers and the payouts stay exactly where they are; only the subscriptions move.
Recurly has the most complete export in the category, thirty-odd CSVs, and a documented way to hand your saved cards to the next system. The one thing to do early is the card export request.
Paddle is the merchant of record, so the move has one extra step the others do not: your customers' cards are in Paddle's vault, and Paddle transfers them to your new payment provider on request. Start that first; the data itself is a report away.
Lemon Squeezy exports orders and subscriptions, and rebuilding a store's products takes minutes. What it does not offer is a documented way to move saved cards to another provider, so the plan below treats the first renewal as a card update.
Maxio's exports arrive by email and in-app notification when they are ready, and it stores no card data of its own, so the cards are already in your gateway. The move is the CSVs, a dry run and one parallel cycle.
Lago stores only provider ids for payment methods, so the cards are already in your Stripe, Adyen or GoCardless account. Invoices export from the app; the rest comes from the API or, self hosted, straight from your database.