Print Friendly, PDF & Email

Prepare your spreadsheet for import

In this article, we will explain how to prepare various types of data for import. The table below outlines the different data fields and their required formatting to ensure a smooth and efficient upload. Certain data fields will need specific headings to be identified when setting up data mappings on the data import page in Broadstripes. You can define data mappings manually, but using the appropriate column headers will speed up the process.

Person name
Data Field/Column Matching?DetailsExampleWorks with
Each contact in your spreadsheet must have a name, whether a person or an organization. Broadstripes gives you a lot of flexibility when importing people's names, but storing each part of a person's name in a separate column is important. (You can find instructions on separating a full name column into first, middle and last name columns here)
For people, name fields include:
TitleTraditionally, this is an abbreviated prefix like "Ms." or "Mr.", "Dr.", "Rev.", and so on. It can, of course, be ignored.Correct inconsistencies in the use of abbreviations and periods (e.g., Dr., Dr, Doctor) before importing.Person
First Name
The "given" name of an individual. Examples: "Louise", "Michael", "Esteban", and so on.
Can be used for matching and such. Made for spacing
First, Middle, and Last names must be in separate columns.Person
Middle name
This may be the full name or just an initial.First, Middle, and Last names must be in separate columns.
Person
Last name
The family name of the personFirst, Middle, and Last names must be in separate columns.Person
NicknameIn this column, you can add any nicknames that could help you identify or keep track of your workers. This field allows you to retain the worker's legal name in your data while allowing people to search for them by the name they are commonly called.The familiar name by which the person is known.
Examples:

"Lou", "Mike", or "Steve"

Person
SuffixAnything the person adds to their name after the last name. Examples: "Jr." and "III".Any suffixes such as

Jr., Senior, II, III.

Person
Organization name
Data Field/Column Matching?DetailsExampleWorks with
Organization Name
The official name of the organization

Saint Vincent Hospital, MegaBurger, etc.

Organization
NicknameIf the organization is commonly called something other than its official name, input it here.Saint Vincent Hospital's nickname could be SVH.Organization
Contact info
Data Field/Column Matching?DetailsExampleWorks with
Contact info includes phone, email, fax, and messenger info along with communication permissions. Contact info needs to be categorized as Home, Personal, Business, or Other.
PhoneThe 10 digit phone numberThe phone number column will accept a standard 10 digit phone number

261-444-7899, (718) 184-6654, etc

All
Phone NotesThis field contains any notes or information you want to record about the contact's phone number.New notes will not be imported if the notes field in the app already contains data.All
Phone BadThe "Phone Bad" fields are numbers you want to retain but are invalid.When importing a bad phone number, more than one column is necessary. The first column (Column Header: Business Cell Phone) will include the phone number. There must be an additional column (Column Header: Business Cell Phone Bad) that will indicate a bad phone number. The applicable rows will contain one of the following in the latter column:
  • Bad: Yes, True, T, 1, X
  • Not Bad: No, False, F, 0
All
Cell PhoneThe 10-digit mobile phone numberThe phone number column should not include *All
Cell Phone NotesThis field contains any notes or information you want to record about the contact's cellular number.

Theresa turns off her cell phone after 7 pm



New notes will not be imported if the notes field in the app already contains data.
All
Cell Phone BadThe "Phone Bad" fields are numbers you want to retain but are invalid.When importing a bad phone number, more than one column is necessary. The first column (Column Header: Business Cell Phone) will include the phone number. There must be an additional column (Column Header: Business Cell Phone Bad) that will indicate a bad phone number. The applicable rows will contain one of the following in the latter column:
  • Bad: Yes, True, T, 1, X
  • Not Bad: No, False, F, 0
All
Cell Phone PermissionThe Cell Phone Permission data field indicates if a contact gives permission to receive phone communications.A Cell Phone Permission entry can be one of two values or blank:
  • Opted in
  • Opted out
All
Cell Phone Permission ReasonThe "Cell Phone Permission Reason" data field records how a contact gave permission to contact or to opt out of communication.The following permission reasons may be entered in this field/column:
  • Signed paper form
  • Submitted online form
  • Clicked emailed link (or sent an email)
  • Sent a text message
  • Gave verbal instructions
  • Is a bargaining unit member

    (Opted-in only)

  • Set in external
All
Pager NotesThis field contains any notes or information you want to record about the contact's pager number.If the notes field already contains data, new notes will not be imported.

John is a driver. It may take hours before he is able to respond.

