Data Mapping Tables

	A	B
1	Key for Fields
2	Required	These fields are necessary for a data import
3	Highly Recommended	While not required, these are highly recommended
4	Recommended
5	Optional	These fields are either auto populated or have little impact on the data you are importing. If you have this data, you may include it.
6
7
8	Overview of Salesforce and HandsOn Connect
9	Salesforce is a relational database with different objects which hold records (your data). These work together in a variety of ways. HandsOn connect extends Salesforce and allows you to have a greater view of your data with volunteer engagement.
10
11	When importing data, most people will import Organizations, Contacts & Locations. Many will import Volunteer Opportunities and Occurrences. If you wish to have historical data in your system of volunteer data, then you will complete the Connections table. Teams, Team Members and Events are not as common.
12
13	Objects in Salesforce that will be utilized for the data migration of HandsOn Connect, including the NPSP:
14	Organizations	These are all entity organizations in your system: businesses or nonprofits. Also referred to as Accounts
15	Contacts	All of the people in your system. This will include volunteers, donors, volunteer opportunity coordinators, or business contacts
16	Locations	This is where all volunteer opportunities and occurrences take place. It is recommended that for any nonprofit in your system, you include a location
17	Volunteer Opportunities	This object holds all of the default information for a volunteer opportunity - the description, overall when it takes place and status and search characteristics
18	Volunteer Occurrences	Each volunteer opportunity must have at least one occurrence, date and time specific can have more than one. This it the "when" a volunteer opportunity takes place. The times for each occurrence must not span more than one day (each date will need it's own occurrence) and the start and end times must be within the dates of the Volunteer Opportunity. Also, the end time must be after the start time, and not equal to it.
19	Recurrences	Recurrences are NOT USED when importing historical data. This tab is included in the event that a future set schedule of occurrences needs to be created.
20	Volunteer Connections	When a volunteer signs up for an opportunity this record is created and is a link between the Volunteer (Contact) and the Occurrence. This record holds attendance status as well as start/end dates of service and number of hours served.
21	Teams	Used for groups of volunteers.
22	Team Members	These are the members (Volunteers/Contacts) of these teams
23	Events	Events are used to group Volunteer Opportunities. Example: MLK Day of Service has many opportunities all related to this one event
24
25	Specific to NPSP
26	Donations	Also known as Opportunities. This would include all donation, grant or other income related information
27	Relationships	This would be used if you are already tracking these relationships (mother, son, friend etc).
28	Allocations
29
30	When looking at the tables, the ID needs to be unique and is what is used to connect the various objects (contact ID is used on Organizations, organization ID is used on Contacts; Volunteer Opportunity ID is used in Occurences). If you already have a unique ID from a prior system, it is fine to continue to use this, however, if you do not, be sure that the IDs carry through and that they are unique. Also, the data that is listed in these files is demo data and can be disregarded.
31
32	Recommended Documentation
33	Volunteer Opportunity Types	http://partners.handsonconnect.org/m/74944/l/836788-volunteer-opportunity-types
34	Data Migrations - A How-To	https://docs.google.com/document/d/1UudE8mcpAS8Yyiu9iI0sI8X5J75uFR9ul_S-Q45YbB8/edit?usp=sharing
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100