Handover scope

What RevBridge can move in a Stripe handover

Check your subscriptions against this list before you connect either Stripe account. Every row below reflects what the product does today, and the codes match the ones a dry-run report shows you.

Last verified: 2026-08-18
Shapes listed: 21 supported, 15 to review, 54 blocked

Read the blocker reference

How to read a verdict

Supported: RevBridge moves this shape and preserves its terms. Nothing is asked of the customer.
Review first: Nothing here stops the handover by itself, though one subscription can raise a review condition and a blocker together. Most appear in the dry-run as a named warning against the subscription that raised them. A few cover subscriptions the scan never returns, so nothing reports them and this page is the only place they are listed.
Blocked: RevBridge refuses this shape. One blocked subscription stops the whole migration, because a half-finished handover is never an outcome.

Accounts and mapping

What both accounts need before the dry-run can judge a single subscription.

Accounts and mapping: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
Stripe Customer Data Copy mapping	Supported	Copy customers to the buyer account with Stripe first, then upload the mapping file Stripe gives you. RevBridge reads the seller and buyer customer id for every customer in the handover. Stripe data migrations.
Seller account with nothing left to move	Blocked	The scan found no subscription to judge. It reads every subscription except canceled and expired ones, so an account whose remaining subscriptions are all unpaid or paused is not stopped here — each of those gets its own blocker instead.`NO_SOURCE_SUBSCRIPTIONS`
Customer missing from the mapping file	Blocked	Every seller customer with a subscription in the handover needs a row. A missing row blocks the whole migration rather than skipping that customer.`MISSING_CUSTOMER_MAPPING`

Subscription statuses

Which Stripe subscription states RevBridge will hand over.

Subscription statuses: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
Active subscriptions	Supported	The core case. The buyer keeps billing the same customer on the same terms at the same renewal date. Stripe subscription statuses.
Canceled and expired subscriptions	Review first	RevBridge leaves them where they are. They collect no future revenue, so the dry-run never reports them. Check the count if you expected them to move.
Test Clock subscriptions	Review first	Stripe returns these only when you ask for a specific test clock, and RevBridge does not ask. They are left out of the scan rather than blocked, so the rest of the account still migrates. An account holding nothing else stops for having nothing to move.
Any status other than active or trialing	Blocked	Incomplete, past due, and unpaid carry unsettled money: settle or end them in the seller account, then run the dry-run again. A status RevBridge does not recognize — an unreadable value, or one Stripe adds later — lands here too, because its billing behavior has not been reviewed and cannot be assumed safe.`UNSUPPORTED_SUBSCRIPTION_STATUS`
Paused after a trial	Blocked	Stripe's paused status has no payment method and issues no invoices. It cannot be created as paused in the buyer account, so RevBridge refuses it. Stripe trial settings.`PAUSED_SUBSCRIPTION`

Trials

What happens to a customer who has not started paying yet.

Trials: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
Active trial with a future end date	Supported	The buyer subscription is created with the same trial end, so the first charge lands on the day the customer was promised. Stripe trials.
Trial with an earlier end date already set	Supported	When the seller scheduled the subscription to end before the trial does, RevBridge carries both dates across rather than collapsing them into one.
Trial ending within 48 hours of the handover	Review first	Stripe can reject a trial end that close. RevBridge then anchors the first charge to the same moment and records that the customer is no longer marked as trialing. The dry-run raises this for any trial inside the 48-hour window, whether or not Stripe ends up refusing. A trial already set to wind down before its trial date is the exception: it ends at that earlier date and never reaches a first charge.`NEAR_TRIAL_ANCHOR_FALLBACK_POSSIBLE`
Trial with no card on the seller side	Review first	The buyer customer already has a card, so the handover can proceed, but nothing is bound to the subscription. Decide whether you want that card attached before the trial ends.`TRIAL_WITHOUT_PAYMENT_METHOD`
Trial settings RevBridge does not recognize	Blocked	RevBridge mirrors Stripe's documented cancel, create invoice, and pause behavior, and refuses any other value. It also refuses any other field set under trial settings, even when the behavior itself is one it knows, because an unread trial setting can change when the customer is first charged.`TRIAL_SETTINGS_UNSUPPORTED`
Trialing with no future trial end	Blocked	The subscription says it is trialing but gives no date to preserve, so RevBridge cannot prove when the first charge falls.`MISSING_TRIAL_END`
Stripe Trial Offers on an item	Blocked	Trial offers change what the item charges over time. RevBridge does not reproduce them.`TRIAL_OFFER_UNSUPPORTED`

