Services in this article may not be included in every Funraise plan.
This article covers the process to migrate active recurring subscriptions to Funraise. You can migrate your recurring donation subscriptions to Funraise from another platform in many cases, but not all. Our ability to migrate subscription data is dependent on your previous system and payment processor. The process will require coordination between Funraise, you, and your previous payments platform.
To get started with a recurring subscription migration, create a new ticket with our support team by emailing support@funraise.org.
You're responsible for your migration
While our award-winning support team is available to guide your way, migrations can be a challenging process if not well organized. The state of your data, your team's resources, and your previous system will determine your migration experience. Funraise does not analyze, structure, or organize your data - this is your data and you know it better than anyone. You are the leader of your migration.
Required data
Payment method data (the actual credit card information). Your current payment service will securely share this data with our vaulting partner, Spreedly.
Subscription details: Information about the supporter, amounts, frequency, payment date, etc. for each subscription. You will export this data from your previous platform and enter it into a template Google Sheet that we provide.
Step-by-step instructions
Step 1
Organization
Create a new ticket with our support team by emailing support@funraise.org and let us know you're ready to begin a recurring migration. We'll respond with next steps and use this ticket thread to communicate throughout the migration process.
Step 2
Organization
Contact your payment service to let them know that you want to start the process of migrating your recurring subscriptions.
Your previous payment service will follow these instructions to share encrypted payment data with our secure payment vault, Spreedly.
Use the following message template when reaching out to your previous payment provider:
Hi previous platform,
We are moving to a new payments platform (Funraise) and will be migrating our recurring donor payment data. Funraise uses Spreedly, a PCI Level 1 payment vault, to securely store payment methods. You can find Spreedly's AOC and latest scan here: https://spreedly.com/pci
Please export all our recurring payment methods to Spreedly. You can review instructions to securely share encrypted payment data with Spreedly via SFTP and Spreedly's PGP key here: http://help.funraise.io/en/articles/4115679-data-migration-active-recurring-subscriptions#h_31d9c26f61
When the encrypted payment data is ready to share, please email support@funraise.org with the following:
Instructions and credentials to access the encrypted payment data
The name of my organization
Funraise will share these details with Spreedly and continue the process.
Thank You!
Step 3
Previous payment platform
Securely shares payment method data with our vaulting service (Spreedly) using these instructions
Step 4
Organization
Confirm with previous payment service when subscriptions will stop charging in the previous environment
Export subscription data from your previous system and transfer exported subscription data to the
Funraise Subscription Migration Template. This is a template Google Sheet, which we'll share with you.
Funraise
Help match tokenized payment methods to subscription data
Finalize subscription data import file for organization approval
Step 5
Organization
Provide final approval for import
Funraise
Import final subscription data
Notes
Migration timeframes
The recurring migration process can take a few weeks to a few months. It entirely depends on the quality of your data and the payment platform you're migrating from.
Timing is important. You'll need to coordinate the cancellation date of your subscriptions in your previous payments platform and the import of subscriptions into Funraise to ensure no payments are missed or duplicated.
Migration costs
In most case, paid plans include a single recurring migration (of many recurring subscriptions records and payment methods). Additional charges will apply after the first migration or if you are migrating subscriptions from multiple sources.
Possibility of new declined payments
A recurring subscription migration will change the gateway that is processing your payments which may cause card networks to fail some payments because the charge requests is coming from a new processor. Generally, declines of this nature are not common, but are possible.
⚠️ With Funraise Payments powered by Stripe you will have access to Stripe Radar rules that can be activated to verify the address provided with credit card payments to help prevent fraud. If your previous processor was not verifying address information for each charge, it is possible to have new declines if Address verification (AVS) is activated.
Some payment methods may fail to import
It is possible that there will be some payment methods that will not be successfully imported to the vaulting service. Possible reasons include:
Payment method/subscription was created after the request for export was sent to the previous payment processor
Data provided by the previous payment processor was insufficient to be imported into vaulting service
Payment method data has errors, such as invalid expiration dates.
While it is possible to import a subscription connected to a payment method with errors, the subscription will fail to charge. We recommend excluding these records from the import process and reaching out to those supporters directly to create new subscriptions in Funraise.
Instructions for previous payments platform
Spreedly is Funraise's vaulting partner. As a previous payments platform, please prepare data to share with Spreedly following the instructions described below.
Once the data is encrypted and ready to be shared, please email support@funraise.org with the instructions and credentials to access the encrypted payment data and the name of the organization that requested the export. Funraise will share these details with Spreedly and continue the process on our end.
Data Format
Spreedly requires incoming data to be in CSV or JSON format. Data should be GPG-encrypted and transferred securely via SFTP (described below).
For credit cards the following data is required:
External ID
Full name
Card number
Expiration month
Expiration year
The following data is helpful but optional:
email
address1
address2
city
state
zip
For ACH payment methods, the following data is required:
First name
Last name
Bank routing number
Bank account number
File Transfer
Spreedly accepts CSV or JSON formatted migration file transfer via SFTP.
The previous payments platform will create their own SFTP configured to the standard SFTP port (22). Credentials should be encrypted to Spreedly’s PGP public key.
If the previous payments platform prefers for Spreedly to authenticate via SSH-RSA key instead of sending encrypted credentials, please use the key listed below.
Spreedly SSH-RSA Public Key
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDKX5MrQBLsthC2qSMhwOut1VGWkkr5EqxLNkZmMwpkNKQTZDXS6zD/7W9nI9xeoSXovZhpbgdRxVZs1gWTW9e5uGA5FQffDm12cmnvtnzheSCak830C3c0dZskcJnybhMbOxdIJkN9GpliuKUUA/uQxj8m+E5GcyYNQEb21dKqKzj7UO3qnfF1KlAJJHx4aiyc7gDQJ4uulVbKATyxKqY525WffqZFAASTUoTiskU/i30iXZk8MC6EQQuxY+hsRGv4ugqt0W2PlVGKi1uOCgPjc7V3MU7HzOpBP60ppI4EH/4M154bKD6BnZGtQflSedhYNnwdQshF5mMehVzB7/bB
PGP
Data shared with Spreedly must be encrypted using Spreedly's public key. If you’re not familiar with PGP, visit GnuPG and start by importing a public key.