# Token Migration

### SensePass Token Migration Process

The SensePass token migration process allows merchants to securely transfer customer payment information for tokenization. 

This process involves the merchant sending a structured Excel file, which contains sensitive customer data such as credit card numbers, expiration dates, and other relevant information. 

The process can be completed in two distinct workflows:

**Workflow 1: Generating New Tokens**

1. **File Submission**: The merchant submits an Excel file following the prescribed format available on our documentation page. This file should include all required customer data fields.
2. **Tokenization by SensePass**: Upon receiving the file, SensePass processes the data by generating new, unique tokens for each credit card entry. These tokens are securely mapped to the original payment information within the SensePass system.
3. **File Return**: SensePass returns the processed file to the merchant. This file will contain the newly generated tokens, replacing the original credit card numbers, ensuring that sensitive data is securely handled.

**Workflow 2: Using Merchant-Specified Tokens**

1. **File Submission**: The merchant submits an Excel file in the standard format, including the existing tokens that they wish to retain. The file should also include the corresponding credit card numbers and other required customer data fields.
2. **Token Matching by SensePass**: SensePass processes the file by matching the provided tokens to the corresponding payment information within the system. This allows for the creation of identical tokens within the SensePass environment, ensuring seamless continuity for the merchant.
3. **File Return**: After processing, SensePass returns the file to the merchant with the specified tokens mapped to the original data, ensuring that the migration is completed without altering the token structure.

#### Excel File Template

{% file src="/files/hGDgh2Bp3j5roQ7YN1I4" %}

#### Security and Compliance

SensePass follows stringent security protocols to ensure the safe handling of sensitive customer information throughout the token migration process.

 All data is encrypted during transfer and processing, adhering to SOC 2 and PCI DSS standards.


---

# Agent Instructions: 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:

```
GET https://docs.sensepass.com/sensepay/transaction-api/other-flows/token-migration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.