Include a row for each person you’re adding or updating.

Include a column for each data field you want to update in the system (Employee ID, Title, etc.).

Include the following columns, with values for every person listed: First Name, Last Name, and at least one unique person identifier, such as Work Email or Employee ID.

Include a Reports To column with data for all people listed if you want the importer to build your org chart. The Reports To identifier must match the unique person identifier (Work Email or Employee ID). Use * to indicate someone is at the top of the org chart.

When creating dotted line relationships via CSV import, include a Dotted Line Relationships column to assign secondary managers, using the same person identifier type as the Reports To column (Work Email or Employee ID).

When importing a people-centric file, columns containing position data will only update a person's primary position, except the Dotted Line Relationships column. To update secondary (dotted line) positions, you must upload a position-centric file.

Include a row for each position you’re adding or updating.

Include a column for each field you want to populate or update in the system (Title, Location, etc.).

If you need to remove positions, you must include a Position Status column and enter “Removed” for the position(s) you want to remove. Positions previously reporting to a removed position will be moved up in your official chart hierarchy. Customers of our Position Management module can view positions removed from their official chart on the Removed Positions report.

Include at least one unique position identifier, such as the Built Position ID or an External ID. Understanding the importance of position IDs can help you choose the best option.

Include a Reports To column with data for all listed positions if you want the importer to build your org chart. The Reports To value must match the unique position identifier used in the file (Position ID or External ID). Use * to indicate someone is at the top of the chart.

If a position’s Reports To data is left blank, the position will be placed at the top of the chart.

When filling an open position, include a column for Employee ID or Work Email to identify who’s filling the role.

When transferring a person from one position to another, ensure you’ve removed their information from columns containing person data for the position they’re leaving.

If you’re placing a new person in a position who hasn’t been added to your company account, your file must also contain a column for First Name and Last Name (or Full Name).

When adding or updating positions shared by multiple people, include a row for each person filling the position and include identical position data for each.

When adding secondary positions (dotted line relationships), include a row for the new position with identical person data. Include an Is Primary column, using False to indicate secondary positions and True for primary positions.

When updating people data using a position-centric file, you must include a column for First Name, Last Name, and a unique person identifier (Work Email or Employee ID).

While you can update most people and position data via import, some data requires manual updates.

If a position is listed more than once and rows contain conflicting data, the last instance (row furthest down) in the file determines what is saved.

Blank data cells in your file will override current field data in Built with a few exceptions: Hiring Date, Employee Type, Employee Status, Location, and Position Status. Additionally, blank values in the Reports To column of a people-centric file will remove a person from a position. When importing a position-centric file, a person will be removed from their position if both their Work Email and Employee ID data cells contain blank values.

The Employee Type field is shared by a person and their position. When importing data, file columns mapped to the Employee Type field will update both the person and their position.