Migrate to Crossdeck

Your billing doesn't change; only who reads it does

Every migration comes down to one question: who is the source of truth, and when does that change? Crossdeck's answer keeps the risky part off the table. Your payment rails keep charging exactly as they do today — Stripe, Apple, and Google stay the source of money truth. The migration is about teaching Crossdeck who your existing customers are, and then pointing your app at Crossdeck for access checks. Money doesn't move; the read does.

Connect, install, import, cut over

The whole thing is four moves, and you've already learned three of the four tools:

• 1 · Connect your payment rail. The OAuth click from Connect Stripe — Crossdeck silently discovers your existing customers and subscriptions in the background.
• 2 · Install the SDK and identify. Courses 1 and 3 — so new and returning users resolve to the same person.
• 3 · Run the import script. The next lesson — you tell Crossdeck how your user IDs map to the customers it discovered.
• 4 · Verify and cut over. The lesson after — confirm everyone resolves correctly, then flip your app to read access from Crossdeck.

One honest note: Apple and Google have no import script — because, as you saw in Connect Google Play, those rails have no bulk history to import. Their subscribers fill in automatically as purchases and renewals flow through.

Every step is additive until you choose to flip

Nothing here is a one-way door. You're adding Crossdeck alongside your existing system, not ripping the old one out mid-flight. Through moves 1–3, your app keeps reading access exactly as it does today; Crossdeck is just quietly learning your customers in parallel. The only moment anything customer-facing changes is move 4, when you flip your app to read from Crossdeck — and because you verified first, you flip it knowing it's right.

A plan, not a leap

That's the shape of the whole thing: connect what you already have, teach Crossdeck your customers, prove it matches, then read from it. The next two lessons cover the two moves you haven't done yet — importing your subscribers, and verifying before you cut over.