Stripe subscription

Learn about migrating your existing Stripe subscription to Fundraise Up.

The general workflow and timeline for this type of migration can be illustrated as follows:

This migration type assumes that you're using Stripe as your payment processor, with that same Stripe account connected to Fundraise Up, and not employing any merchant processor to initiate or authorize supporters’ transactions. Since these customers are in the same Stripe account that is connected to your Fundraise Up account, we recommend following the steps below to begin this process:

Step 1: Export the Stripe subscription data

 
Link copied

From your Stripe subscription dashboard, export all current Stripe subscriptions. Be sure to include the entire date range, and all available columns. The data should include the subscription ID, current period date/time, interval, and Stripe Customer ID (this value will begin with "cus_"). Use the template below to see what type of data we're looking for.

Step 2: Identify and isolate the data

 
Link copied

Identify which subscriptions you would like to migrate to Fundraise Up; remove any of the subscriptions you would not like to migrate from the Stripe subscription data you exported.

Step 3: Format the data

 
Link copied

For us to use the data, it needs to be formatted in a particular way. Use our instructions and sample template to get the right formats. Make a copy of the sheet, rename it to "[Organization name] Stripe Subscription Migration", and add the relevant data.

If essential fields are missing from the Stripe subscriptions export, you can obtain the data from your CRM or a third-party solution that manages your supporters' accounts. 

Please use the formatting in the sheet, making 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 be more than one month earlier than the current date). Kindly refrain from auto-filling missing dates and times of the last donation.
  • zeros before last four credit card digits, ZIP codes and other fields are preserved, as predefined Excel/Google Sheets format may remove them.
  • the Fundraise Up account ID is correct, and the chosen campaigns and designations exist within that specified account. For campaigns and designations, it is necessary to specify their respective IDs.
  • there are no duplicate emails or other unique identifiers (such as Stripe IDs/Billing Agreement IDs) in the sheet.

Share this sheet with the migrations@fundraiseup.com email address and ensure that we are granted Editor access as we may need to make adjustments to the format. Please add the cleaned Stripe subscription data in a new tab on the spreadsheet and send us the link to the completed spreadsheet.

Step 4: Data review and validation

 
Link copied

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.

Step 5: Schedule a migration date

 
Link copied

Once everything is validated and approved, we will arrange the stop processing and migration date, time and timezone and share it with you. We will also re-adjust the dataset to guarantee that the last donation date is up-to-date and supporters won't be double-charged. Lastly, we deliver the data to our Billing team.

Step 6: Migration complete

 
Link copied

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.

 

In this article