Successful and verified donation records, donor records, contact records, and registration records are synced from Neon Fundraise to Neon CRM automatically after a donation or registration is submitted. Any refunds processed in Neon Fundraise will not be automatically synced and will require a manual update in Neon CRM.
Successful donations are automatically synced to Neon CRM along with the donor information (as an account), the relevant campaign, the donation recipient (to the fundraiser field), the notification recipient (for tribute donations), and donation information such as amount, anonymous selection, and payment type. See below for full mapping.
Successful registrations are automatically synced to Neon CRM. The contacts of all registrants will be synced, and they will be marked as Attendees of the corresponding Neon CRM Event. The primary registrant will be marked as an Attendee as well as a Registrant. Managed users registered by the primary user will be marked as just an Attendee. Managed users will be synced without an email but will still have their own contact record with their own name. Invited users are marked as DO NOT CONTACT.
The sum of the registration will be synced as a registration payment of the primary registrant. Donations made at the time of registrations will be synced as donations if both donations and registrations are configured to sync.
Successful ticket purchases are synced to Neon CRM as registrations. The ticket purchaser will be marked as an attendee of the corresponding Neon CRM Event. All tickets purchased in a single transaction are part of the same registration corresponding to the purchaser. On the Neon CRM side, tickets will either be matched to the ticket ID (using the API name), or a new ticket will be created in Neon CRM at the time the first ticket is purchased. If there is a donation associated with the ticket purchase it will be synced as a donation. Ticket purchases and donations associated with ticket purchases are only synced if the sync ticket registration setting is set for the Neon CRM integration.
Field mapping between Neon Fundraise & Neon CRM
The below table outlines what fields in Neon Fundraise will be synced to which fields in Neon CRM.
|Neon CRM Object||Neon CRM Field||Synced Value|
|Last Name||Last Name|
|Email Address 1||Email Address|
|Address Line 1||Address Line 1|
|Address Line 2||Address Line 2|
|Zip Code||Zip Code|
|Country||Neon CRM Country ID|
|Phone Number 1||Phone Number|
|Primary Address flag in Addresses account section||TRUE|
|Do Not Contact||Set to "true" for invited registrants|
|Organization Account||Company Name||Company Name|
|Donation||Account ID||Neon CRM Account ID|
|Amount||Donation Amount (include fees based on setting)|
|Created Timestamp||Donation Created-on Date|
|Donor Name||Donor Name Override|
|Fundraiser Account ID||Neon CRM Account ID|
|Campaign ID||Value set in Admin|
|Fund ID||Value set in Admin|
|Send Acknowledge Email||Set in Admin|
|Tribute Information||Acknowledgee Name||Name of Notification Recipient|
|Email Address||Email Address of Notification Recipient|
|Address Line 1||Address Line 1 of Notification Recipient|
|Address Line 2||Address Line 2 of Notification Recipient|
|City||City of Notification Recipient|
|State/Province||State of Notification Recipient|
|Zip Code||Zip Code of Notification Recipient|
|Country||Country of Notification Recipient|
|Payment||Amount||Donation Amount (include fees based on setting)|
|Check Number||Check Number|
|Tender (accessible via API request)||Payment Type|
|Card Number (last four)||Last four digits of card number|
|Name on Card||Name on Card|
|Expiration Month||Expiration Month|
|Expiration Year||Expiration Year|
|Address Line 1||Billing Address Line 1|
|Address Line 2||Billing Address Line 2|
|Zip Code||Billing Zip Code|
|Registration||Event (not visible in UI)||Value set in Admin|
|IgnoreCalculatedAmount (not visible in UI)||TRUE|
|Account ID||Neon CRM Account ID of primary registrant|
|Registration Date||Role Submission Date (registration completed)|
|Send System Email||Set in Admin|
|Registration Status (visible at top of event registration record)||SUCCEED|
|Attendee||Account ID||Account ID of primary user|
|First Name||First Name of primary user|
|Last Name||Last Name of primary user|
|Attended (accessible in Mark Attendance function)||TRUE|
|Registration Date||Registration Date|
|Registration Payment||Amount||Total Registration Amount (excludes donation amount)|
|Payment Received Date||Payment Creation Date|
|Cardholder Name||Name of primary registrant|
|Cardholder Email Address||Email Address of primary registrant|
|Billing Address||Billing Address of primary registrant|
|Address Line 2||Address Line 2 of primary registrant|
|City||City of primary registrant|
|Zip Code||Zip Code of primary registrant|
|Country||Neon CRM Country ID|
|Ticket||Ticket Name||Ticket name|
|Tax Deductible Amount||Synced as percentage: deductible amount divided by fee|
How does the integration handle duplicate data?
When a record is first synced to Neon CRM, the integration will look for an account match based on email address.
- If one matching account is found, account data (such as phone and address) will not be updated with the data from Neon Fundraise. The original account data, such as phone and address, will remain in the CRM. Only transactions will be added to the matching account.
- If multiple accounts are matched, the integration will look for a match based on last name and then first name.
- In the event that a match is not found, or the previously synced record’s account ID no longer exists, a new account record will be created in Neon CRM.