Direct attributes on a record are fields that can only have one value, and typically this tends to be bio-demographic data. Fields like citizenship status, gender, but also contact data like cell phone number, home address, and more are direct attributes. This is a good place to start when importing historic data as the mapping will be pretty standard and you won't have to worry about application, funnel, school, or test score data.
Creating a Bio-Demographic File
Creating a Bio-Demographic File
As a reminder, the file needs to be either .csv or .txt, contain a unique identifier (or a few!), and only have one row per record. The bio-demographic file is a great opportunity to add unique identifiers that may be helpful for future imports like your application and funnel information.
Any direct attributes or properties can be added to the file you are creating. There is a Historic Bio-Demographic Import template in your instance, but you are not required to follow that exact layout if you need additional unique identifiers or need to put the fields in a different order, the template is a starting point if you need direction.
Fields to Include in the File
Fields to Include in the File
Listed below are fields that you can include on your bio-demographic file.
Contact Identifiers (Student ID, Historic ID, and/or Email)
Name
Birthdate
Gender
Ethnicity
Citizenship
Phone Numbers
Addresses
Intended Major, Term, Student Type, Degree
Intended fields are simply what the student might be interested in or expressed interest in through a form. This is not related to the application.
Mapping Bio-Demographic Data
Mapping Bio-Demographic Data
You will have one import task for bio-demographic data with some of the following fields.
Mapping
Mapping
Contact Identifiers: This can be a historic ID from a previous CRM, student ID, email, or other identifier. Not all are necessary, but the more the better!
user-identities-historicid
user-identities-schoolid
user-email-address
Note, this is the record's personal email
user-identities-school-email
Personal
user-ssn
user-preferred-name
user-first-name
user-middle-name
user-last-name
user-former-last-name
user-dob
user-gender
user-gender-pronouns
Contact
user-phone-cell-country-code
user-phone-cell-number
user-phone-home-country-code
user-phone-home-number
user-sms-updates
user-addresses-home-street1
user-addresses-home-street2
user-addresses-home-city
user-addresses-home-state
user-addresses-home-province
user-addresses-home-country
user-addresses-home-zip
user-addresses-mailing-street1
user-addresses-mailing-street2
user-addresses-mailing-city
user-addresses-mailing-state
user-addresses-mailing-province
user-addresses-mailing-country
user-addresses-mailing-zip
Race
user-race-hispanic
user-race-categories
Citizenship
user-citizenship-country
user-citizenship-country-of-birth
user-citizenship-us-status
user-citizenship-visa-type
Pay special attention to any fields that have a blue box next to their Field and Slug name. Blue = Do! There are additional transformation settings to consider before running the import. Review our Column Setting Options article for an explanation on Transformations.
Next Steps
Next Steps
After you complete mapping the import, you are almost ready to run it. Follow the rest of our Creating Imports help article for setting up Configuration Settings, Previewing, and Running your import.
Importing a large file? Copy the first couple rows of your file into a separate file and import that subset in. That will give you a chance to see what the results look like, without causing too much trouble if something was mapped incorrectly.