CSV Requirements and Best Practices

This guide will help you to understand the requirements and best practices for fields that should be included in a user data CSV. Bridge user data is pretty easy, but this document will help you to think about your CSV and what data should come into  Bridge. Note that for the file itself, the data must be in .csv format and the columns can appear in any order. Below are more requirements that are field-specific.

 

Requirements for the CSV

Must Haves

A Bridge CSV must have:

  1. A field to be used as the Unique Identifier (UID). This data point also serves as the user login.
    • This field must not contain any duplicates.
    • Can be any string of characters (including spaces) or numbers.
  2. The UID should:
    • Not recycle a string to represent another user.
    • Not change.
  3. UTF-8  encoding. Most data software like Excel, Google Sheets, and others export using UTF-8, while some HRIS systems may compile reports in a  format other than UTF-8. Though, settings sometimes can be adjusted to export in UTF-8.
    • For companies that have employees with names containing special characters (é, ñ, ç, ł, etc.), this requirement is essential. Bridge will accept CSVs not encoded with UTF-8, but the characters will not appear.
  4. The date and Time Format for csv import will be MM-DD-YYYY; you can also include an optional time of day in date fields e.g. MM/DD/YYYY 12:00.

 

Should Haves

Bridge user CSVs should have:

  1. An email address. This string must be in email format (like abcd@xyz.xy or abcd@xyz.xyz)
  • This string cannot contain any invalid characters, like spaces.
  • Bridge will not upload a line that contains invalid emails.

Date formats run via the API should conform with the ISO 8601 Data elements and interchange formats – YYYY-MM-DDTHH:MM:SSZ

Additional Resources

Related to

Was this article helpful?

1 out of 1 found this helpful

Have more questions? Submit a request