Moving 1,100 Paying Customers Between Stripe Accounts in a 3-Hour Window

Short summary

A payments engineering team moved 1,100 paying customers from an Australian Stripe account to a new US account in 3 hours with zero customer impact, using Stripe's PAN tool plus custom Go scripts for credits, coupons, and metadata. The core challenges were coordinating across payment states (open invoices, failed payments), maintaining usage limits for coupons split across multiple fields, and routing webhooks to the correct regional cluster after the migration. Their approach—dry-run-first scripts, sequenced by product risk, and a cloud function as a unified webhook router—generalizes to any multi-account payment infrastructure.

• •Migrated 1,100 customers between Stripe accounts in 3 hours with zero downtime or double-charging
• •Key engineering challenges: syncing credits, reconciling split coupon/promo-code logic, managing in-flight invoices during settlement
• •Reusable pattern: cloud function webhook router for multi-account architecture, dry-run scripts for safety

Generated with AI, which can make mistakes.