Migrate a tokenized PAN vault to a new payment processor while preserving stored card data portability

Steps

1. Engage both your source and destination payment processors to understand their token portability or PAN export/import processes; note that raw PAN export is only available under strict PCI DSS controls
2. Request a token-to-PAN export from your source processor through their PCI-compliant data export service; ensure the export is encrypted and transferred via a secure channel to a PCI-DSS-compliant intermediate environment
3. In the intermediate PCI environment, re-tokenize each exported PAN against the destination processor's tokenization vault API, capturing the new token reference for each card
4. Build a mapping table from old tokens to new tokens in your application database; deploy a code change that queries the new token for any payment method older than the migration cutover date
5. Run a parallel period where both old and new tokens are valid; validate a sample of re-tokenized cards by running zero-dollar verification authorizations against the new processor
6. After validation, decommission the old token vault and remove the old token references from your database