All
Pager BadThe "Pager Bad" field is a phone number that you want to retain but are not valid.When importing a bad phone number, more than one column is necessary. The first column (Column Header: Business Pager) will include the phone number. There must be an additional column (Column Header: Business Pager Bad) that will indicate a bad pager number. The applicable rows will contain one of the following in the latter column:
  • Bad: Yes, True, T, 1, X
  • Not Bad: No, False, F, 0
All
Email
The email address of the contact

jane@example.com

All
Email NotesThe Email Notes field should contain any relevant information about a contact's email.

This email address should be used if Ken does not respond to the primary



New notes will not be imported if the notes field already contains data.
All
Email BadThe "Email Bad" field is an email that you want to retain but is not valid.When importing a bad email address, more than one column is necessary. The first column (Column Header: Other email) will include the email address. There must be an additional column (Column Header: Other Email Bad) that will indicate a bad email address. The applicable rows will contain one of the following in the latter column:
  • Bad: Yes, True, T, 1, X
  • Not Bad: No, False, F, 0
All
Email PermissionThe Email Permission data field indicates if a contact gives permission to receive email communications.An Email Permission entry can be one of two values or blank:
  • Opted in
  • Opted out
All
Email Permission ReasonThe "Email Permission Reason" data field are a record of how a contact gave permission to contact or to opt out of communication.The following permission reasons may be entered in this field/column:
  • Signed paper form
  • Submitted online form
  • Clicked emailed link (or sent an email)
  • Sent a text message
  • Gave verbal instructions
  • Is a bargaining unit member

    (Opted-in only)

  • Set in external
All
FaxThe fax number of a contact

261-444-7899



The phone number column should not include *
All
Fax NotesAny notes or information you want to record about the contact's fax number.New notes will not be imported if the notes field already contains data.

Fax number is a shared line. Confirm receipt with follow-up call after fax., etc

All
Fax BadThe "Fax Bad" fields are fax numbers that you want to retain but are not valid.When importing a bad fax number, more than one column is necessary. The first column (Column Header: Home Fax) will include the fax number. There must be an additional column (Column Header: Home Fax Bad) that will indicate a bad fax number. The applicable rows will contain one of the following in the latter column:
  • Bad: Yes, True, T, 1, X
  • Not Bad: No, False, F, 0
All
PagerThe pager number of the contactThe phone number column will accept a standard 10 digit phone number

261-444-7899, (718) 184-6654, etc

All
ImThe URL or handle for Instant MessengerEnter the person's instant messenger info here.All
Im NotesAny notes or information you want to record about the contact's Instant Messenger.If the notes field already contains data, new notes will not be imported.All
Im BadThe "Im Bad" fields are instant messenger urls or handles that you want to retain but are not valid.When importing a bad IM handle, more than one column is necessary. The first column (Column Header: Personal IM) will include the instant messenger handle. There must be an additional column (Column Header: Personal IM Bad) that will indicate a IM handle. The applicable rows will contain one of the following in the latter column:
  • Bad: Yes, True, T, 1, X
  • Not Bad: No, False, F, 0
All
Person Address
Data Field/Column Matching?DetailsExampleWorks with
People addresses are categorized as Home, Business, or Other. Addresses may be separated by street address, city, state, and zip, or you may have one column with the complete address.
AddressThe street address of the contact

100 Shepard Ave., 658 N. Main St. etc.



If you do not have your address formatted in separate columns, you may alternatively enter the full address in this column, e.g.

100 Shepard Ave., Tuscaloosa, AL 35487


Person
UnitA unit or suite number in the contact's address.

3rd Fl, Unit 454, Apt 3B, etc

Person
CityThe city the address is located in

Tuscaloosa, Springfield, Houston, etc.

Person
StateThe two-letter abbreviation for the state.

CT, NY, NV, etc

Person
ZipThe 5-digit zip code or 9-digit zip code, including the plus-four code.

37042, 73099-1039, etc

Person
Address NotesAny notes or information you want to record about the contact's address.

Doorbell does not work. Knock hard.



The column header should include the appropriate category:
  • Home Notes
  • Business Notes
  • Other Notes
Person
Address BadThe "Address Bad" fields are addresses that you want to retain but are not valid.When importing a bad address, more than one column is necessary. The first column(s) (Column Header: Home Address) will include the address. There must be an additional column (Column Header: Home Bad Address) that will indicate a bad address. The applicable rows will contain one of the following in the latter column:
  • TRUE: Yes, True, T, 1, X
  • FALSE: No, False, F, 0
Person
Organization Address
Data Field/Column Matching?DetailsExampleWorks with
Organization addresses are categorized as Business or Other.Addresses may be separated by street address, city, state, and zip, or you may have one column with the complete address.
AddressThe street address of the contact

