Frequently Asked Questions

MoveMRR is a one-time-use SaaS tool that helps founders safely migrate customers, active subscriptions, and products from one Stripe account to another when selling a SaaS business. It ensures MRR continuity without double-charging customers.

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 wants the recurring revenue to flow into their own Stripe account. Stripe does not offer a simple plug-and-play solution for this, making manual migration slow, risky, and error-prone.

You create a transfer project, connect both Stripe accounts using restricted API keys, perform Stripe's Customer Data Copy to move payment methods, upload the mapping CSV, and then execute the migration. MoveMRR recreates subscriptions in the new account and safely deactivates the old ones.

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.

Old subscriptions are safely deactivated only after new subscriptions are confirmed in the destination account. This ensures customers are never double-charged and revenue continuity is preserved.

Yes. MoveMRR recreates subscriptions with the same billing dates and renewal periods, ensuring customers experience no disruption in their billing schedule.

Yes. MoveMRR creates subscriptions in the destination account with preserved billing anchors and no proration charges. Old subscriptions are only deactivated after confirming the new ones are active. Payment methods transfer via Stripe's Customer Data Copy, so no re-authorization is required. Customers experience no interruption.

No. Stripe's Customer Data Copy transfers payment methods automatically. MoveMRR recreates subscriptions seamlessly. Neither Stripe nor MoveMRR notifies customers. You decide whether to communicate about the ownership change.

Yes. MoveMRR explicitly sets the billing cycle anchor to match the original subscription and disables proration. No unexpected charges, no billing date resets. Products and prices are recreated identically in the new account, preserving currency, amount, interval, tiers, and metadata.

Invoice history and payment records stay in the source account (Stripe limitation). Dunning settings are account-level and must be configured in the new account. Everything else transfers: products, prices, subscription metadata, and coupons are all recreated in the destination account.

Cleanly preserved. When MoveMRR auto-creates prices, it copies the currency, unit amount, and all currency options. USD, EUR, SEK, or any other currency subscriptions will have prices created in their respective currencies in the destination account.

MoveMRR does not trigger charges during migration. Subscriptions are created with matching billing anchors and no proration, so no charge occurs at migration time. The first charge happens on the customer's normal renewal date, handled by Stripe's dunning in the new account.

MoveMRR does not influence Stripe's risk assessment. The new account's risk profile depends on its own history and verification status. Customer Data Copy brings over established payment methods, which generally helps. No payout holds or Radar issues are introduced by the migration itself.

Your choice. MoveMRR does not notify customers. Many acquirers stay silent since the billing experience is identical from the customer's perspective. If you notify, frame it as a business update — customers see no change to their subscription, billing date, or price.

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.

Yes, as long as Stripe's Customer Data Copy supports both countries. MoveMRR works with any Stripe account regardless of location. The key dependency is Stripe's ability to transfer payment methods between the two accounts. We recommend verifying with Stripe support that Customer Data Copy is available for your specific country pair before starting.

No. MoveMRR works with any Stripe account type — Individual, Sole Proprietorship, Company, or Non-profit. The migration process is identical regardless of account structure. What matters is that both accounts have the necessary API permissions and that Stripe's Customer Data Copy is available between them.

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 is currently in early access. Join the waitlist to be notified when pricing is announced and to receive early-bird benefits.

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

Early access users receive priority support. For general inquiries, contact us at jovanovic@thecodecave.de.