Import CSV data

ļ»æ

You can bulk-import data for a large number of jobs or people via a CSV file (a common format that you can export from Excel or Google Sheets).

For example, you might have performance-review information in a spreadsheet that you want to import and store as custom fields. The data format is flexible, and supports uploading any type of information associated with Jobs and People.

Importing in ChartHop

From ChartHop, visit theĀ Import CSV DataĀ page. From that page, you can upload the CSV file directly.

You must have Primary Editor access permissions to import data.

CSV format

Requirements:

  1. TheĀ first rowĀ of the CSV must be aĀ header row. It should list the names of the fields being imported. All the following rows will be imported as data.
  2. TheĀ leftmost columnĀ of the CSV must be the identifier (see below).
  3. You should include a column namedĀ Date. This should contain the date that each datapoint will be attributed to. If you do not include a Date field, your upload will be credited to the current date.
  4. Your CSV should be in UTF-8 format.

Column names

All column names are case-insensitive, and ignore spaces. So, for example, a column namedĀ Base CompĀ means the same thing as a column namedĀ basecompĀ orĀ baseCompĀ -- use whichever is most convenient for you.

If you are importing a custom field, you must use the field name in ChartHop, not the field label. So if you have a field namedĀ perfRatingĀ that is labeledĀ Performance Rating (Manager Evaluation), you should useĀ perfRatingĀ as the column name.

Identifiers

The leftmost column of the CSV is always the identifier column, which identifies which job or person to attribute the information to. You can use one of the following as identifiers:

  • EmailĀ orĀ Work EmailĀ - match based on the person's work email
  • NameĀ - match based on a person's full name (Last, FirstĀ andĀ First LastĀ both supported). This is not recommended for larger organizations because of the potential for people with duplicate names -- we recommend using Work Email instead.
  • Job IDĀ - ChartHop's unique Job ID
  • Person IDĀ - ChartHop's unique Person ID
  • ADP IDĀ - ADP's person identifier
  • Successfactors IDĀ - ADP's person identifier
  • Paylocity IDĀ - Paylocity's person identifier
  • Greenhouse IDĀ - Greenhouse's job and opening identifier

For most day-to-day purposes, we recommend using Email as it should be unique and human-readable. For programmatic integrations, you may want to consider using Job ID or Person ID.

Field columns

The field columns should be identical to the custom field name in ChartHop.

Example format

Suppose we are importing data for three employees for two data fields: selfRating (a numeric field) and selfRatingComment (a long text field). The CSV file might look like this:

email

date

selfRating

selfRatingComment

ļ»æbob@example.comļ»æ

1/1/2019

3.5

Things are good.

ļ»æjane@example.comļ»æ

1/1/2019

4.5

Awesome.

ļ»æmonica@example.comļ»æ

1/1/2019

1.5

Struggling.

ļ»æbob@example.comļ»æ

2/1/2019

3.5

Still pretty good.

ļ»æjane@example.comļ»æ

2/1/2019

4.0

Still awesome.

ļ»æmonica@example.comļ»æ

2/1/2019

3.5

Turning it around.

Sample CSV file:

ļ»æ

ļ»æ