Intervals and renewal timing

How often the customer is billed, and whether the next date survives the move.

Intervals and renewal timing: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
Daily, weekly, monthly, and yearly billing	Supported	Any interval count Stripe accepts works, including quarterly and half-yearly. The buyer subscription is anchored to the seller's next renewal date, with no proration. Stripe billing cycles.
Classic and flexible billing modes	Supported	RevBridge mirrors whichever mode the seller subscription uses, because Stripe cannot move a flexible subscription back to classic. Stripe billing modes.
An interval outside Stripe's four values	Blocked	The next renewal date can be perfectly readable and this still applies. RevBridge cannot recreate and check a cadence it does not recognize, so it cannot promise the renewals after the handover land where the customer expects.`UNSUPPORTED_INTERVAL`
Calendar anchor rules	Blocked	RevBridge preserves the next renewal date but does not rebuild a rule that pins billing to a day of the month.`BILLING_CYCLE_ANCHOR_CONFIG_UNSUPPORTED`
Unknown billing mode or flexible settings	Blocked	A billing mode field RevBridge has not reviewed can change invoice amounts, so it stops rather than guess.`FLEXIBLE_BILLING_MODE_UNSUPPORTED`
No readable renewal date	Blocked	Without a current period end there is nothing to preserve on the buyer side.`MISSING_CURRENT_PERIOD_END`
Renewal date already passed	Blocked	Stripe needs a future anchor, and this subscription reports one in the past. The dry-run compares against the clock rather than against an earlier reading, so this is not a sign that something moved while it ran, and running it again will not clear it. Reconcile the subscription in the seller account first.`RENEWAL_TIMESTAMP_NOT_FUTURE`

Subscription items

Subscriptions that bill for more than one thing at once.

Subscription items: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
Several items on one subscription	Supported	Each item is checked, priced, and recreated on its own, and quantities carry across per item. All items must share one interval and one renewal date. Stripe subscription items.
Items billed on different intervals	Blocked	One subscription gets one anchor. Items that renew on different cycles cannot keep their timing through a single move.`MIXED_ITEM_INTERVALS`
Items with different period end dates	Blocked	Same reason: divergent per-item dates cannot be reproduced from one preserved renewal date.`ITEM_PERIOD_END_MISMATCH`

Prices and quantities

What the customer pays, and how RevBridge recreates it.

Prices and quantities: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
Fixed per-unit recurring prices	Supported	The amount, interval, and quantity are recreated exactly in the buyer account. Stripe pricing models.
A price the buyer account is missing, or holds in a form RevBridge will not use	Supported	RevBridge clones the price with the same terms and a link back to the seller object, then reuses that clone on later runs. It clones rather than reuses whenever a buyer-side price of the same ID is inactive, or its amount, currency options, tax behavior, or lookup key differ. An existing buyer product carrying the right lineage is reused rather than cloned again.
Tiered, transformed-quantity, and amount-less prices	Blocked	These compute the amount at invoice time rather than stating it. RevBridge will not recreate a price whose economics it cannot read. Stripe price object.`UNSUPPORTED_PRICE_STRUCTURE`
Metered and usage-based billing	Blocked	Usage records live in the seller account and set the amount after the fact. RevBridge does not move usage history, so it refuses these subscriptions. Stripe usage-based billing.`METERED_PRICE`
An item with no readable recurring price	Blocked	This covers a subscription with no items at all, and any single item whose recurring price RevBridge cannot read. The rest of the subscription can still carry future revenue; RevBridge refuses because it cannot recreate every item safely, not because there is nothing worth moving.`NO_RECURRING_PRICE`

Currencies

Whether the customer keeps paying in the same money.

Currencies: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
Billing in each price's base currency	Supported	RevBridge pins the buyer subscription to the same currency and the same base amount, so the renewal cannot change value in the move.
A currency RevBridge cannot prove	Blocked	A price with several currency options can bill in one that is not its base, and RevBridge refuses those rather than risk a different renewal amount. The same blocker covers currency it cannot read at all: a missing subscription currency, a missing base currency or amount, or currency options Stripe did not return. Stripe currency options.`PRESENTMENT_DETAILS_UNSUPPORTED`

