More data about recurring plans now available in CRMs

We’ve updated what data is shared with CRMs about recurring plans. Organizations now receive a consistent and more complete set of data points for recurring donations across all supported platforms.

• Standardized data set: CRMs that support syncing the recurring plan entity will now receive a minimum required set of data points. These include status, frequency, amount, payment method, next and previous installment dates, campaign, custom fields, and more.
• Cancellation reasons: We now sync the cancellation reason provided by the supporter (when available) to all supported CRMs as a text field, up to 500 characters.
• Supporter anonymity: A new field, Supporter is anonymous, is now passed to supported CRMs as a yes/no value.
• Improved mapping flexibility: In most CRMs, we’ve added more entities and fields that you can map our recurring plan data to — including custom objects and user-created fields.

• Salesforce
  • Added support for mapping Cancellation reason and Supporter is anonymous from Fundraise Up’s Recurring object.
• Salesforce NPSP
  • Added support for mapping Cancellation reason and Supporter is anonymous from the Recurring object to standard and custom fields.
• Salesforce Nonprofit Cloud
  • Expanded Recurring data synced to Gift Commitment and Gift Commitment Schedule objects.
  • New fields supported: Payment method, Previous installment date, Created date, Campaign ID, Cancellation reason, Supporter is anonymous.
• Virtuous G&C Import Write
  • Added support for Recurring field: Status, Payment method, Previous installment date, Campaign ID, Cancellation reason.
• Virtuous CRM
  • Added support for Recurring field: ID, Status, Payment method, Previous installment date, Next installment date, Campaign ID, Cancellation reason.
• DonorPerfect
  • Recurring field now available for mapping to the Gift object: Status, Next installment date, Created date, Campaign ID, Supporter is anonymous, Cancellation reason.
• Bloomerang
  • All fields from Fundraise Up’s Recurring object can now be mapped to any custom field, including: ID, Status, Amount, Currency, Frequency, Previous installment date, Next installment date, Created date, Campaign ID, Supporter is anonymous, Cancellation reason.
• Bonterra EveryAction
  • All fields from Fundraise Up’s Recurring object can now be mapped to Commitments and any custom fields, including: ID, Amount, Currency, Previous installment date, Next installment date (including standard End Date), Created date, Campaign ID, Supporter is anonymous, Cancellation reason.
• Microsoft Dynamics 365 F&E
  • Added support for new recurring fields: Previous installment date, Created date, Campaign ID, Supporter is anonymous, and Cancellation reason.