Migrating from SmartWallet

There's no technical mechanism to transfer Apple Wallet passes between Pass Type IDs — the cert identity is baked into the installed pass. The migration pattern that works is issue new, let old decay:

1. Turn on the public enrollment form for your program, then share its link (/enroll/{tenant-slug}/{program-slug}) with your existing cardholders — by email, SMS, or in store. See Enrolling members.
2. Each cardholder fills in the form once and receives an email with a link to add the new Stokk-issued card to their phone. (For a handful of members you can also enroll them one at a time at Enroll a member.)
3. The old vendor's cards keep working on the devices they're already on, but get no further updates.
4. After 30 days of clean operation, cancel the old vendor.

Why this is the pattern

Apple Pass Type IDs and signing certs are 1:1 bound. Two different vendors signing under different Pass Type IDs produce two different passes from the device's perspective. This isn't a Stokk constraint — it's how Apple Wallet works. Any wallet vendor you migrate away from will face the same when you leave them. Owning your own Pass Type ID under your own Apple Developer account is the long-term answer; until then, Stokk hosts the identity for you.