Tax

Tax state stays where it is; it does not travel.

Tax: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
Prices marked tax inclusive or exclusive	Supported	A cloned buyer price keeps the same setting, and a buyer price already there is reused only if its setting already matches. Either way automatic tax stays off during the handover, so invoice totals do not move.
Stripe Tax, tax rates, and item tax rates	Blocked	These change what a customer owes. Set them up in the buyer account and handle the affected subscriptions yourself. Stripe Tax.`TAX_UNSUPPORTED`
Tax status or tax IDs on the seller customer	Blocked	RevBridge does not copy customer tax state, and a customer carrying it is refused rather than migrated without it.`CUSTOMER_TAX_UNSUPPORTED`
Tax status or tax IDs on the buyer customer	Blocked	Existing buyer-side tax state would apply to the new subscription and change the amount due, so RevBridge stops first.`DESTINATION_CUSTOMER_TAX_UNSUPPORTED`

Discounts and coupons

Which price reductions survive the handover intact.

Discounts and coupons: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
A forever coupon on the subscription	Supported	Percent off or amount off. RevBridge clones a buyer coupon with the same terms, or reuses a matching one already there, so every future invoice keeps the same discount. Stripe coupons.
A once coupon not yet used	Supported	Carried across so the customer still gets the single discounted charge they were promised.
A repeating coupon with months left	Supported	RevBridge clones a buyer coupon whose remaining window discounts exactly the same future renewals, not the same original duration.
A once coupon already spent	Review first	The discount was consumed in the seller account. The buyer subscription shows the normal renewal amount, which is what should happen.`ONCE_COUPON_ALREADY_CONSUMED`
A repeating coupon ending before the next renewal	Review first	No future invoice on either side would be discounted, so the subscription moves without the coupon.`REPEATING_COUPON_EXPIRES_BEFORE_RENEWAL`
A repeating coupon RevBridge cannot reproduce	Blocked	Most often no whole-month duration discounts the same renewals, which is common on weekly and daily billing. The same blocker covers a discount whose applied window Stripe does not return, invalid duration fields, renewal timing that cannot be computed, and a window spanning too many renewals to check. RevBridge refuses rather than move the discount to a different set of invoices.`REPEATING_COUPON_UNSUPPORTED`
A once coupon on a voided invoice	Blocked	The invoice cannot be collected, so nobody can tell whether the discount was meant to be used. Fix the invoice in the seller account first.`VOIDED_ONCE_COUPON_UNSUPPORTED`
More than one discount on a subscription	Blocked	RevBridge reproduces one discount per subscription and refuses to guess how several combine.`MULTIPLE_DISCOUNTS_UNSUPPORTED`
Discounts attached to a single item	Blocked	RevBridge carries subscription-level discounts only. Stripe discounts.`ITEM_DISCOUNT_UNSUPPORTED`
Promotion-code discounts	Blocked	A promotion code carries redemption rules that belong to the seller account and cannot be recreated safely. Stripe promotion codes.`PROMOTION_CODE_UNSUPPORTED`
Coupons limited to certain products	Blocked	The scope depends on seller-side product ids, which do not exist in the buyer account.`PRODUCT_SCOPED_COUPON`
A discount on the seller customer	Blocked	Every shape of this is refused, for reasons that differ by shape. Stripe's current API does not accept discount writes on a customer, and spreading one across subscriptions can change what each invoice charges. The same row covers a fixed amount off, which multiplies per invoice; a discount that conflicts with one already on the subscription or an item; a once discount spread over several subscriptions; a coupon or window Stripe did not return; and a full-scope percent off, which is deferred until it can be proved end to end rather than judged unsafe. The dry-run names which one you have.`CUSTOMER_DISCOUNT_UNSUPPORTEDCUSTOMER_PERCENT_OFF_DISCOUNT_UNSUPPORTEDCUSTOMER_AMOUNT_OFF_DISCOUNT_UNSUPPORTEDCUSTOMER_DISCOUNT_WITH_SUBSCRIPTION_DISCOUNT_UNSUPPORTEDCUSTOMER_ONCE_DISCOUNT_MULTIPLE_SUBSCRIPTIONS_UNSUPPORTEDCUSTOMER_DISCOUNT_FULL_SCOPE_UNPROVEN`
A discount already on the buyer customer	Blocked	It would apply to the new subscription and change the renewal amount, so RevBridge stops before creating one.`DESTINATION_CUSTOMER_DISCOUNT_UNSUPPORTED`
Any other coupon structure	Blocked	A coupon whose terms RevBridge cannot reproduce exactly is refused rather than approximated.`UNSUPPORTED_COUPON`

