Skip to main content

Member Data File Requirements for Enterprise Organizations

File Requirements

Your file must:

  • Be saved as a CSV file

  • Use UTF-8 encoding

  • Include a header row matching the field names below

  • Contain no quotes (") in column headers

  • Contain only one sheet

Sample CSV

Review our CSV template to understand correct formatting. The template includes:

  • All required, recommended, and optional fields with correct header names

  • Example data showing expected formats

Quick Reference

Start with the required fields, then add recommended fields based on what’s available in your organization’s HRIS system. Each additional field improves matching quality and capabilities.

Required

Field Name

Example

Notes

First name

Jane

Field should be labelled "first_name (required)"

Last name

Doe

Field should be labelled "last_name (required)"

Email

Field should be labelled "email (required)"

Management Level

This is mapped to the Role segment

Director

Maps to “Role” segment. Example values: Student, Intern, Analyst, Associate, Individual Contributor, Manager, Sr. Manager, Director, Sr. Director, VP, SVP, Executive

Recommended

Field Name

Example

Notes

Job title

Solutions Engineer

Field should be labelled "job_title"

Business unit

Consulting

Job function

Engineering

People manager status

Yes

Use only “yes” or “no”

Manager email

To exclude members from matching with managers

Optional

Field Name

Example

Notes

City, Country, or Office

For matching across geographies

Atlanta

Locale

Include this field to specify which members require other languages. English is the default language.

en-US

Field should be labelled "locale"

Use only: en-US, fr-CA, es-ES, ko, ja

Status

To deactivate and reactivate profiles for employees that go on leave and come back

active

Field should be labelled "status"

Use only: active, inactive

Did this answer your question?