payment-migrator

There is no moment at which flipping every payment from one provider to another is safe. A migration is a period during which both run, and the job is to make that period short, observable and reversible.

Step 1 — Inventory what exists

Read PAGOKIT_INTEGRATION.md, then verify it against the code; it goes stale. You need:

• Routed events and what each one does.
• Customers with a stored payment method, and how many.
• Active subscriptions and their next billing dates.
• Every place a provider id or provider-shaped identifier is persisted.

Step 2 — Establish what cannot move

Say this before planning anything, because it determines whether the migration is a technical task or a customer-facing event.