If you'd like to import peer-to-peer participant or team data from another provider, we can assist in the process.
The service incurs a one-time fee of $999.00 and can take up to 14 business days to complete once we have everything we need from you.
Here's a rundown of how it works:
You'll enter information into a CSV file to upload to our system. This automatically creates the registrations and sends a registration email confirmation that admins can configure in the control panel. We manually add some messaging to have registrants set an account password if they are fundraising, which you can't control, but all of the other text is editable.
Please note: It's important to get your peer-to-peer event set up and ready in Qgiv (all registration options entered, custom fields, any $0 categories, etc.) BEFORE we run the import and not make any changes until the import is complete.
Ready to get started? Here's what you need to do!
- Contact our Customer Experience Team and let us know you'd like to import peer-to-peer registrant and/or team data to Qgiv.
- Download the CSV templates attached to this article--there's one for registrations and one for team information.
- Carefully review the tables below to see what information needs to go in each column.
Please note: If files are not submitted in the correct format, this could impact the overall timeline and risk additional costs up to $1,000.00.
- Once you've entered the information (make sure to check for accuracy!), let the Customer Experience Team know you're ready, and we'll coordinate with you to complete the process.
Please note: The process may take up to 14 business days from this point to completion.
Registration Import Format Specifications
Any yes/no fields that are missing or left blank will default to "no"
| Column Name | Description | Data Type | Required |
| firstName | Registrant's first name | Any string | ✓ |
| lastName | Registrant's last name | Any string | ✓ |
| street | Registrant's street | Any string | ✓ |
| city | Registrant's city | Any string | ✓ |
| state | Registrant's state | FULL state name | ✓ |
| zip | Registrant's zip code | 5-digit zip code | ✓ |
| country | Registrant's country | Two-character country abbreviation | ✓ |
| phone | Registrant's personal phone number | 10-digit phone | |
| cell | Registrant's personal cell phone number | 10-digit phone | |
| username | Username for registration and/or the personal email address | Valid email address | ✓ |
| category | ID of category under which the registration should occur | Integer | ✓ |
| paymentType | If there was a fee for registration, how was it collected? | "cash" or "check" but will be empty if there is no payment required | |
| fundraisingGoal | The fundraising goal of the registration (defaults to participant fundraising goal) | Any number | |
| pfp_message | The personal message displayed in the first content control on the PFP | Any string | |
| emergencyContactFirstName | First name of the first emergency contact, if required | Any string | |
| emergencyContactLastName | Last name of the first emergency contact, if required | Any string | |
| emergencyContactPhone | Phone number of the first emergency contact, if requried | 10-digit phone | |
| emergencyContactEmail | Email of the first emergency contact, if required | Valid email address | |
| emergencyContact2FirstName | First name of the second emergency contact, if required | Any string | |
| emergencyContact2LastName | Last name of the second emergency contact, if required | Any string | |
| emergencyContact2Phone | Phone number of the second emergency contact, if required | 10-digit phone | |
| emergencyContact2Email | Email of the second emergency contact, if required | Valid email address | |
| parentRegistration | Parent registration username or ID | Integer (ID) or valid email (username) | |
| activityRole | The registration role (Use "managed" for additional registrants whose fundraising will be managed by the primary registrant) | "fundraising", "nonfundraising", or "managed" | ✓ |
| showInSearch | Allows the registration to appear in search | Yes or No | |
| showInLeaderboard | Allows the registration to appear in leaderboards | Yes or No | |
| classification | The classification under which the registration should occur | Integer | |
| classificationCaptain | Is the registrant a classification captain? | Yes or No | |
| team | The team ID under which the registration should occur | Integer | |
| teamCaptain | Is the registrant a team captain? | Yes or No | |
| teamOwner | Is this registration the team owner? ONLY ONE TEAM OWNER CAN EXIST PER TEAM. | Yes or No | |
| avatar | The URL of the avatar image to use for the registration | Valid URL | |
| alias | The alias to use for the registration | Any string | |
| [custom field ID or reporting label] | Any additional columns that match a custom field ID or reporting label will map the registration to that custom field with the answer provided | Integer (ID) or any string (reporting label) |
Team Import Format Specifications
Any yes/no fields that are missing or left blank will default to "no"
| Column Name | Description | Data Type | Required |
| title | The title of the team | Any string | ✓ |
| registrationGoal | The team member count goal (defaults to zero) | Integer | |
| originatingRegistration | The ID of the registrant who is the owner of this team | Integer | |
| fundraisingGoal | The fundraising goal of the team (defaults to team fundraising goal) | Any number | |
| allowRegistration | Should this team allow registrations? | Yes or No | |
| showInSearch | Allows the team to appear in search | Yes or No | |
| showInLeaderboard | Allows the team to appear in leaderboards | Yes or No | |
| avatar | The URL of the avatar image to use for the team | Valid URL | |
| alias | The alias to use for the team | Any string | |
| classification | The classification under which the team should reside | Integer |