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. Export your existing cardholder list from the old vendor as CSV.
  2. Use Bulk import to re-issue every cardholder under Stokk.
  3. Each cardholder receives an email with a link to add the new Stokk-issued card to their phone.
  4. The old vendor's cards keep working on the devices they're already on, but get no further updates.
  5. After 30 days of clean operation, cancel the old vendor.
Expected install rate

Some percentage of cardholders won't add the new pass — that's expected. Watch the active count in Loyalty over the migration window. For non-installers, reach out via your tenant's preferred channel and resend the link.

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.