When importing a CSV file, the system will build your chart differently depending on whether the rows in your file represent people or positions. While a people-centric file lists people and their required identifiers (name and work email or employee ID), a position-centric file lists positions and their required identifiers (Built position ID or external ID). The import requirements below will help you make the needed changes in Built based on how your file is organized.
Notes about people and position identifiers:
If the file you’re importing contains multiple identifiers, you may be asked to confirm which identifier you’d like to use to build your org chart.
Using a new identifier that isn’t already saved in Built will duplicate the associated people or positions.
When importing a people-centric file:
Include a row for each person you’re adding or updating.
At minimum, you must include the following columns, with values for every person you want to import: First Name, Last Name, and either Work Email or Employee ID as the unique person identifier.
Include a Position ID or External ID column if you’d like to update any position assignments, including values for all individuals.
Notes about including position IDs and external IDs:
Excluding a person’s position identifier will remove the individual from their existing position. If a person holds multiple positions, removing their primary position can make a secondary position their new primary.
If you choose to include both a Position ID and an External ID column, you must confirm which is the primary identifier for determining position assignments.
Include a column for each additional data field you want to populate or update in the system.
Include a Reports To column with data for all people listed to ensure the importer adds everyone to your org chart. The Reports To identifier must match the unique person identifier (Work Email or Employee ID). Use an asterisk (*) to indicate someone should be placed at the top of the org chart.
Within the Chart Builder panel, you can view a list of individuals imported into Built but not added to the chart.
While it is possible to create dotted line relationships via a people-centric import, additional secondary position data cannot be imported. Therefore, we recommend creating dotted-line relationships via a position-centric import. If you prefer to add them via your people-centric 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). Once your import is complete, you can enter any additional secondary position data manually.
When importing a position-centric file:
Include a row for each position you’re creating or updating.
Include at least one unique position identifier, the Built Position ID or an External ID. Understanding the importance of position IDs can help you choose the best option.
Include a column for each data field you want to populate or update in the system.
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 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 an asterisk (*) 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 because the system will be unable to identify which position it reports to.
To fill an open position, include a column for Employee ID or Work Email to identify who’s filling the role, as well as First Name and Last Name.
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.
When adding or updating positions shared by multiple individuals, include a row for each person filling the position, ensuring that position data is identical for each.
When adding or updating secondary positions (dotted line relationships), include a row for the 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).
Notes about importing a data file:
If you have questions about importing specific field data or would like to request an import template, please contact our Customer Success Team for additional assistance. While you can update most people and position data via import, some data fields require manual updates.
When importing custom field data, you must first create a custom field in Built. Learn more about utilizing custom fields.
If a position is listed more than once and any data is conflicting, the last instance (row furthest down) in the file determines what is saved.
Blank data cells in your file will delete 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. If you’d like to exclude a data column from your import rather than importing blank values or editing your file, you can map the column to the double dash (- -).
The Employee Type field is shared by a person and their position. When importing a people-centric file, columns mapped to the Employee Type field will update both the person and their position. However, only the position’s Employee Type field data can be updated via a position-centric import.
After reviewing your file, ensure there are no extra rows or columns with “notes” or non-data content before saving it as a CSV and importing your employee or positions list.
Please contact our Customer Success Team for additional assistance.