Migrate subscriptions from Stripe
Treat customer data, payment credentials and billing state as separate migration work.
Inventory before you export
List customers, subscriptions, prices, tax information, trial ends, discounts, usage records, billing anchors, unpaid invoices and entitlements. Check whether your destination supports the same billing model.
Use supported payment-data transfer
A CSV does not contain transferable card credentials. Work with the processors’ supported secure migration process and confirm destination eligibility. Do not export sensitive payment credentials yourself.
Reconcile and protect continuity
Test renewals, proration, cancellation, refunds, webhooks and access controls. Avoid charging both systems for the same period. Keep invoice history and a rollback/reconciliation plan appropriate to your contracts.
A migration has three separate workstreams
| Object | Who coordinates it | What to confirm |
|---|---|---|
| Customer and invoice records | Your team, using permitted exports | IDs, tax evidence, credit balances and record retention |
| Stored card details | The source and destination processors | Supported secure transfer, eligible records and token mapping |
| Subscription schedules | Your billing integration and destination | Next billing date, prices, trials, cancellation and proration |
Treat the first successful destination renewal as the cutover test. Match old and new IDs, keep entitlements active, and reconcile the last source charge against the first destination charge. A supported payment-data transfer does not recreate your billing logic.
Stripe documents processor-coordinated transfers and subscription remapping. Ask the destination to confirm acceptance before cancelling the existing billing relationship.
Useful next steps
Build the export plan → · Stripe profile → · Paddle profile →
Read the product-specific evidence
Provider-specific conditions and primary sources: