# Specific considerations for data migrations

The following sections provide additional information only and do not cover the complete set of required data for collecting payments through a given payment processor.

For a complete overview of required data, please refer to our [data quality rules Google Sheet](https://docs.google.com/spreadsheets/d/1HiIp3Cy_uXz9Y3sSFcId0rG-y134WiatLW1RXTYc3Yw/edit?usp=sharing).

### Adyen migrations

| Target Object | Target Field | PSP data | Comments |
|  --- | --- | --- | --- |
| Mandate | `adph__Token__c` | Token | Specific field on Mandate for Adyen tokens |


### Axerve migrations

| Target Object | Target Field | PSP data | Comments |
|  --- | --- | --- | --- |
| Mandate | `gffd__Bank_Transaction_Id__c` | Bank Transaction Id | Specific field for Axerve |
| Mandate | `gffd__MOTO__c` | MOTO (true /false) | Specific field for Axerve |
| Mandate | `gffd__Eligible_for_Token_Refresh__c` | [Eligible for Token Refresh](/docs/payment-processors/axerve#refresh-expired-credit-cards) (true /false) | Specific field for Axerve |
| Payment Profile | `gffd__Target_To_Refresh_Token__c` | Target to Refresh Token | Specific field for Axerve |


### Authorize.net migrations

| Target Object | Target Field | PSP data | Comments |
|  --- | --- | --- | --- |
| Mandate | `cpm__Reference__c` | Customer Payment Profile Id | Can be found from the Authorize.net Customer Information Manager or [using their API](https://developer.authorize.net/api/reference/index.html#customer-profiles-get-customer-payment-profile). |
| Mandate | `cpm__External_Customer_Id__c` | Customer Profile Id | Ditto above |
| Mandate | `cpm__Country_PL__c` | Shipping address country code | 2-letter ISO Code, required if you use [IP address fraud detection](/docs/payment-processors/authorize-net#ip-address-fraud-detection) |
| Payment Profile | `aufd__Customer_Ip__c` | IP address | Required if you use [IP address fraud detection](/docs/payment-processors/authorize-net#ip-address-fraud-detection) |


### Buckaroo

For SEPA Direct Debit migrations, special attention is needed in the area of mandate reference handling. There are two ways to manage the  [Buckaroo prefix](https://docs.buckaroo.io/docs/prefix).

| Target Object | Target Field | PSP data | Comments |
|  --- | --- | --- | --- |
| Mandate | `cpm__Custom_Reference__c` | Prefix + Mandate | If the entire Buckaroo mandate reference, including prefix, is migrated as one value, the value should be added to this field. |
| Mandate | `cpm__Prefix__c` | Prefix | If the prefix is not included in migrated mandate references, add the prefix to this field. |


### Checkout.com migrations

| Target Object | Target Field | PSP data | Comments |
|  --- | --- | --- | --- |
| Payment Profile | `ccph__Fingerprint__c` | Fingerprint | Specific field for Checkout.com |


### GoCardless migrations

| Target Object | Target Field | PSP data | Comments |
|  --- | --- | --- | --- |
| Contact | `gcf__GoCardless_Customer_Id__c` | GoCardless Customer Id | Needed only if you use the Manual Direct Debit component for existing customers |
| Mandate | `cpm__Custom_Reference__c` | GoCardless Mandate Id | Example: MD000EHA3S6AT7 |
| Payment Profile | N/A | N/A | If you want to use custom notifications with GoCardless Pro, you need to create payment profiles with a Bank Name to get all the required data into Salesforce. |


### Mollie migrations

| Target Object | Target Field | PSP data | Comments |
|  --- | --- | --- | --- |
| Contact | `moph__Mollie_Customer_Id__c` | Mollie Customer Id | Specific field for Mollie |
| Mandate | `cpm__Reference__c` | Mollie Mandate id | Example: mdt_4tCvx2TJEz |


### PayPal migrations

| Target Object | Target Field | PSP data | Comments |
|  --- | --- | --- | --- |
| Mandate | `cpm__Custom_Reference__c` | Payer | Billing Agreement ID with PayPal, e.g. B-8G591046VR212925B. This overwrites the Mandate Id. |


### Redsys migrations

| Target Object | Target Field | PSP data | Comments |
|  --- | --- | --- | --- |
| Mandate | `cpm__Reference__c` | DS_MERCHANT_IDENTIFIER | e.g.  01903f9b923895767228066924f23b5892e88fdb |


### Saferpay migrations

| Target Object | Target Field | PSP data | Comments |
|  --- | --- | --- | --- |
| Mandate | `sford__Is_Alias__c` | Credit card reference | Is Alias must be true for migrated recurring credit card transactions to allow further collections |
| Mandate | `cpm__Reference__c` | (Card) Alias | The authorization token from Saferpay for a recurring payment (not set up through FinDock). |


### Access PaySuite (SmartDebit) migrations

| Target Object | Target Field | PSP data | Comments |
|  --- | --- | --- | --- |
| Mandate | `cpm__Custom_Reference__c` | Payer | Bacs reference with SmartDebit, e.g. UCOSHX7. This overwrites the Mandate Id. |


### Stripe migrations

| Target Object | Target Field | PSP data | Comments |
|  --- | --- | --- | --- |
| Contact | `phstr__Stripe_Customer_Id__c` | Stripe Customer Id | Specific field for Stripe, e.g. cus_1234absced |
| Mandate | `cpm__Custom_Reference__c` | Mandate Id | Mandate Id specifically for PAD direct debits, e.g. mandate_1X2xxXX... |
| Mandate | `cpm__Reference__c` | Stripe Customer Id | Reference to Stripe customer Id, e.g. cus_1234absced |
| Mandate | `phstr__Payment_Method_Id__c` | Stripe Payment Method Id | Specific field for Stripe, e.g. pm_123sdf3dsf3 or card_123w213sf |


#### Further Stripe migration requirements

If you are going to use MOTO payments, make sure you migrate the [data needed for credit card re-use](/docs/payments/configuring-findock-moto#additional-fields-from-payment-profile).

If you are moving [SEPA Direct Debit payments](https://stripe.com/docs/payments/sepa-debit) to FinDock, you need to get the SEPA mandate [Stripe Payment Method Id](https://stripe.com/docs/api/charges/object#charge_object-payment_method_details-sepa_debit-mandate) into FinDock. If the field is not included in reports, it can be queried via the [Stripe API](https://stripe.com/docs/api/mandates/retrieve).

### Worldpay

| Target Object | Target Field | PSP data | Comments |
|  --- | --- | --- | --- |
| Mandate | `cpm__External_Customer_Id__c` | Shopper Id | Specific field for PSP payer Id |
| Mandate | `cpm__Custom_Reference__c` | Token | Card token is also used for `cpm__Unique_Mandate_Id__c`, `cpm__Mandate_ID__c` and `cpm__Reference__c` |


### Vipps

| Target Object | Target Field | PSP data | Comments |
|  --- | --- | --- | --- |
| Mandate | `cpm__Custom_Reference__c` | Agreement ID | E.g. agr_123456 |


### FinDock as processor

#### Autogiro migrations

Before you start migrating existing Autogiro recurring payments to FinDock, please first assess the types of payment collection in use. Autogiro supports two: automatic recurring collection based on a single payment order to initiate collection, and recurring collection based on recurring payment collection instructions. FinDock only supports the latter.

If you have any automatic collection in use, these orders need to be cancelled as part of the FinDock migration. We recommend proceeding in batches, cancelling a small set of orders, migrating those, and restarting collection through FinDock. Once your process is confirmed to work, you should gradually move remaining automated orders to FinDock, for instance, in batches of increasing size.

When it comes to migrating Autogiro data, in addition to the general migration guidance noted above, special handling of custom mandate Id values may be needed.  Payer numbers (mandate Ids) in FinDock must be filled with leading zeros to match the expected 16-digit length. If, for example, the payer’s Bankgiro number is migrated and used for the mandate Id, the value needs to be with leading zeroes.

Also, note that you need to use the BBAN record type and page layout for Payment Profile for Autogiro payer bank details. Start by selecting Sweden from the country picklist. This will show you which fields should be populated for Swedish banks accounts.

#### AvtaleGiro migrations

For mapping details, please see [Migrating AvtaleGiro Agreements](/docs/payment-processors/migrating-avtalegiro-agreements)

#### Bacs migrations

| Target Object | Target Field | Bacs data | Comments |
|  --- | --- | --- | --- |
| Mandate | `cpm__Date_Signed__c` | Date | FinDock automatically populates this for new mandates |


#### SEPA migrations

| Target Object | Target Field | SEPA data | Comments |
|  --- | --- | --- | --- |
| Mandate | `cpm__Last_Used__c` | Date | Needs to be populated for recurring, otherwise the next installment generated by FinDock will be first automatically. |
| Mandate | `cpm__Prefix__c` | Text | Only populate if you have a prefix, and no Custom Reference value is used on the record. |
| Payment Profile | (address fields) | N/A | If you have UK payers for SEPA, you need to populate the address fields: Street, Housename Or Number, Zipcode, City, and Country. |