Legacy payment processor to Stripe
Learn how to migrate recurring plans from your legacy payment processor to Stripe.
The general workflow and timeline for this type of migration can be illustrated as follows:
If you are migrating from a legacy payment processor, please follow the steps below to begin this process.
1. Initiate the process with Stripe - Click here to submit a data migration request with Stripe and use the image below as a guide. Once submitted, you will receive a confirmation email from Stripe, usually within one business day. Since you are coming from a different payment gateway, You MUST submit one request to Stripe. This request will inform Stripe you are approving the incoming payment tokens:
2. Initiate the process with the legacy processor - You need to send a request to your legacy processor asking them to transfer all payment tokens to Stripe. Here is a template you can use:
TO: Legacy Processor Support Email
3. After the payment tokens have been transferred to your Stripe account, export the details of the recurring plans you want to migrate. This information can be exported from the platform managing your recurring plans. This can be your CRM, your payment processor or a third-party merchant processor. The data should include name, email, the last donation date and time, and any unique identifiers.
4. Format the data to match Fundraise Up's required import format - In order for us to use the data, it needs to be formatted for our migration development team. Click here to see the instructions and to get a sample template you can use. Please keep the existing formatting and make sure that:
- You thoroughly reviewed the crucial information at the start of the sheet, as well as the specific annotations accompanying each column.
- Stripe IDs / Billing Agreement IDs match their related plans.
- The last donation date is aligned with the donation frequency, ensuring that it falls within a reasonable time frame (e.g., for a Monthly donation frequency, the last donation date should not exceed one month from the current date). Kindly refrain from auto-filling missing date and time of the last donation.
- Zeros before last 4 credit card digits, ZIP codes or other fields are preserved, as predefined Excel / Google Sheets format may remove them.
- The provided Fundraise Up account ID is accurate, and the chosen campaigns and designations exist within the specified account. For campaigns and designations, it is necessary to specify their respective IDs.
- No duplicate emails or unique identifiers (such as Stripe IDs / Billing Agreement IDs) can be found in the sheet.
You can make a copy of this sheet and share it with firstname.lastname@example.org (please ensure we have access to the document as an editor). Please send us a link to the completed spreadsheet.
5. Data review and validation - We examine the submitted data, ensuring all required fields are accurately completed and formatted. We also confirm that plans correspond to their respective Stripe customers and conduct additional checks as necessary. During this stage, we may reach out to you for further dataset details.
6. Scheduling stop processing and migration dates - Once everything is validated and approved, please contact your legacy processor to schedule a stop processing date, time, and timezone for migrating recurring plans. After confirming the date, share it with us, and we will arrange the migration accordingly. We'll also re-adjust the dataset to guarantee that the last donation is up-to-date and donors won't be double-charged. Lastly, we deliver the data to our billing team.
7. Migration complete - Once the migration is complete, you'll receive a confirmation with the number of migrated plans and the number of plans charged upon creation. To view the full results, navigate to the Recurring tab in your Fundraise Up dashboard and select “Recurring migration” in the Source filter.