100 Shepard Ave., 658 N. Main St. etc.


If you do not have your address formatted in separate columns, you may alternatively enter the full address in this column, e.g.

100 Shepard Ave., Tuscaloosa, AL 35487

Organization
UnitA unit or suite number in the contact's address.

3rd Fl, Unit 454, Apt 3B, etc.

Organization
CityThe city the address is located in

Tuscaloosa, Springfield, Houston, etc.

Organization
StateThe two-letter abbreviation for the state.

CT, NY, NV, etc

Organization
ZipThe 5 digit zip code or9 digit code including the plus-four code.

37042, 73099-1039, etc

Organization
Address NotesAny notes or information you want to record about the organization's address.

Doorbell does not work. Knock hard.


The column header should include the appropriate category:
  • Business Notes
  • Other Notes
Organization
Address BadThe "Address Bad" fields are addresses that you want to retain but are not valid.When importing a bad address, more than one column is necessary. The first column(s) (Column Header: Home Address) will include the address. There must be an additional column (Column Header: Home Bad Address) that will indicate a bad address. The applicable rows will contain one of the following in the latter column:
  • TRUE: Yes, True, T, 1, X
  • FALSE: No, False, F, 0
Organization
Employment
Data Field/Column Matching?DetailsExampleWorks with
When importing employment, you will be connecting people to their employers. You may choose to update existing employment with new information or to create separate employment in the configuration section of the data import upload page.
EmployerThe name of the organization that is the employer.The main name of an organization

e.g. Grand City Hospital, The Grand Hotel, Mega University, etc.



If the employer does not exist in your project, a new organization will be created.
Person
DepartmentAn employer may have different sections, floors, units, etc.A department is a child organization of an employer.The name of the department

e.g. Accounting, Concierge, North Campus, etc.


If the department does not exist in your project, a new organization will be created in your project.
Person
SubdepartmentLarger organizations may be subdivided into multi-level structures. A subdepartment is a division of a department which is part of a employer.The name of the subdepartment

e.g. 3rd Floor, West Pavilion, VIP Lounge, etc.


If the subdepartment does not exist in your project, a new organization will be created in your project.
Person
SubsubdepartmentLarger organizations may be subdivided into multi-level structures. A subsubdepartment is a division of a second level department.The name of the subsubdepartment

e.g. Clerical, Special Units, etc.


If the subsubdepartment does not exist in your project, a new organization will be created in your project.
Person
SubsubsubdepartmentLarger organizations may be subdivided into multi-level structures. A subsubsubdepartment is a division of a third level department.The name of the subsubsubdepartment

e.g. Casual, Level E, etc.

If the subsubsubdepartment does not exist in your project, a new organization will be created in your project.
Person
Classification or Job TitleClassification/Job Title is the title/role of an employee.

Housekeeper, Unit Clerk II, Teacher's Assistant, etc.

The header of this column will be either Classification or Job Title depending on your project's settings.
Person
Parent Organization IDThis column is used to indicate that the organization is a child of another organization or subdepartment.You may use any unique id to identify the parent organization. This can be the Broadstripes ID or an external system ID.The column header for this field/column should start with "Parent Organization" and the name of type of ID.

Parent Organization ID, Parent Organization Legacy CRM ID, Parent Organization NetID, etc.

Employee NumberThis field records the worker's employee number.This field is a free-form text box that will accept any combination of text that is applicable.Person
Employee StatusThis field can indicate the status of worker

Floater, Permanent, Temp, etc


The status is not pre-defined. You may use whatever term is appropriate for your project.
Person
Work LocationThis field can be used to provide location details for a worker

Fordham Road, Front of House, etc.

Person
Bargaining Unit MemberThis field indicates if a person is a member of a bargaining unit.This is a yes/no checkbox, which may or may not suit your union’s needs for keeping track of members.If you choose not to use this field, there are other tools in Broadstripes to track union membership.This column may contain one of the following values for each contact:
  • TRUE: Yes, True, T, 1, X
  • FALSE: False

An import that includes Bargaining Unit Members should include employment information. (Employer, Department, etc.)
Person
Date EndedThe date the employment terminated.This field records the last date of employment in MM/DD/YYYY format.Person
Date Last PaidThe date the worker last received their wagesThis field records worker's last payday in MM/DD/YYYY format.Person
Hourly RateThis field records the worker's hourly wage

e.g. 17.23, 20.00, etc.

Person
HoursThis field records the hours worked.

32.5, 17:15, etc.