Payment methods

Whether the buyer can charge the same card without asking the customer for it again.

Payment methods: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
A card matched between the two accounts	Supported	RevBridge matches the copied card by brand, last four digits, and expiry, then binds it to the buyer subscription. The customer re-enters nothing.
A subscription that can never charge	Supported	A price of zero, a quantity of zero, or a forever coupon that discounts the whole amount. RevBridge can prove no future invoice collects anything, so every card rule below is skipped and the subscription migrates without one. It still binds the copied card when exactly one match exists.
The card came from somewhere other than the subscription	Review first	The subscription named no instrument, so RevBridge fell back to the customer default, the latest invoice, or the oldest one on file, and says which it used. The latest invoice supplies its instrument whatever the invoice status, so check this is what you expect to charge. If the fallback turns out not to be a card, this warning arrives with the blocker below.`SOURCE_CUSTOMER_DEFAULT_PAYMENT_METHOD_USEDSOURCE_CUSTOMER_DEFAULT_SOURCE_USEDSOURCE_LATEST_INVOICE_PAYMENT_METHOD_USEDSOURCE_LATEST_INVOICE_SOURCE_USEDSOURCE_CUSTOMER_OLDEST_PAYMENT_METHOD_USEDSOURCE_CUSTOMER_OLDEST_SOURCE_USED`
The buyer customer default will be set	Review first	When every migrated subscription for that customer lands on the same modern card, RevBridge also makes it the customer's invoice default. A card matched as a legacy source stays bound to its own subscriptions and changes no customer default.`CUSTOMER_DEFAULT_PAYMENT_METHOD_WILL_BE_SET`
The buyer customer default is left alone	Review first	The customer's subscriptions resolve to different cards, so RevBridge binds each subscription and changes no customer default.`CUSTOMER_DEFAULT_PAYMENT_METHOD_SKIPPED_MULTI_CARD`
No card on the seller customer	Blocked	There is nothing to match, and a renewal that charges would fail on the buyer side. This applies only to a subscription that can still collect a future non-zero invoice.`SOURCE_CUSTOMER_NO_PAYMENT_METHOD`
No matching card on the buyer customer	Blocked	The copy step did not bring the card across. Run Stripe's customer copy again before the handover. This applies only to a subscription that can still collect a future non-zero invoice.`SUBSCRIPTION_PAYMENT_METHOD_MAPPING_MISSING`
Several cards that look the same	Blocked	When two buyer-side instruments share a brand, last four, and expiry, RevBridge refuses rather than pick one. This applies only to a subscription that can still collect a future non-zero invoice.`SUBSCRIPTION_PAYMENT_METHOD_MAPPING_AMBIGUOUS`
The buyer customer has no card at all	Blocked	Renewal would depend on collecting a payment method after the handover, which is exactly the interruption RevBridge exists to avoid. This applies only to a subscription that can still collect a future non-zero invoice.`DESTINATION_CUSTOMER_NO_PAYMENT_METHOD`
Anything other than a card	Blocked	Bank debits, wallets, and other instruments are outside the current scope. This applies only to a subscription that can still collect a future non-zero invoice.`SUBSCRIPTION_PAYMENT_METHOD_UNSUPPORTED`
Invoices sent for manual payment	Blocked	RevBridge hands over subscriptions Stripe charges automatically. Manually invoiced subscriptions are refused. Stripe subscription invoices.`MANUAL_COLLECTION_UNSUPPORTED`

Invoices and receivables

Money already owed stays with the seller.

