Stripe Migration FAQ: 33 Answers for SaaS Sellers

You create a transfer project, connect both Stripe accounts using restricted API keys, use Stripe's Customer Data Copy for eligible customer and payment-method data, upload the mapping CSV, and then execute the migration. MoveMRR recreates supported subscriptions in the new account and applies the source-deactivation strategy you selected.

No. MoveMRR never touches raw card data. Payment methods are transferred through Stripe's official Customer Data Copy process, which is handled entirely by Stripe. MoveMRR only manages the subscription and customer metadata.

A source subscription is deactivated only after its destination counterpart is confirmed. That ordering, together with rehearsal and reconciliation, reduces double-billing and continuity risk; exceptions still need review before and after cutover.

MoveMRR uses the source billing-cycle data to reproduce the expected renewal schedule for supported configurations. The dry run flags cases that require mapping or manual review, and the first destination renewals should be reconciled after cutover.

Use Sandbox Seeding. It scans your live Stripe account with a read-only key and recreates its catalog in your sandbox — products, prices, coupons, promotion codes, tax rates, and the subscriptions on the customers you copied in with Stripe's copy tool. Customers without a payment method get a Stripe test card. The result is a sandbox that behaves like your live account, so your test migration actually predicts the real one. The full walkthrough is at movemrr.com/knowledge/sandbox-seeding-guide/.

It only reads. You provide a read-only live key, MoveMRR uses it once to scan your live account, and the key is never stored — not in the database, not in logs. All writes go to your Stripe sandbox through its own sandbox key. Re-seeding later means pasting the live key again.

MoveMRR is designed to avoid service downtime: it creates destination subscriptions with preserved billing anchors and no proration, then deactivates a source subscription only after the destination subscription is confirmed. Eligible payment data can be copied through Stripe Customer Data Copy. An issuer or unsupported payment method can still require customer authentication later, so no migration tool can promise that customer action will never be required.

Usually not for eligible customer and payment-method data copied by Stripe. MoveMRR recreates subscriptions without charging customers during the migration, and you decide how to communicate the ownership change. Some payment methods are not copyable, and a card issuer can still require authentication on a later off-session payment. Link wallet authorizations are scoped to a business and may need to be confirmed again.

MoveMRR maps supported billing anchors, products, prices, currency, interval, tiers, and metadata and disables migration-time proration. Because Stripe configurations and subscription states vary, the dry run and reconciliation must confirm the resulting dates and amounts before launch.

Canceled, unpaid, and incomplete subscriptions are not transferred. Active and trialing subscriptions migrate by default, and past-due subscriptions can be included as an explicit per-run opt-in. Invoice history and payment records stay in the source account, and account-level settings such as dunning must be configured in the destination. Supported products, prices, subscription metadata, and coupons can be recreated; review readiness results for unsupported or manually mapped configurations before launch.

Yes, as an opt-in per project. When enabled, the live run recreates the source account's enabled webhook endpoints on the destination — URL, subscribed events, API version, description, and metadata. If the destination already has an endpoint at the same URL, MoveMRR widens that endpoint's event list instead of creating a duplicate, so it keeps its existing signing secret. Endpoints the seller had disabled are deliberately not re-enabled. The one thing Stripe does not allow anyone to copy is the signing secret: every newly created endpoint gets a fresh whsec_, and MoveMRR lists exactly which endpoints need that secret re-deployed to your consumers. A readiness check before the run and a coverage diff after it show which endpoints are covered, partial, or missing.

Yes — as an explicit opt-in for each migration run, off by default. When enabled, past-due subscriptions are recreated in the destination account with billing anchored to the next regular cycle, so there is no immediate charge. To stop the old account from still collecting on a customer who has already moved, the open overdue invoice in the source account is voided — the outstanding amount is intentionally written off. If that outstanding payment matters to your deal, collect or resolve it before migrating. Canceled, unpaid, and incomplete subscriptions are never migrated.

Only customer and payment-method data that Stripe marks eligible for the specific source and destination accounts can be copied. Wallet or business-scoped authorizations may require a customer to confirm or replace a payment method. Confirm the current supported-method list with Stripe and include every non-copyable default in the remediation queue.

MoveMRR maps supported price currencies, unit amounts, and currency options into the destination catalog. Review multi-currency and tiered prices in the dry run, because account capabilities, tax settings, or unsupported price configurations can require manual mapping.

