> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integration-guide/account-management/data-migration/import-data-to-hyperswitch.md).
# Data Migration from PSP to Hyperswitch
We help you with smooth migration from your current payment processor, ensuring uninterrupted business operations.
### Performing the import data process:
1. Merchant initiates a request to our team for Data import.
2. We will share our PCI Attestation of Compliance (AoC) certificate to Merchant.
3. Merchant requests a data export (for both customer records and associated payment data) from their current payment processor, by providing Juspay Hyperswitch's PCI AoC certificate.
4. We will provide our public PGP key for Merchant's current payment processor to encrypt their export data. (see below)
5. An encrypted CSV file containing all the export data needs to be sent through SFTP by Merchant's current payment processor.
6. We will import the data.
7. Post migration of data, we will send an updated customer-payment method reference IDs to Merchant.
### Public PGP Key:
```
Created: 30 July 2026 at 19:03 IST
Expires: Does not expire
Key ID: C2BF6CD3
Length: 255
Algorithm: Ed25519
Fingerprint: C92D CC09 533D AA54 E6FA E97A AD01 848A C2BF 6CD3
```
```
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEamtSxBYJKwYBBAHaRw8BAQdANDBtqn7GGvGZRoON7AAts31PAyVIBeXqp0f2
3vuMnZ60GmRlZXBhbnNodS5iYW5zYWxAanVzcGF5LmluiK8EExYKAFcWIQTJLcwJ
Uz2qVOb66XqtAYSKwr9s0wUCamtSxBsUgAAAAAAEAA5tYW51MiwyLjUrMS4xMiww
LDMCGwMFCwkIBwICIgIGFQoJCAsCBBYCAwECHgcCF4AACgkQrQGEisK/bNNu7wD/
UtqrESnztJTMqEYPCaYXybxz7a7POYngKJ+k/SbIRAEBALXLh55EKJmSSDja6aNl
IGRplHloATEcuxs5cc888PkPuDgEamtSxBIKKwYBBAGXVQEFAQEHQBaAMirUx2a8
b94DeUFJLGltEOYGNdt+wn06TsIqolthAwEIB4iUBBgWCgA8FiEEyS3MCVM9qlTm
+ul6rQGEisK/bNMFAmprUsQbFIAAAAAABAAObWFudTIsMi41KzEuMTIsMCwzAhsM
AAoJEK0BhIrCv2zTlHMBAIUhkv+CsX8ZB/d330CJipZNJo93hV0DM095tRBWtniR
AP4z/ETdOlql10Sb6884Gm2KJqVqvkKZvEtivgq2kiIZAA==
=RQay
-----END PGP PUBLIC KEY BLOCK-----
```
### Import file format:
The CSV file for import should be formatted in accordance with the following requirements:
* The first line contains the names of the fields.
* Each subsequent line should contain the fields for a single record.
* Delimit rows by a single newline character `\n (not \r\n)`.
* Delimit columns by `,`
* Leave empty fields entirely empty (no character in between delimiters). You must not denote a missing field with NULL, N/A, or any other value.
* Fields can't contain comma, newline characters `(\r or \n or ,)` within a field.
* Example of what to avoid: `1st Ave\nApt 1`
* All rows must have the same number of columns.
* Field names and values are case-sensitive.
* Multi-line fields are not allowed.
* Save the file in UTF-8 format (to support non-western characters).
* Encrypt the file using the public PGP key provided by Juspay Hyperswitch.
### To import card data:
#### Required fields:
| **Field** | **Description** |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| card\_number | Primary Account Number (PAN) of the customer card |
| card\_expiry\_month | Card expiry month |
| card\_expiry\_year | Card expiry year |
| payment\_instrument\_id | Unique reference ID of payment method saved (PSP token)
Note: This is required for mapping to Hyperswitch payment\_method\_id.
|
| original\_network\_transaction\_id | Original Transaction ID of the first transaction where the customer signed up for recurring payments. For eg. Visa - Visa Transaction ID, Mastercard - Mastercard Trace ID.
Note: This is only required for connector agnostic MIT
|
#### Optional fields:
Note: Billing details are mandatorily required if AVS (Address verification Service) check is enabled.
| **Field** | **Description** |
| ----------------------------- | ------------------------------------------------------------- |
| name | Name of the customer |
| email | Email id of the customer |
| payment\_method | Payment method used by customer (Eg: card - for cards import) |
| payment\_method\_type | Payment method type used by the customer (eg: credit / debit) |
| card\_scheme | Card network (Eg: Visa, Mastercard, American Express) |
| phone | Customer mobile number |
| phone\_country\_code | Country code of Customer mobile number |
| billing\_address\_first\_name | Customer First Name for billing address |
| billing\_address\_last\_name | Customer Last Name for billing address |
| billing\_email | Billing email id of the customer |
| billing\_address\_line1 | Street Name/Address Line 1 of the billing address |
| billing\_address\_line2 | Locality Name/Address Line 2 of the billing address |
| billing\_address\_city | City of the billing address |
| billing\_address\_state | State of the billing address |
| billing\_address\_zip | Postal code of the billing address |
| billing\_address\_country | Country of the billing address |
{% hint style="info" %}
To import other payment methods like SEPA, ACH, Paypal, Klarna, kindly reach out to
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.hyperswitch.io/integration-guide/account-management/data-migration/import-data-to-hyperswitch.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.