Invoices and receivables: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
Invoice fields and footers on the seller customer	Review first	Custom fields, footers, and PDF options change how an invoice reads, not what it charges. RevBridge does not copy them, and says which customers had them. Stripe invoice customization.`SOURCE_CUSTOMER_INVOICE_RENDERING_NOT_MIGRATED`
Invoice fields and footers on the buyer customer	Review first	The buyer's own invoice design stays as it is and applies to the migrated subscription.`DESTINATION_CUSTOMER_INVOICE_RENDERING_PRESERVED`
An unpaid balance on the latest invoice	Blocked	RevBridge moves future collection only. Settle the invoice in the seller account first.`OUTSTANDING_INVOICE_UNSUPPORTED`
Draft, open, or uncollectible invoices on the seller customer, worth more than zero	Blocked	Open receivables belong to the seller. RevBridge will not leave them behind silently. An invoice with nothing left to collect is ignored.`CUSTOMER_OUTSTANDING_INVOICE_UNSUPPORTED`
Draft, open, or uncollectible invoices on the buyer customer, worth more than zero	Blocked	RevBridge wants the buyer customer clean before it adds a subscription, and refuses unreconciled buyer-side receivables rather than migrate alongside them. An invoice with nothing left to collect is ignored.`DESTINATION_CUSTOMER_OUTSTANDING_INVOICE_UNSUPPORTED`
Pending invoice items on the seller side	Blocked	These are charges queued for the next invoice. RevBridge does not move them, so it stops rather than drop them. Only items that can reach this handover count: one sitting on the customer with no subscription of its own, or one attached to the subscription being moved. An item belonging to another subscription is left alone.`PENDING_INVOICE_ITEM_UNSUPPORTED`
Pending invoice items on the buyer side	Blocked	They would attach to the first buyer invoice for this customer and change what it charges.`DESTINATION_PENDING_INVOICE_ITEM_UNSUPPORTED`

Credits and balances

Balances change future invoice amounts, so they are refused.

Credits and balances: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
A credit or debit on the seller customer	Blocked	Account balance, invoice credit, and cash balance all change what a future invoice collects. Settle them before the handover. Stripe customer balances.`CUSTOMER_BALANCE_UNSUPPORTED`
A credit or debit on the buyer customer	Blocked	The same problem on the other side, in both directions: existing credit would quietly absorb the first renewal, and an existing debit would add to what the buyer invoice collects.`DESTINATION_CUSTOMER_BALANCE_UNSUPPORTED`

Schedules, pauses, and pending changes

Anything that changes the terms after the handover moment.

Schedules, pauses, and pending changes: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
Subscription schedules	Blocked	A schedule holds future phases with different terms. RevBridge moves one set of current terms and does not rebuild the phases. Stripe subscription schedules.`SUBSCRIPTION_SCHEDULE`
Paused collection	Blocked	Stripe accepts a pause only after the subscription exists, which means a second write and a gap where the state is wrong. RevBridge refuses every paused subscription rather than carry that risk. Stripe pause payment collection.`PAUSE_COLLECTION_UNSUPPORTED`
A pending update waiting on payment	Blocked	Stripe applies the new terms only once the latest invoice is paid, so nobody can prove which terms are current at the handover moment. Stripe subscription updates.`PENDING_SUBSCRIPTION_CHANGE_UNSUPPORTED`
A schedule for invoicing pending items	Blocked	Stripe restarts that schedule from the buyer-side creation date and offers no way to set its phase, so future items would be invoiced on a different day. The same blocker covers schedule state RevBridge cannot read: a next pending invoice date with no valid interval behind it, or an interval object it cannot make sense of.`PENDING_INVOICE_ITEM_INTERVAL_UNSUPPORTED`

Subscription settings

Settings that decide how Stripe charges and what it records.

Subscription settings: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
Card-only payment settings	Supported	RevBridge pins every buyer subscription to card payments, so a seller subscription already set that way carries across unchanged.
Subscription, product, price, and coupon metadata	Supported	Subscription and item metadata is copied when the buyer subscription is created. Product, price, and coupon metadata comes across only on objects RevBridge creates: when a matching one already exists in the buyer account it is reused as it stands, keeping its own metadata. Stripe's limits apply throughout, and RevBridge adds its own lineage keys so a later run can find its work.
Metadata trimmed to fit	Review first	When a source object is at Stripe's metadata limit, some keys cannot come across. The dry-run names the subscription, item, price, or coupon this happens to. A cloned product is trimmed the same way but is not reported, so check a product carrying many keys yourself.`METADATA_KEYS_TRUNCATED`
Custom payment settings	Blocked	Non-card payment method types, payment method options, and save-default behavior are outside the current scope. Any other field set under payment settings lands here too, so a subscription that looks card-only can still be refused for a setting RevBridge has not reviewed.`PAYMENT_SETTINGS_UNSUPPORTED`
Custom subscription invoice settings	Blocked	RevBridge does not reproduce per-subscription invoice configuration.`INVOICE_SETTINGS_UNSUPPORTED`
Billing thresholds	Blocked	A threshold can invoice a customer early, off the preserved cycle.`BILLING_THRESHOLDS_UNSUPPORTED`
Connect routing, account-issued invoices, and account tax liability	Blocked	Transfer data, application fees, and on-behalf-of route money to a third account, and that routing does not exist in the buyer account. The same blocker covers a subscription whose invoices are issued by another account or whose tax liability sits with one, because both name an account the buyer does not control. Stripe Connect subscriptions.`CONNECT_TRANSFER_UNSUPPORTED`