MoveMRR configures supported destination subscriptions with the mapped future renewal date and no migration-time proration. Existing source invoices and later off-session destination charges are separate events, so reconcile both accounts and configure destination dunning before cutover.

MoveMRR does not control Stripe's risk assessment. The destination account is evaluated on its own verification, business model, transaction history, and risk profile, and Stripe can independently apply reviews, reserves, or payout holds. Confirm account readiness with Stripe before scheduling the cutover.

MoveMRR does not notify customers. Whether notice is required depends on the transaction, contracts, privacy terms, payment methods, and applicable law. Ask legal and payment advisers, and prepare targeted communication for customers who must authenticate or update a payment method.

MoveMRR provides a complete audit log with timestamps for every action: subscription created, old subscription deactivated, products and prices created, coupons mapped. You get customer-by-customer tracking showing old subscription ID to new subscription ID, status, and billing anchor.

The migration is idempotent — if it fails partway, you can safely re-run without creating duplicates. Old subscriptions are only deactivated after new ones are confirmed active. A full rollback would require another migration in reverse, but the design minimizes this need.

Yes, if you enable product migration. MoveMRR auto-creates products and prices identically in the destination account — including name, description, images, metadata, currency, amount, recurring interval, tiered pricing, and tax behavior. Mappings are stored so subscriptions reference the correct new price IDs.

Potentially. The key dependency is whether Stripe supports and approves Customer Data Copy between the specific source and destination accounts and whether the relevant payment methods are eligible. Verify the country pair and account configuration with Stripe before starting.

The legal account type does not by itself determine the MoveMRR workflow, but the two accounts still need the required API permissions and Stripe must support the planned Customer Data Copy. Country, business structure, ownership, and payment-method eligibility can affect what Stripe approves, so verify the exact account pair before launch.

MoveMRR provides a CSV export with old-to-new subscription ID mappings for every migrated subscription. Use this to update your database or third-party integrations (WordPress plugins, membership platforms, etc.). The export includes old subscription ID, new subscription ID, customer IDs, and status — everything you need for a simple database query or bulk update.

MoveMRR follows a security-first approach. Only restricted Stripe API keys are used, scoped strictly to user-selected actions. No long-lived secrets are stored beyond the project scope, and every action is logged for full auditability.

You define exactly what actions MoveMRR is allowed to perform. Based on your choices, MoveMRR guides you to create restricted API keys with only the necessary permissions for your specific migration needs.

Yes. MoveMRR is designed to be idempotent, meaning it can be safely re-run without creating duplicates or corrupting data. If something goes wrong, you can retry the migration.

MoveMRR uses one-time pricing based on the active subscriptions and estimated monthly recurring revenue being migrated. Current starting prices are Minimum from 150€, Advanced from 350€, Done-For-You from 3.150€. Enter both values in the homepage pricing calculator; all prices are in EUR and exclude VAT.

MoveMRR is designed as a one-time-use tool for SaaS exits. You pay once for your migration project, not a recurring subscription.

Yes. Sandbox projects are free and unlimited: they use Stripe test keys, consume no license, need no liability waiver, and run the same migration engine as a paid live project — with no cap on runs or subscription count. Once your customers are in the sandbox — you copy them there with Stripe's own copy tool — Sandbox Seeding adds your live catalog, discounts and tax rates and recreates your active, trialing, and past-due subscriptions on top of them, so the rehearsal reflects your real billing. Only the live migration is paid; the sandbox costs nothing. A sandbox project cannot be converted into the live one, so create the live project separately once you are ready.

Minimum is self-service, Advanced includes guided sessions and priority email support, and Done-For-You includes hands-on migration and cutover support. For general inquiries, contact jovanovic@thecodecave.de.

MoveMRR is a one-time-use SaaS tool for controlled customer, active-subscription, and catalog migrations between Stripe accounts. It is designed to preserve recurring-revenue continuity while reducing double-billing and cutover risk during a SaaS handover.

MoveMRR is designed for SaaS founders who are selling their business and need to transfer Stripe subscriptions to the buyer. It is also used by SaaS buyers, brokers, and agencies supporting SaaS acquisitions.

When you sell a SaaS business, the buyer typically needs recurring revenue in their own Stripe account. Stripe Customer Data Copy does not move existing Subscription objects, while Stripe's Billing Migration Toolkit focuses on recreating billing data. MoveMRR coordinates the surrounding mappings, rehearsals, two-account cutover, source deactivation, reconciliation, and audit trail.