Person
Seniority DateThis field records worker's seniority date in MM/DD/YYYY format.

01/22/2019, 11/03/1982, etc.

Person
Recent Hire DateThis field records worker's most recent hire date (in the case of a rehire) in MM/DD/YYYY format.

01/22/2019, 11/03/1982, etc.

Person
Start DateThis field records worker's start date in MM/DD/YYYY format.

01/22/2019, 11/03/1982, etc.

Person
Is PrimaryWhen a worker has more than one concurrent employments, this field will indicate which employment is the primary.This column may contain one of the following values for each contact:
  • TRUE: Yes, True, T, 1, X
  • FALSE: No, False, F, 0

Person
Full Part TimeThis field ccontains the worker's full time or part time status.

Full-time, part-time, Casual, etc.

Person
Leadership
Data Field/Column Matching?DetailsExampleWorks with
Leader RoleThe Leader role provides a way to categorize and identify the leaders within a bargaining unit or worker group. Account admins can create leader roles as needed for the project.

Commitee, Key Leader, Target, etc.


If the leader role category of an imported contact, does not exist, a new leader role will be created.
Person
Leader Broadstripes IDThe Broadstripes ID is a set of 6 alphanumeric characters that are unique identifiers exclusive to the app.
This field contains the Broadstripes ID of the leader of a group.

UTO-559, LST-470, etc.


Person
Leader Unique IDThe unique identifier of an external system.This spreadsheet column should be mapped to the Broadstripes field named after the external system (i.e. “Big Hospital ID” if you named the external system “Big Hospital”).The Broadstripes ID is also a unique ID.Person
Follower Broadstripes IDThe Broadstripes ID is a set of 6 alphanumeric characters that are unique identifiers exclusive to the app.
This field contains the Broadstripes ID of the follower of a worker.

UTO-559, LST-470, etc.


Person
Follower Unique IDThe unique identifier of an external system that belongs to a follower. This spreadsheet column should be mapped to the Broadstripes field named after the external system (i.e. “Follower Big Hospital ID” if you named the external system “Big Hospital”).The Broadstripes ID is also a unique ID.Person
Basic info
Data Field/Column Matching?DetailsExampleWorks with
RelationshipsThe relationships field allows you to ability to track special relationships between individual workers.Some relationships are automatically available for use, such as

Friend of, neighbor of, etc.


More relationships can be created by Broadstripes support upon admin request.
The header of this column should include the type of relationship, e.g.

Family member of, Connected to, Members include.


The values will include the Broadstripes ID of the person or organization you want to connect.
All
NotesThe notes fields is a built-in memo field which can be used to store any textual information you choose about a contact.When you match to an existing contact and upload new data to the Notes field, it is appended to any existing text already in the field. This behavior is unique to this field.Person
PartyIf your project includes voter data, you can use the Party field to enter registered voters’ party affiliation.Be sure to check for spelling and grammatical errors.If a value does not exactly match an existing value a new one will be created.
You should also check for reiterations of the same party. For example, "Dem" and "Democrat" will create two separate values even though they signify the same party.
Person
Union MemberThis is a yes/no checkbox, which may or may not suit your union’s needs for keeping track of members.If you choose not to use this field, there are other tools in Broadstripes to track union membership.The Union Member field may contain one of the following values for each contact:
  • TRUE: Yes, True, T, 1, X
  • FALSE: False
Person
Birth DateBirth dates are useful when trying to correctly identify workers with common names or the same name, and also may be used for matching employer records.This field records worker birth dates in MM/DD/YYYY format.Person
WebsiteBoth people and organizations can have a website. For workers, this field can be useful for storing Facebook or Twitter account links, blog pages, and so on. The data in this field will be displayed as a Web link.*Insert full URLs

https://www.example.com

