Crewmojo supports bulk user imports via CSV file. This article outlines the required and optional fields for your CSV, along with the correct format for each.
Your CSV can be a complete file (all users) or a differential file (only changed or new records). If you upload a complete file, Crewmojo will automatically identify which records have changed and only update the relevant fields — existing records that haven't changed will be left untouched.
| Field | Required | Format |
|---|---|---|
| firstName | Yes | String |
| lastName | Yes | String |
| emailAddress | Yes | String — must be a valid email address |
| employeeCode | No | String |
| managerEmployeeCode | No | String — can also use managerEmailAddress if employee codes are not present |
| employmentStartDate | No | String — allowed formats are any combination of DD, MM, and YYYY. Eg. YYYY-MM-DD or MM-DD-YYYY |
Custom fields can be configured in Admin > General settings and are added as extra columns in the CSV alongside the core fields above. Once imported, custom fields are automatically carried through into system reports and can also be used to trigger automations. For example, including an employeeFinishDate field can be used to automatically trigger an exit survey.
firstName, lastName, and emailAddress — must be present and populated for every row.managerEmployeeCode, you can substitute managerEmailAddress as the column name if your organisation doesn't use employee codes.employmentStartDate, any date format combining DD, MM, and YYYY is accepted (e.g. YYYY-MM-DD, DD-MM-YYYY, MM-DD-YYYY).