> For the complete documentation index, see [llms.txt](https://docs.sensepass.com/sensepay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sensepass.com/sensepay/additional-services/token-migration.md).

# Token migration

Move your customers' saved cards from another payment provider to SensePass.

Moving to SensePass from another payment provider? Token migration moves your customers' saved cards to SensePass, so you can keep charging them without asking them to enter their card again.

### Choose how your tokens are migrated

| Option           | What you send                                                                                | What you get back                                                                           |
| ---------------- | -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| New tokens       | An Excel file with the card data and other required customer fields                          | The same file with a new SensePass token for each card, in place of the card number         |
| Keep your tokens | An Excel file with your existing tokens, the matching card numbers and other required fields | The file with your tokens mapped to the cards in SensePass. Your token values do not change |

### How it works

| Step | Who       | Action                                                                              |
| ---- | --------- | ----------------------------------------------------------------------------------- |
| 1    | You       | Ask your SensePass account manager or <support@sensepass.com> for a token migration |
| 2    | You       | Fill in the SensePass Excel template, one card per row                              |
| 3    | You       | Send the file to SensePass using the secure transfer method SensePass gives you     |
| 4    | SensePass | Creates or maps the tokens                                                          |
| 5    | SensePass | Returns the file with the tokens                                                    |

#### Excel template

Download the template and fill in one card per row.

{% file src="/files/hGDgh2Bp3j5roQ7YN1I4" %}
Excel file template for token migration
{% endfile %}

{% hint style="danger" %}
**Important:** The file contains full card numbers. Never send it by regular email or chat. Use only the secure method SensePass gives you.
{% endhint %}

SensePass encrypts the data in transfer and processing, following SOC 2 and PCI DSS standards.

### Timeline

SensePass confirms the timeline with you when you request the migration.

### Technical details

For the technical description of both workflows, see [Token Migration](https://docs.sensepass.com/sensepay/developers/transaction-api/other-flows/token-migration) in the Developers section.

Questions? Contact <support@sensepass.com> or your SensePass account manager.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sensepass.com/sensepay/additional-services/token-migration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
