A sample migration

Acme has 50 Stripe subscriptions. 15 are active: 10 move now, 5 wait for a later pass. Pick a moment. Every state is derived the same way as a real project. Try the decisions in stage 3; other writes are disabled. Some steps are left out here; your own project shows every step.

Start your own migration

Acme → Globex migration

You: sole operator · proj_ac1e59b7 · Stage 1 of 6 · Connect

Your move · Connect the source account
Sample data

Stage 1 of 6Youup next

Connect the accounts

Two restricted keys: one that can only read the source account, one that can write to the destination account.

The source account has to be connected read-only before anything can be scanned.

Source account, read-only key. Lets SubPorter read products, prices, meters, customers, saved payment methods, and subscriptions. It cannot create, change, or cancel anything.

Destination account, write key. Lets SubPorter create products, prices, meters, and subscription schedules there. Needed from stage 5, once the project is paid.

Both keys. Encrypted before they are stored, scoped to this project, and deleted when the migration completes.

Connections

  • Source accountnot connected
  • Destination accountnot connected

Connect the source account, read-only

A restricted key that can only read. SubPorter cannot change anything in the source with it.

  1. 1
    This one-click key creation link is provided in your migration project. It opens Stripe’s form with the exact permissions filled in.

    Before clicking Create key, check the Stripe URL shows the account you expect and that live mode is selected. Use the Create key button in the footer of Stripe’s form, then copy the rk_live_… value right away. Stripe shows it only once.

  2. 2

    Encrypted before it is stored, scoped to this migration, deleted when the migration completes.