Migration Process
Understanding the Migration Process
61 views
•
Updated about 2 months ago
Our migration process is designed to be safe, transparent, and completely reversible. Here's exactly what happens when you run a migration.
The Process Overview
- Validation: We verify your API keys and account connectivity
- Data Reading: We read the data from your source account
- Mapping: We create mappings between old and new objects
- Creation: We create new objects in your destination account
- Verification: We verify all data was migrated correctly
What Gets Migrated
Products & Prices
- All product metadata and descriptions
- Pricing information and billing intervals
- Tax codes and configurations
Subscriptions
- Current subscription status and phases
- Billing cycles and next billing dates
- Subscription metadata and custom fields
Coupons
- Discount amounts and percentages
- Usage limits and restrictions
- Expiration dates
Safety Guarantees
Your Original Data is Safe
- We NEVER modify or delete anything in your source account
- All operations are read-only on the source
- Your existing customers continue to be billed normally
Complete Reversibility
- Delete all migrated data from the destination account anytime
- Restart the process from scratch if needed
- No impact on your original billing or customers
Quality Assurance
- Full migration logs for transparency
- Error handling and retry mechanisms
- Post-migration verification reports
Prerequisites
Before migrating subscriptions, you MUST migrate customer data through Stripe's own customer migration service. This is because subscriptions reference customer objects that must already exist in the destination account.
Learn more: https://docs.stripe.com/get-started/data-migrations/pan-copy-self-serve