All
Contact TypeBroadstripes project admins can create “contact types” to capture the distinctions between different types of people and organizations. For example, an external organizing campaign might have two types of people: “Workers” and “Managers.” A community organizing campaign might have “Media,” “Elected Officials,” and “Neighborhood Leaders.” Examples of organization sub-types in a healthcare campaign might be “Hospital,” “Department,” “Clinic,” and so on. Contact type can’t be set in bulk anywhere else, so this can be a handy feature of the import.The contact type must exist in the project already. *All
Unique IDs
If you’re uploading data from an external system for the first time, you will probably want to map the column containing the unique ID from that system to the Broadstripes field intended to capture it (the “external system ID” that was automatically created when you or another admin created the external system).For example, if you have an excelsior list (aka “the e-list”) list provided by an employer, it will often (though not always) have a column containing a unique ID for each worker, under a header like “ID,” “Employee ID,” etc. In order to capture this unique ID and match on it when an updated list is provided, a Broadstripes admin should create an external system named “E-list” or “Employer” (or whatever makes sense to the organizing team). Doing that will automatically create a field named “E-list ID” or “Employer ID” in Broadstripes.This spreadsheet column should be mapped to the Broadstripes field named after the external system (i.e. “Big Hospital ID” if you named the external system “Big Hospital”).The Broadstripes ID is also a unique ID.All
EventsYou can use events to record and track literal union-organized events, like rallies and marches, but you can also use events to keep track of important one-time information or occurrences, like petition signatures or signing a union card. You can even use events for answering multiple yes/no questions about the workers in the bargaining unit. For more information on using events, click here. Importing event data requires that you create an event, and then create as many "steps" under the event as you need to capture your data.The column header for Events should start with the event name followed by a colon and the the step name.
For example: If your project has an event called "July Rally" and and event step called " Invited", the column header would be “July Rally: Invited”. Mark the applicable contacts with an X in their corresponding row of the column
All
ListsLists give you an easy way to manually tag individuals who you want to track as a group f'or any reason. You can find additional information on tag lists here.To add a contact to a list, you need to create a column whose header starts with “List:” followed by the name of the list that you want updated ( A new list will be created if the name provided does not match an existing list.) In the rows of the corresponding contacts enter X to add that contact to the list.All
Assessment or CodeAssessments or codes are excellent way to assess where the workers stand in relation to the campaign’s goalsAssessments must be imported in numeric form, and must fall within the range of the possible values in the project. Depending on your project settings, the column header will either be Assessment or Code.All
Custom fields
Data Field/Column Matching?DetailsExampleWorks with
Custom fields - CheckboxesCheckboxes are used to indicate data that can either be true or false.The header of this column should be the actual name of the custom field.
This column may contain one of the following values for each contact:
  • TRUE: Yes, True, T, 1, X
  • FALSE: No, False, F, 0
All
Custom fields - single line text fieldsThis field may be used for free-form text, a date or number.If data already exists in this field for a contact, it will be overwritten with new data in an import.All
Custom fields - multi-line text fieldsMulti-line text input fields allow free-form text with line breaks.If data already exists in this field for a contact, it will be overwritten with new data in an import.All
Custom fields - Dropdown chooserDropdown choosers allows a select set of values for a data field. This field allows one value.If the value to be imported into Broadstripes is not already an option in the dropdown chooser, you must enable the option to "Allow imports to add options."
This feature will allow the app to create new options via data import.
You can implement this by selecting it on the custom field's edit page.
All
Custom fields - Multiple selection chooserMultiple selection choosers allows a select set of values for a data field. This field may have more than one value.Values are separated by commas, e.g.

Healthcare, Wages, Coverage


The values included in an import will overwrite the existing data in this field.
If the value to be imported into Broadstripes is not already an option in the dropdown chooser, you must enable the option to "Allow imports to add options."
This feature will allow the app to create new options via data import.
You can implement this by selecting it on the custom field's edit page.
All
Custom fields - Sortable listsSortable lists are usually used to indicate levels of importance or priority by allowing the adjustment of a value's position.If the value to be imported into Broadstripes is not already an option in the dropdown chooser, you must enable the option to "Allow imports to add options."
This feature will allow the app to create new options via data import.
You can implement this by selecting it on the custom field's edit page.
All
Custom fields - TimeThis field is used to record a time of an event such as a petition signing, etc.

01:23 PM, 2:47, etc.

All
Timeline Items
Data Field/Column Matching?DetailsExampleWorks with
A timeline item is a record of an occurrence, including when the event occurred, who created the item, who contacted the person, and a description. This appears on a contact's timeline. To create a timeline item with a data import, you must indicate those details in to seperate columns:
Timeline Item TypeThis column indicates how the timeline item will be categorized.The timeline item type may include:
  • Note
  • Group Meeting
  • House Visit
  • One-on-one
  • Phone Call
  • User-defined timeline item type (e.g. Training, Information Session, etc.)
All
Timeline Item DateThe date on which interaction or event occured.

3/15/2022, 11/7/14, etc.

All
Timeline Item DescriptionThis column is where you would describe the details of the occurence.

Henrietta seems to have a better understanding of what a union would mean for her and her family. She said she would attend the next meeting on Tuesday.

All
Timeline Contacted by Unique IDThis data field identifies the person who contacted this person using a Unique IDThis must be a unique ID such as a Broadstripes ID or an external system IDAll