Customer mapping CSV

RevBridge expects a source-to-destination customer mapping file before dry-run validation.

The mapping is the control plane for the migration. It tells RevBridge which seller customer corresponds to which buyer customer.

Upload the Stripe Data Transfer / Customer Data Copy CSV without editing it in a spreadsheet tool. If you need to create a test file manually, keep it as plain CSV text.

Required values

Each non-empty mapping row must contain:

• A source customer ID from the seller Stripe account.
• A destination customer ID from the buyer Stripe account.

Both values must be Stripe customer IDs that start with cus_.

old_customer_id,new_customer_id
cus_seller_123,cus_buyer_456
cus_seller_789,cus_buyer_999

Accepted headers

RevBridge intentionally accepts only Stripe's Customer Data Copy header pair:

• old_customer_id
• new_customer_id

Other guessed aliases such as source_customer_id, destination_customer_id, customer_id, copied_customer_id, or free-form labels are rejected so the parser does not silently read the wrong columns.

Validation behavior

The CSV must include a header and at least one mapping row. Empty rows are ignored. Rows with non-cus_ identifiers are rejected.

Each source customer and each destination customer can appear only once. Duplicate source rows, duplicate destination rows, and rows that map a customer ID to itself are blocked because the migration must be a one-to-one customer handoff.