This import template will create or match a donor contact and a fundraiser contact. The match criteria are based on Name, Email, and Address for the donor and CRM ID, Sponsored Fundraiser ID, and Name for the fundraiser.
Both contacts will be added with an Active account status, the donor will be added with contact type Individual and the fundraiser will be added with contact type Fundraiser.
Attribute type Funraisin Marketing Opt-in? will be created, with attributes Yes and No. One of these will be added to each donor contact, depending on the Marketing opt-in column.
Attribute type Campaign Name will be created, with attributes for each value in the Donated to Event Name column. This will be added to each donor contact.
It will create a payment on the donor contact as per the details in the template and use the default GL code in your organisation. The batch for these payments will be [Funraisin] [payment month] [payment year]. All payments will be added as credit card pay type with a payment successful status.
If there is a Sponsored Fundraiser ID then the payment will be added as type Supporter-Led Fundraising and linked to the fundraiser contact.
Please see the table below for how the template columns are mapped in vega:
Template Column | Data added to vega |
ID |
This is ignored in the import |
MemberID | This is ignored in the import |
PageID | This is ignored in the import |
Title | This will be added as the donor contact Title |
First name | This will be added as the donor contact First Name |
Last name | This will be added as the donor contact Last name |
Organisation | This will be added as the donor contact Organisation |
This will be added as the donor contact Email Address | |
Unit | This will be added as the donor contact Address 1, combined with Street Number and Street (format- [Street Number] [Unit] [Street]) |
Street Number | This will be added as the donor contact Address 1, combined with Unit and Street (format- [Street Number] [Unit] [Street]) |
Street | This will be added as the donor contact Address 1, combined with Unit and Street Number (format- [Street Number] [Unit] [Street]) |
Suburb | This will be added as the donor contact Suburb address field |
Postcode | This will be added as the donor contact Postcode address field |
State | This will be added as the donor contact City address field |
Country | This will be added as the donor contact Country address field |
Mobile | This will be added as the donor contact Mobile |
Type | This is ignored in the import |
Donation Amount | This will be added as the donor payment amount |
Date Paid | This will be added as the donor payment date if included and will default to the import date if it is not included |
Receipt Number | This will be added as the donor payment receipt number if included |
Payment Reference | This will be added as the donor payment Pay details |
Stripe Fee | This is ignored in the import |
Optional Contribution | This is ignored in the import |
Net Amount | This is ignored in the import |
Donated to Event Name | This will be added as the donor payment Campaign Header |
Sponsored Fundraiser ID | This will be used to match on contact OrgID or added if no match exists |
Sponsored Fundraiser First Name | This will be added or updated to the fundraiser contact First Name |
Sponsored Fundraiser Last Name | This will be added or updated to the fundraiser contact Last Name |
Sponsored Fundraiser Team Name | This is ignored in the import |
Donated to Page Name | This will be added as the donor payment Campaign Action |
Marketing Optin |
This will be used to decide the donor contact's mail status. If this is N or No then the status will be inactive and the default inactive reason will be used. If this is Y or Yes then the status will be active and the default active reason will be used. This will also be added as an attribute on the contact, Fundraising Marketing Opt-in? - attributes No and Yes. |
Fundraiser CRM ID | When this is included it will be used to match the contact in vega by their vega ID |
Donation Type | This is used as the pay type where the description matches an existing pay type in your Vega system, otherwise it will use Credit Card |
Comments
0 comments
Please sign in to leave a comment.