Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Developer tools
Get started
Payments
Finance automation
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
OverviewExplore all products
Start building
Start developing
Sample projects
About the APIs
Building with LLMs
Use Stripe without code
Set up Stripe
Create an account
Products and prices
Web Dashboard
Mobile Dashboard
Migrate to Stripe
Migrate customer data
Migrate payment data
    Overview
    Import payment data
      Card data imports
      ACH data imports
      UK Bacs data imports
      SEPA data imports
      PADs/ACSS data imports
      AU BECS data imports
      Map payment data
      Upload supplementary data
    Export payment data
    Copy payment data
Migrate subscriptions
Manage fraud risk
Understand fraud
Radar fraud protection
Manage disputes
Verify identities
Regulatory support
HomeGet startedMigrate payment dataImport payment data

Map payment data

Map payment data to existing Stripe Customers.

Copy page

Our standard process creates new customers alongside the payment method data from your previous provider. If you’ve been processing new transactions on Stripe during the migration, you might already have some customers in Stripe. Map imported payment data to these existing Stripe customers to avoid creating duplicates.

After you submit the migration intake form, reply in the same email thread with a CSV file that includes two columns:

  • old_customer_id: The unique identifier from your former processor.
  • stripe_customer_id: The corresponding Stripe customer ID in the cus_xxxx format.

To download a list of customers with their Stripe IDs:

  1. Go to the Customers section in the Stripe Dashboard.
  2. Filter the list based on your desired parameters.
  3. Click Export.
  4. Select the ID field for export.
  5. Export your list.

How it works

Shows the migration mapping process.

Example mapping file

old_customer_idstripe_customer_id
PSP_buyer_ID_1cus_NsKvEuOxdDP111
PSP_buyer_ID_2cus_Nrt6IryCjAK222
PSP_buyer_ID_3cus_OAiRfxde7Ya333

Customer data overwrite

Our current tooling preserves existing customer level data. Mapping doesn’t overwrite any information already present in the customer’s record. Rather, it appends data for any new cards that aren’t already included without altering the customer level information displayed in the Dashboard. If the data file flags a card as the default card, it overrides any previously set default cards in the Dashboard.

Was this page helpful?
YesNo
Need help? Contact Support.
Join our early access program.
Check out our changelog.
Questions? Contact Sales.
LLM? Read llms.txt.
Powered by Markdoc