Data Migration
migrates your existing customer data from your previous payment provider, such as Stripe, to your new account, ensuring your merchants can continue processing payments using previously saved payment methods.
Data migration overview
- Seamless data transfer: works closely with your payment provider to securely transfer payment and customer data.
- No fees: Data migrations are done at no cost.
- Quick turnaround: Migrations are typically completed within 3-5 business days once all required information is received and reviewed.
Pre-requisities
A merchant must be approved with before initiating the migration process.
Migration Process
To initiate the process:
- Provide Tilled's PCI Attestation of Compliance (AOC) to your payment provider. The current PCI AOC can be requested by emailing .
- Obtain Tilled's PGP public encryption key (opens in a new tab) for secure data transmission.
- After your payment provider prepares your data, they’ll email you encrypted instructions that Tilled needs in order to download your data securely. Please forward this email to [email protected] for decryption and data retrieval by Tilled's Migration team.
During the migration:
- Payment provider creates an encrypted file containing card details, email addresses, and any associated metadata. Payment history, subscriptions, and CVVs are not included in the migration.
- Payment provider securely transfers the file to Tilled.
- Tilled imports the data, enabling your merchants to process using the stored payment data right away.
FAQ
Are subscriptions set up as part of the data migration?
No, the import is limited to creating customers and payment methods.How are migration results communicated?
A result file is generated and sent to the provided email address. Results will include:
- Account ID
- Payment Method ID
- Customer ID
- Customer Vault ID - this ID is pulled from the imported file and generally provides a link to the prior processor system’s customer record
- Billing ID or Customer Vault ID - this ID is pulled from the imported file and generally provides a link to the prior processor system’s payment method or customer record
- First Name
- Last Name
- Payment Method Type
- Account Number Last Digits - last 2 for Debit, last 4 for Card
Why might a row from the imported CSV not be processed?
A row from the imported CSV might not be processed if it contains issues such as:
- Missing required information, like a ZIP code
- Invalid data, such as an expired card
Can a partner provide a file to update records after an import?
While our primary focus is on the creation of records rather than ongoing maintenance, the API does support updates to metadata, customer names, and similar fields. If you have a specific need for updating records via a file, reach out to for assistance.