Live demo · sample data

A finished two-party migration. Explore the pipeline and the asset tables — actions are disabled. Try the source / destination toggle to see customer masking.

Start your migration
Migration complete

Acme → Globex billing handoff

You: source ownerproj_ac1e59b7

Phase 3 of 3100%

Selected migration complete

47 subscriptions scheduled in the destination and set to cancel at period end in the source. 1 manual-review subscription was kept outside this packet and keeps billing in the source.

Pipeline3/3 phases complete
  1. Plan
    Done
  2. Copy
    Done
  3. Migrate
    Done

Completed migration step

Customer copy verified

Stripe customer data has been copied and mapped for the selected migration packet. Keep the CSV and map below as recovery evidence.

CSV customers46
CSV subscriptions47
Mapped46 / 46
Manual included1
Manual outside1
Download CSVDownload mapStripe docs

What's being migrated

47 subscriptions scheduled in the destination so far.

CustomerMigrationManual reviewStatusRenewsItems
ava@northwind.ioPending plan—activeJul 5, 20261
liam@craftbase.coManual review

Why this needs review

Discount presentMissing payment method
Source decisionIncluded

This demo is read-only. Create a migration to save manual-review decisions.

activeJul 9, 20262
omar@stackline.appPending plan—activeJul 18, 20263
jonas@brewmetrics.comPending plan—activeJul 11, 20262
maya@loomworks.ioManual review

Why this needs review

Existing schedule
Source decisionExcluded

This demo is read-only. Create a migration to save manual-review decisions.

active · cancelingJul 21, 20261
ravi@tidalhq.comPending plan—activeJul 14, 20261
tom@brightledger.comPending plan—activeJul 25, 20264
sara@nimbus.coPending plan—activeJul 8, 20261
leo@driftbase.devPending plan—activeJul 16, 20262
9 rows

Migration pipeline

Four phases, in order. Each party runs the actions it owns; the other side can watch every state change.

Plan
Free · read-only
  • 1. Source inventoryYou · source owner

    Read the source account: products, prices, meters, and every active subscription.

    50 subscriptions · 48 customers

  • 2. Migration planEither party

    Sort the subscriptions into auto-migrate and manual-review.

    46 auto · 2 manual

  • 3. Catalog dry runEither party

    Preview the products and prices to recreate in the destination. Nothing is written.

    3 products · 7 prices · 1 meters

Copy
Live writes unlocked
  • 4. Copy customers in StripeYou · source ownerLive write

    Generate the partial-copy CSV, then use Stripe’s Dashboard flow to share customers with the destination account.

    46 customers · 46 subscriptions

  • 5. Apply catalogdestination ownerLive write

    Create the products and prices in the destination account.

    3 products · 7 prices · 1 meters

  • 6. Verify customersEither party

    Confirm Stripe copied the customers and payment methods into the destination.

  • 7. Repair payment defaultsdestination ownerLive write

    Set the default payment method on each copied destination customer.

  • 8. Tax previewEither party

    Preview destination tax behavior before any renewal is scheduled.

Migrate
Live writes unlocked
  • 9. Schedule dry runEither party

    Build the subscription schedules, each aligned to its real renewal date.

  • 10. Create schedulesdestination ownerLive write

    Write the subscription schedules into the destination, in safe chunks.

    47 scheduled

  • 11. Verify schedulesEither party

    Confirm every destination schedule matches its source renewal before cutover.

    47 scheduled

  • 12. Source cancel planYou · source owner

    Preview cancel-at-period-end for the source subscriptions. Nothing is written.

  • 13. Cancel sourceYou · source ownerIrreversible

    Set the source subscriptions to cancel at period end. This is irreversible.

Deliverables

Every dry run and live write is retained as a downloadable record for both parties.

Final migration packet
The signed-off record of everything that moved. Markdown.
Source inventoryJSON
Product count: 8Price count: 12Billing meter count: 1Subscription count: 50
Migration planJSON
Total subscriptions: 50Auto candidate count: 46Manual review count: 2Auto customer count: 45
Destination catalog planJSON
Products: 3Prices: 7Meters: 1
Stripe partial customer-copy CSVCSV
Customers: 46Subscriptions: 47
Product mapJSON
Total: 8Mapped: 8
Price mapJSON
Total: 12Mapped: 12
Destination customer verificationJSON
Checked: 46Mapped: 46Unmapped: 0Same id customer: 0
Customer map CSVCSV
Total: 46Mapped: 46Unmapped: 0Different id: 46
Customer mapJSON
Total: 46Mapped: 46Unmapped: 0Different id: 46
Destination payment-default repairJSON
Set default count: 5Skip count: 0
Destination tax previewJSON
Customers: 46Success: 46Failed: 0
Subscription schedule planJSON
Schedules: 47Blocked: 0Created: 47Reused: 0
Billing migration toolkit CSV exportCSV
Rows: 47
Subscription schedule mapJSON
Rows: 47
Subscription schedule verificationJSON
Checked: 47Valid: 47Issues: 0
Source cancellation planJSON
Targets: 47Safe updates: 47Updated: 0Blocking issues: 0

Accounts & keys

Source owner
seller@acme.com
active
Destination owner
buyer@globex.com
active
Source preview key

Restricted read key for inventory and planning.

Restricted key · verified
Account
acct_1AcmeSource0000
Fingerprint
THHzT5Bl28w9aVPx
Create another source preview key in Stripe

Replacing a key? Check the Stripe URL shows the account you expect, scroll to the footer Create key button, then copy the value right away.

Destination migration key

Restricted key with the destination write permissions.

Restricted key · verified
Account
acct_1GlobexDest0000
Fingerprint
Dn8s2Kd91mWqe7Zx

Only the account owner can upload this key.

Final source cancellation key

Narrow subscriptions-write key for cutover only.

Restricted key · verified
Account
acct_1AcmeSource0000
Fingerprint
THHzT5Bl28w9aVPx
Create another source cancellation key in Stripe

Replacing a key? Check the Stripe URL shows the account you expect, scroll to the footer Create key button, then copy the value right away.

Key hygiene. SubPorter encrypted key values are deleted after the completed-project retention window. Stripe restricted keys remain in Stripe until you delete or revoke them there.

After saving the final packet, delete temporary SubPorter restricted keys from the Stripe Dashboard in the source and destination accounts.

Audit log

Approvals, key uploads, admin views, and every migration action are recorded.

  • inventory.completed

    Source inventory completed for 50 subscriptions.

    seller@acme.com

  • plan.completed

    Migration plan created with 46 auto candidates and 2 manual-review rows.

    seller@acme.com

  • catalog.planned

    Destination catalog dry run created for 3 products and 7 prices.

    seller@acme.com

  • customers.copy_csv_created

    Stripe customer-copy CSV generated for 46 customers.

    seller@acme.com