Migration project

A migration project is the shared workspace for one migration between one source account and one destination account. Both owners see the same project. Each runs the steps for their own account.

Two accounts, two owners

The source owner controls the source account and its keys. The destination owner controls the destination account and its keys. Neither owner can write to the other's account. One person can hold both roles, for example when a founder moves to a new legal entity.

Who does what

• Source owner: the read-only key, the scan, the decisions, the customer list upload in Stripe, the cancellation key, and the final confirmation.
• Destination owner: the write key, accepting the copy request in Stripe, the catalog, and the schedules.
• Either owner: payment, verification of the copied customers, and verification of the schedules.

Payment

Planning is free: the scan, the decisions, and sandbox migrations. The one-time fee is charged before the first write to the destination account.

Gates

Each stage waits behind a check:

• The read-only key is connected before the scan.
• Every flagged subscription is decided before the customer list exists.
• The project is paid before the first destination write.
• Every copied customer is verified before any schedule is created.
• Every schedule is verified before the cancellation key is used.
• The source owner confirms the cancel step by hand.

Data handling

Restricted keys are encrypted before they are stored, scoped to one project, and deleted 7 days after the project completes, or after 30 days without activity. Stripe IDs are shown after payment. Customer emails are masked for the destination owner until the migration completes.

Outside the project

Your application, database, entitlements, webhooks, and customer messages stay with your team. SubPorter moves Stripe Billing objects and stops there.