Audit exports

Audit exports help the buyer, seller, and deal team understand what happened during the migration.

RevBridge exposes CSV and PDF audit export actions from the migration console.

What to reconcile

After execution, review audit records against:

• Source customer IDs.
• Destination customer IDs.
• Source subscription IDs.
• Destination subscription IDs.
• Actions executed.
• Failures or skipped records.
• Final project status.

VERIFY_DESTINATION_WRITE records can include a temporary inactive product ID. RevBridge creates that product to prove buyer-side product write scope, then attempts to delete it immediately. If cleanup fails, the audit row includes the product ID for manual cleanup in Stripe.

CLONE_PRODUCT records show buyer-side product clones created for shared source products before price clones are created. The product ID is included in the audit message.

Failed CREATE_SUBSCRIPTION records include the destination subscription ID when Stripe created a buyer-side subscription but RevBridge stopped before seller-side cancellation because a post-create safety check failed, such as an unexpected non-zero initial destination invoice.

Failed CANCEL_SOURCE records include the destination subscription ID when the buyer-side subscription exists but the seller-side cancel_at_period_end update failed.

VERIFY_CUSTOMER_DISCOUNTS records show the final pre-execution recheck for customer-level discounts. If a customer discount appears after dry-run, execution stops before buyer-side subscription creation because Stripe can inherit customer discounts onto new subscriptions.

VERIFY_CUSTOMER_BALANCES records show the final pre-execution recheck for customer balance, invoice credit balance, and cash balance fields. If a non-zero balance appears after dry-run, execution stops before buyer-side subscription creation because Stripe can apply those balances to future invoices.

VERIFY_CUSTOMER_TAX records show the final pre-execution recheck for customer tax exemption and tax ID configuration. If customer tax state appears after dry-run, execution stops before buyer-side subscription creation because Stripe can alter future invoice totals.

VERIFY_CUSTOMER_INVOICE_SETTINGS records show the final pre-execution recheck for customer invoice custom fields, footer, and rendering options. If these settings appear after dry-run, execution stops before buyer-side subscription creation because Stripe can inherit them onto future invoices.

VERIFY_CUSTOMER_INVOICES records show the final pre-execution recheck for non-zero customer invoices that are not paid or void. If a draft, open, or uncollectible invoice appears after dry-run, execution stops before buyer-side subscription creation because v1 does not migrate existing receivables or debt collection state.

Export formats

CSV is useful for finance and operator reconciliation. PDF is useful for deal records and handoff documentation.

The CSV export includes these non-PII identifier columns for reconciliation:

• sourceSubscriptionId
• destinationSubscriptionId
• sourceCustomerId
• destinationCustomerId
• sourcePriceId
• destinationPriceId
• sourceCouponId
• destinationCouponId
• idempotencyKey

Both should be treated as migration evidence, not a substitute for reviewing the buyer Stripe account directly.

Review timing

Download audit records after dry-run review and again after execution completes.