The direct answer
MoveMRR supports multiple recurring items when all source items have destination mappings and compatible timing. If one item is unmapped, carries account-specific tax behavior, or uses an incompatible interval, the complete subscription should be held for review rather than partially recreated.
Reviewed July 24, 2026 by the MoveMRR product team.
Migration behavior: Multi-Item Stripe Subscriptions
The destination subscription is built from the complete approved item set. Atomic handling prevents a subscription from being accepted with only some of its recurring products. Quantities, currencies, intervals, taxes, and price behavior are validated at item level.
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.
- Every recurring item has an approved destination price mapping.
- Quantities and currencies match the source.
- Intervals and interval counts produce one valid destination billing model.
- Item-level tax rates and metadata are reviewed.
The primary failure mode to control
Partially recreating a subscription silently changes what the customer receives and pays for. A single missing mapping must block or exclude the whole subscription according to the approved policy.
Multi-Item Stripe Subscriptions: source-to-destination checks
| Check | Required evidence | If it fails |
|---|---|---|
| Item coverage | All recurring items map | Hold the complete subscription |
| Quantity | Destination quantity matches source | Correct planned action |
| Intervals | Cadence is compatible | Manual design required |
| Item tax | Destination tax behavior approved | Resolve tax mapping |
A controlled workflow
- 1
Verify the first prerequisite
Every recurring item has an approved destination price mapping.
- 2
Verify the second prerequisite
Quantities and currencies match the source.
- 3
Test representative examples
Use sandbox data that includes the difficult records, not only the happy path.
- 4
Control the primary failure mode
Partially recreating a subscription silently changes what the customer receives and pays for. A single missing mapping must block or exclude the whole subscription according to the approved policy.
- 5
Reconcile after creation
Compare destination behavior with the approved source-state and monitor the next event.
Limits to verify before migration
- Mixed recurring intervals can require a different destination design.
- One-time invoice items are not the same as recurring subscription items.
- Usage state attached to metered items requires separate treatment.
- Account-specific tax-rate objects need destination equivalents.
Frequently asked questions
Can a subscription with several products be migrated?
Yes when every recurring item maps to a compatible destination price and the combined billing cadence is supported.
What happens if one item is unmapped?
The safe behavior is to hold or exclude the complete subscription rather than silently creating a partial commercial contract.
Can item quantities be preserved?
Quantities can be carried into the planned destination items and should be checked in the dry-run output.