Dry-run reports

A dry-run builds the migration plan without creating live buyer-side subscriptions.

Use it to decide whether the migration is ready, which subscriptions are blocked, and which actions RevBridge would execute.

Report fields

The dry-run report includes:

• supportedCount: subscriptions that can move automatically.
• blockedCount: subscriptions that cannot execute until resolved.
• needsPriceCloneCount: supported cases where a buyer price clone is planned.
• needsCouponCloneCount: supported cases where a buyer coupon clone is planned.
• actions: the approved action plan if blockers are resolved.
• blockers: migration-stopping issues.
• warnings: conditions that require review but do not always stop execution.

Planned actions

Dry-run actions can include subscription creation, price cloning, coupon cloning, and customer default payment method updates.

The action plan is the safest source of truth for what execution will attempt.

Review workflow

Before execution:

1. Confirm mapped customers are correct.
2. Resolve blockers.
3. Review warnings with the billing owner.
4. Confirm expected revenue exposure.
5. Keep the dry-run output for reconciliation.