The direct answer
Past-due subscriptions require an explicit inclusion decision. MoveMRR can include them in a reviewed run and preserves a future billing boundary rather than forcing an immediate destination charge. The destination recreation does not erase the source invoice history, collection state, or underlying payment problem.
Reviewed July 24, 2026 by the MoveMRR product team.
Migration behavior: Past-Due Stripe Subscriptions
A past-due status reflects an unpaid source invoice and active collection logic. Recreating the subscription in a new account creates a new billing object; it does not transfer the historical invoice or dunning state. The migration plan must separate subscription continuity from recovery of the existing receivable.
What the readiness review must verify
Compatibility is established from the actual Stripe objects, not from a page title. The project should surface every missing mapping, unsupported field, ambiguous state, and destination prerequisite before the live run.
- The project explicitly includes past-due subscriptions.
- The unpaid source invoice and collection owner are documented.
- Destination creation uses a future boundary rather than an immediate charge.
- Dunning, access, and support behavior are defined in the buyer’s application.
The primary failure mode to control
Treating past-due subscriptions like normal active records can trigger an unexpected destination payment attempt while the source still pursues debt, or can grant access without a clear collection policy.
Past-Due Stripe Subscriptions: source-to-destination checks
| Check | Required evidence | If it fails |
|---|---|---|
| Source debt | Invoice and collection owner recorded | Keep debt handling outside the migration batch |
| Destination date | Future boundary approved | Block immediate creation |
| Payment method | Coverage known; failure path assigned | Manual review |
| Entitlement | Buyer policy for unpaid accounts tested | Do not accept application handover |
A controlled workflow
- 1
Verify the first prerequisite
The project explicitly includes past-due subscriptions.
- 2
Verify the second prerequisite
The unpaid source invoice and collection owner are documented.
- 3
Test representative examples
Use sandbox data that includes the difficult records, not only the happy path.
- 4
Control the primary failure mode
Treating past-due subscriptions like normal active records can trigger an unexpected destination payment attempt while the source still pursues debt, or can grant access without a clear collection policy.
- 5
Reconcile after creation
Compare destination behavior with the approved source-state and monitor the next event.
Limits to verify before migration
- Historical invoices and dunning state are not transferred as destination history.
- MoveMRR does not decide whether debt is assigned in a transaction.
- Failed payment credentials remain failed until the underlying issue is resolved.
- Legal and accounting treatment of receivables needs professional review.
Frequently asked questions
Does migrating a past-due subscription collect the unpaid invoice?
No. The source receivable and invoice history remain separate. Destination subscription continuity and debt recovery need distinct plans.
Can past-due records be excluded?
Yes. They should be included only when the project configuration and deal policy explicitly call for it.
Will the destination charge immediately?
The reviewed path preserves a future billing boundary for included past-due records rather than intentionally starting an immediate charge.