> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dodopayments.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Subscription Migration to Dodo Payments
> Migrate existing subscribers and card payment methods from your current processor to Dodo Payments without interrupting billing.
A subscription migration transfers your existing subscribers and their payment methods from your current processor to Dodo Payments. Your customers won't need to re-enter payment details or experience any billing interruption.
We support migration for **card tokens only**. Apple Pay, Google Pay, and other wallet payment methods cannot be transferred between processors due to tokenization restrictions.
## What Is a Subscription Migration?
A subscription migration transfers your existing subscribers from your legacy payment processor to Dodo Payments, giving you a single source of truth for all your customer data. Without a migration, customers you've acquired to date remain in your legacy system, and only new customers would be visible in Dodo Payments.
## Migration Process Overview
The subscription migration process consists of three key parts:
1. **Payment method transfer** — Secure transfer of sensitive card data from your current processor
2. **Subscriber data transfer** — Export of customer details, subscription plans, and billing schedules
3. **Import and validation** — Unifying payment methods and subscriber data in Dodo Payments
To begin a subscription migration, contact our [support team](mailto:support@dodopayments.com). They will connect you with a dedicated Solutions Engineer who will guide you through the entire process.
## Requirements
Before initiating a migration, ensure you meet the following requirements:
* **PCI DSS compliance**: Your current processor must be PCI DSS Level 1 compliant and able to export encrypted card data. Dodo Payments is PCI DSS Level 1 compliant. View our [Attestation of Compliance (AOC)](https://pub-2a89184e4c954b599464449d23f506bb.r2.dev/dodo-payments-pci-dss-aoc.pdf) to share with your processor.
* **Dodo Payments integration**: Complete your integration and route all new customers to Dodo Payments checkout before migrating. This prevents data inconsistencies.
* **Data access authorization**: You have permission to export customer and payment data from your current processor. This typically requires account owner verification and completion of their security steps.
## Step-by-Step Migration Guide
Contact your current payment processor's support team and submit a formal request for a complete export of your customer card tokens.
You will need to:
* Provide verification of your identity and authorization
* Request they encrypt the export using Dodo Payments' PGP public key (provided below)
* Ask them to transfer the encrypted file directly to our secure SFTP server
Your Solutions Engineer will provide the SFTP credentials to share with your current processor. On average, this process takes around **2 weeks**, although timing varies depending on your current processor's policies and response times.
While the payment method transfer is in progress, export your subscriber data from your legacy system. Your Solutions Engineer will provide a CSV template and guide you through the required fields.
### Required Subscriber Data
| Field | Description |
| - | - |
| `customer_id` | The customer ID from your current processor (Dodo Payments assigns its own `cus_` ID on import) |
| `email` | Customer's email address |
| `name` | Customer's full name |
| `country` | Two-letter country code (ISO 3166-1 alpha-2) |
| `product_id` | The Dodo Payments product the subscription maps to. Its price, currency, and billing interval apply |
| `quantity` | Subscription quantity |
| `next_billing_date` | Next scheduled billing date (ISO 8601) |
| `card_token` | Unique token from your current processor |
For Paddle migrations, the `card_token` field is critical: it's used to match subscriber records with their payment methods during import. Ensure this matches exactly with the token in the payment method export.
### Sample Data Format
```csv theme={null}
customer_id,email,name,country,product_id,quantity,next_billing_date,card_token
ctm_01abc123,jane.doe@example.com,Jane Doe,US,pdt_pro_monthly,1,2025-01-15T00:00:00Z,tok_xyz789
```
Before the import date, our team will:
* Verify file integrity and encryption of the payment method data
* Validate your subscriber CSV for correct formatting
* Run a test import in Test Mode
* Identify and resolve any data mapping issues
You'll receive a validation report confirming everything is ready for the production import.
On the agreed import date, our engineering team will:
1. Import the payment method data into our PCI-compliant Card Vault
2. Import your subscriber data
3. Match subscribers to their payment methods using the card tokens
4. Activate all migrated subscriptions
Typical processing time is **2-3 business days** for standard migrations, depending on the volume of subscribers.
After the import completes, you'll receive:
* A comprehensive migration report
* A CSV mapping your old subscription IDs to new Dodo Payments IDs
* Access to all migrated customers in your Dodo Payments dashboard
We recommend:
* Verifying a sample of migrated subscriptions in your dashboard
* Testing a few subscription renewals in Test Mode
* Updating your internal database references with the new IDs
* Running parallel monitoring for the first billing cycle
## Migratable Data
The following data can be transferred during a subscription migration:
| Data type | Supported | Notes |
| - | - | - |
| Credit/debit card numbers | ✅ | Encrypted via PGP |
| Card expiration dates | ✅ | |
| Cardholder names | ✅ | |
| Billing addresses | ✅ | |
| Customer email addresses | ✅ | |
| Customer metadata | ✅ | Custom key-value pairs |
| Subscription details | ✅ | Plan, amount, interval |
| Apple Pay tokens | ❌ | Cannot be transferred |
| Google Pay tokens | ❌ | Cannot be transferred |
| Other wallet tokens | ❌ | Cannot be transferred |
| Payment history | ❌ | Export from your current processor |
Payment history and transaction records cannot be migrated. We recommend exporting this data from your current processor for your records before completing the transition.
## PGP Encryption
For maximum security when transferring sensitive card data, all files **must** be encrypted using our PGP public key. This provides an additional layer of protection beyond transport-level encryption.
Share this key with your current payment processor for encrypting the card data export:
```
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQINBGflFWEBEADA8IaeXNc9ekoyWGH6TBi3PvazDTXH9MeAIcq8tcXPjr+aDTA7
QE0oJbnH+Zi6nP6Mh20c4bftzC890/QJmk6shdgpQuCd/80yC1TT5tyqKDV517WQ
B7A8CmbonuZ//jS+jWrekpbLFMzoro1ZkeCRDNbhF3KSrMv1UOugBHPAchtkTur8
2k+HtIFKVW8xQ3/nrnKGeNWdHMp3y6yATjXm0E2y9Oq83CQ1TkwwB+MI0Y/uZaXv
3016pOos3lQFXqVAvShDRzMXxvPHc902QS47v0gSj5wsVWv3g5QP/TlAE6Pvua18
78xoROo9RLwovMmX372JeZdqKgIV+BmxlOrGCDcNOY4Flz+NRJuKbVk0UmD8f1tW
NL5x/r36ZNnBbzohqcwp5dktiRn0MDHUsvv8StOkbFqQ+HyYSzoO1dRYGkz5bkfI
urv4hd26I4rdu8GTpEaBcd0rx1NcNT2lbqrcTE7rux3c3Vf1QD6lSj+VbJBxxyxO
+fgeoVNpAi4Zfyls+VYCRolVHxxdjh/Zu6iAUrpubpgBxoxwzF3vMVWDPvZahUxY
gt340eRr6KQUpI2TK4iNhTzc4CpYP/eKyC8TavHzpuGap0f7ojNaD1yjPxKJ9HFF
eFde7jtoglvGrdW/GnoTVBFdN4wdcrJ6+Xthlqk5n0CZLKxZzCsnJ+Y00wARAQAB
tFlEb2RvIFBheW1lbnRzIEltcG9ydCBLZXkgKEltcG9ydCBrZXkgZm9yIGNhcmQg
dG9rZW4gbWlncmF0aW9uKSA8cHQtdGVhbUBkb2RvcGF5bWVudHMuY29tPokCVwQT
AQgAQRYhBAfnpp8sSFvzQCZA9mOB38/zSlnMBQJn5RVhAhsDBQkJZgGABQsJCAcC
AiICBhUKCQgLAgQWAgMBAh4HAheAAAoJEGOB38/zSlnMLm4QAK1sQxraYnV4OC9l
G0LNUDRKsayJ3+5uW6gbD72NhQ1Q7GpD6J1kmoXO95ZMSV4Ev+PAdBHVnhbl+LTk
JBZTrVszeZfmAr2D0HTdBsqlB8uUISXaffL/a0POWTLRdVzHJbTPtC23SHjW8XFu
0ixomJxnIXu1iBccEPJTWpjYQbecfK6xMbHYvLQYBCLBWbDfr7hJ3ubnF8izo4W+
cxYmFS5A4lKs6PHC+MlikFHtKKhDaKT+Zc5c5utcGpPEFUw1vxvQkgabOie6/ufc
EAfzHaFklDvyovfKJ3eOrTRlOG8T0TmoccxjTtx4vboaTcnKoANO0p1G5esjkAWU
2Bpa/hTaW3YvKBlHEPovm+E4c7OieHIvw3+BS7uyWOmNHgzJcAEVkbJAvRl9X1lQ
LzcOqBIVMyLF5zswRBHtCWHuYsolIO8zMKHmYKV52jR7OkGcZ5ekaqIKVsOmpDCk
Rn7RWubhglOC6e+CNK+2LEQALpDLx05F4uUSmbo0KvQtgnXJHsVsesaO/CVxvdOw
nWv3MyZbhN+EGCKbO3eoTkaM7EHRPEsHa04a+T+TPFel1B7VlTdBikoyNQxyh4a2
V/ERoKi1qI9DS158lkPkZt90PLhPMVyOFTmTt8ZbZhp1TndmIterWGlYFz8yXb7A
BDeo0Xmu2rmuoG7kEihSwt0UmfMSuQINBGflFWEBEACyXdG9SjXd7dRoJ5bcs64A
Cxea1NZ90x4NWdx0lTy8ruHBSzl2SYDGhDbAAOhVTxZHr1UeDfPBp/urYiENsFeA
Fx2V4Pt2Jj0oBJ6IIHnf1X0U+T6JzVYraaQBHUjXsq4GVoD0bWydQwE6+PSOOZ8R
d7GlsdDl0lM38krkN84BRI/OEfLJaUKFAN9COBnna3bpUwhrvk2o05ItYK/CPoEp
lQAI5mvO7x+kPSsWUCW905TrQuvYuJQvhCZN/2NMn7X5NzhVLLnPW+hyBfkjkWWm
8GQoH54AADQOKAczkXuSUuLwji+TA2ImAw9FI/S5cIjxG3z4PaAg7zVeZEpjjTWN
7QQXEMvzDLLXRSjXHsmtWmg//pgvkTxyuzPbNKK7KY9Q+Xyqb0bP5UQKrZ9nRn4l
MMZjC7Kj7eeMv3g/V6wH60Sle0/XW1zSX0djay/Hf99eXcfntlSW0DB2pn9fa8+W
vdmASrLwcYyGjIROxzHIW9uUs4kdJqWatzfT/0uWWwaLayEkd/lCzITn61UAYwVt
YIhY5u9lH0ZuQsxOm267TZrrgDbN9h+z5OVLxW9ylhvXZhMa0w87z8ZTp9wCycki
CNCM1dP0N+lxIPnDu3MztK8u/yelcKpruY5L+gMmVcyDPSYUHDO7g764IdUmSPh4
VfIeXAsj2r5usa4/+OcxuQARAQABiQI8BBgBCAAmFiEEB+emnyxIW/NAJkD2Y4Hf
z/NKWcwFAmflFWECGwwFCQlmAYAACgkQY4Hfz/NKWcxoIA//edJGWP4Pu70M5IlQ
rLRhi0+hKe0l5VrR1XYcr0EA4qiRQIouab4QvHoxNpn5RGQ+C2agwraiIwIP/nqR
Wz1arWpea8BuSeAJCI0uVQURGexB9ZIJ4oiz8itAiHyjW6x+B4zC9RKe3xGO8KIt
FhtGMYGP+8bZyOUnIU9ZqO+mxHc/wnwCeICzE5TpITrEERbXh0XZJJCLotpss8o8
4F0Lb/9VwObCEdxpC6IkKW9GF5WJjmycfdcojaEr26qNSj1KsKRww7ukoVthD4aT
KRM0j3X0UFNz522hBCV/+0+cGMSc5lIRzE+gsXM8vpCW3rmWZj9pMyL5r/RH1FFL
9N3nFvfjoiuEqQ/DRy3jdwCHXEijjo5ym1KU9AGuo42deI0nrpvzXYSSahKMOb0/
PbF4YlrtSbXwhIsBfCUX6njvNomu2u4wDs7gv7gyimyetMZ8EwJ3aGvXlD4kHh15
tIo5NVXXLfslGtoL+27iW4nmoAxV1lOU2c2Wei+lXEc7t6JgeI0NTdqBnYTNHsOZ
f+dti4KGC2Y+6QKhCgvTFHdHpBJj9DzG49C+4E5ZZL3bNdsU5eXaIuJf/KW+eVQB
EZgHVgBRCqwrDD6SpkOT2lzNxfKI5rBV+WCT+hbu83hk2Pd1K7N3JQs1fVFffF37
1OSDhXaPYtJnVApUzaCrC5PJCXU=
=nHcw
-----END PGP PUBLIC KEY BLOCK-----
```
## Timeline Expectations
| Phase | Duration |
| - | - |
| Initial setup and planning | 1-2 days |
| Payment method transfer | \~2 weeks |
| Subscriber data preparation | 3-5 days (parallel) |
| Validation and testing | 2-3 days |
| Production import | 2-3 business days |
| Post-migration verification | 1-2 days |
The total migration typically takes **3-4 weeks** from start to finish. Starting your subscriber data preparation while the payment method transfer is in progress helps minimize the overall timeline.
## Get Started
Ready to migrate your subscriptions to Dodo Payments? Contact our team to begin the process:
Reach out to start your migration and get connected with a Solutions Engineer.
Explore our API to understand how subscriptions work in Dodo Payments.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.