As of July 12, 2021, this "Learn Veracross" site has been deprecated. It will remain live at least through October 1, 2021, but will no longer be updated. All knowledge content has moved to the new Veracross Community. Please update your bookmarks.
The Veracross Data Importer allows you to import people's relationships with organizations into Axiom, which are also known as Person Organization or Organization Membership records. This import type is considered both an importer and an updater — it allows you to both import new person organization records or update existing person organization records. For the importer to consider a row an "update" instead of a new record, the person_fk and organization_fk values for the row must exactly match these values in an existing organization membership record.
The following values are found on the Organization Membership record between the person and the organization:
Importing person organization records involves:
- Preparing the data for upload using the "Person Organization" import type template found at import.veracross.com/your_school.
- Uploading the data using the Veracross Data Importer.
Preparing the Data for Upload
Prepare a comma-separated-value (CSV) file containing all data to import. This file must contain all columns in the order listed below.
Recommendation: Use the import template provided at import.veracross.com/your_school, rather than creating your own CSV file. This can eliminate many unintentional errors.
Fields in the Import Type Template
|Column (Field) Value||Notes|
|person_fk||Required value. Numeric format. Supply the internal person ID from Veracross. Find it in the Person ID column of a standard Find People query on the Main homepage (and many other places).|
|organization_fk||Required value. Numeric format. Supply the internal organization ID from Veracross. Find it in the Organization ID field of a Find Organization query. (Note that, by default, the Organization ID field is suppressed from results.)|
|relationship||Required value. Text format. The person organization relationship between the person and the organization. Find a list of available options in this Person Organization Relationship query.|
|primary_organization||Text format. Determines whether or not this organization should be designated as the associated person's primary organization. Viable options for this column are Y (for yes) and N (for no).|
|title||Text format. The person's title within the organization. This field has a 100 character limit.|
|start_date||Date format (YYYY-MM-DD). The start date for this person in this organization.|
|end_date||Date format (YYYY-MM-DD). The end date for this person in this organization.|
|address_1||Text format. The Address 1 field on the relevent organization membership record.|
|address_2||Text format. The Address 2 field on the relevent organization membership record.|
|address_3||Text format. The Address 3 field on the relevent organization membership record.|
|city||Text format. The City field on the relevent organization membership record.|
|state||Text format. The State field on the relevent organization membership record.|
|zip_code||Numeric format. The Zip Code field on the relevent organization membership record.|
|country||Text/numeric format. The Country field on the relevent organization membership record. This must be a country that already exists in Varacross — a list of available countries can be found in a Countries query on the System homepage. Accepted values are:|
|phone||Text format. The Phone field on the relevent organization membership record.|
|When updating existing data through the importer, what happens if I leave a column blank?||If you are updating an existing organization membership record, leaving a column blank will clear a value that is already in place.|
Example: the Title field is currently "Manager". If an import updates this organization membership record and the title field in the csv file is blank, the title field would be "updated" to a blank field.