Migrating Stripe Customers to Evolve — gotchas to watch for?
Posted by rachel_eng — March 28, 2026 — 22 replies
About to start a Stripe → Evolve migration with ~400k Customer records and active subscriptions. Field mapping I think I have, but I'm worried about the things we won't notice until it's too late. What are the surprises?
Three big ones from our migration of ~250k customers last year:
- Network tokens don't transfer. Stripe's network tokens are scoped to Stripe's BIN sponsorship; Evolve's are scoped to ours. You'll re-tokenize on first charge, which works fine but means the first attempt has slightly higher friction. Run the parallel-charge pattern for 2 billing cycles and you'll be fine.
- Mandate text matters. If your Stripe Customer object has a stored mandate, transfer it as part of the import — Evolve respects PSD2 mandate continuity if the mandate text and timestamp are preserved. We missed this on the first batch and got a wave of fresh SCA challenges.
- Payment-method metadata. Stripe stores some PM metadata (last_used, fingerprint) that Evolve regenerates on its side. If you have business logic depending on those exact values, plan for them to differ. Fingerprints in particular use a different hashing approach.
The migrate-from-stripe tutorial in the Evolve Tutorials space covers the parallel-run pattern in detail. Worth a read before you cut over.
+1 to network tokens. We saw a 2.1% bump in soft declines for the first 3 days post-migration, which then settled down once renewal mandates kicked in.