Wind-down timing

When the seller stops billing, so nobody is charged twice.

Wind-down timing: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
A subscription with no end date set	Supported	RevBridge sets the seller subscription to stop at the renewal the buyer now owns. One renewal, one charge, on the same day as before. Stripe subscription cancellation.
A subscription ending at the handover renewal	Supported	Stripe has already shortened the period to that date, so the seller subscription is left exactly as it is and the buyer subscription carries the same date.
A subscription ending after the handover renewal	Supported	The buyer subscription carries the exact end date. The seller subscription is set to stop at the handover renewal instead of its later date, so it cannot keep billing alongside the buyer.
A subscription the seller had already set to end	Review first	The dry-run names this whether the seller used the end-at-period-end flag or an exact date, and RevBridge mirrors whichever one it finds. Check that you meant to hand over a subscription that is ending.`SOURCE_CANCEL_AT_PERIOD_END_MIRRORED`
An end date RevBridge will not migrate	Blocked	Two shapes land here. An end date that falls before the next renewal leaves no future invoice to hand over, so there is nothing to migrate. A wind-down shape RevBridge cannot read exactly is refused rather than guessed at.`CUSTOM_CANCEL_AT_UNSUPPORTED`

Prior migrations and recovery

Running the handover again after a stopped or finished run.

Prior migrations and recovery: which subscription shapes RevBridge moves, which need review, and which it refuses.
Subscription shape	Verdict	What happens
A subscription an earlier run already moved	Review first	RevBridge finds its own work in the buyer account, checks the timing, discount, and card still match, and the dry-run proposes no work for it. No second subscription is created.`SUBSCRIPTION_ALREADY_MIGRATED_SKIPPED`
A subscription from a run that stopped part-way	Review first	The buyer subscription exists and every check still passes, so the next run finishes that one instead of creating a second.`DESTINATION_SUBSCRIPTION_PAUSE_RECOVERY_PLANNED`
A prior migration that no longer matches	Blocked	Look at both accounts, not just the buyer. This covers a buyer subscription whose timing, discount, items, or card moved since it was created, a seller wind-down that was cleared or changed after the earlier run finished, and invoice history on the buyer clone that is not safe to reuse. RevBridge refuses to reuse it and asks you to settle it by hand.`DESTINATION_SUBSCRIPTION_ALREADY_MIGRATED_UNSAFE`
A buyer customer holding a subscription RevBridge did not expect	Blocked	Either the customer already has a live subscription this handover did not create, which usually means the mapping points at the wrong customer, or it holds two live subscriptions carrying RevBridge lineage for the same seller subscription, which can bill the buyer twice. Both refuse until you resolve them by hand.`DESTINATION_CUSTOMER_HAS_EXISTING_SUBSCRIPTION`

Codes from an older report

A dry-run you saved before a rule changed can name a code no row above lists. RevBridge no longer raises these, and the shapes they used to refuse now migrate: several items on one subscription, and invoice fields on either customer. Run the dry-run again to see the current verdict.

CUSTOMER_INVOICE_SETTINGS_UNSUPPORTEDDESTINATION_CUSTOMER_INVOICE_SETTINGS_UNSUPPORTEDMULTIPLE_ITEMS

A dry-run tells you which rows you actually have.

Connect both Stripe accounts with restricted keys. RevBridge’s setup links preselect the exact permissions it needs, which include the write access the run uses later. The dry-run itself only reads: it walks every billing-relevant subscription, names each blocker and warning against the subscription that raised it, and writes nothing. Nothing moves until you approve that dry-run.