With KPI imports, you can create multiple KPIs at once, update existing KPI definitions, and import target and actual values without entering this information manually for each KPI.
Two import types are available:
KPIs - to create new KPI definitions or update existing ones.
KPI progress - to import target and actual values for KPIs that already exist.
🧾 Prepare your file for KPIs import
Download the template to your computer and use it as a reference. (This sample is for reference only.)
Fill in the template (mandatory fields are highlighted in red in the file):
title (mandatory): the KPI title. Use a clear and meaningful name that describes what the KPI measures.
email/employee ID (mandatory): the ID or email of the employee who owns the KPI.
kpi_type (mandatory): defines who or which organisational unit the KPI belongs to. Available KPI types are: individual, department, location, division, company-wide.
metric (mandatory): the measurement unit used for the KPI. KPIs can be measured as percentage, number or currency.
currency_code: the currency code for the KPI. This field is required when the selected metric is Currency.
department: the name of the department associated with the KPI. This field is required when the KPI type is Department.
location: the location associated with the KPI. This field is required when the KPI type is Location.
division: the division associated with the KPI. This field is required when the KPI type is Division.
💡Weight, Year, and monthly targets are not included in the KPI import.
Target and actual values are imported separately using the KPI progress import.
How existing KPIs are updated
You can use the same file to update existing KPIs. PeopleForce identifies an existing KPI by its title and owner:
If no KPI with the same title and owner exists, a new KPI is created.
If a KPI with the same title and owner already exists, that KPI is updated instead of creating a duplicate.
When updating a KPI, make sure its title and owner in the file match the existing KPI.
📤 Import KPI data into the system
Go to Settings > Imports.
Select KPIs as the import type.
Upload your completed KPI import file.
Check the field mapping. The system maps matching columns automatically where possible. Manually map any fields that were not recognised automatically.
Make sure the mandatory fields are mapped.
Click Next to preview the data.
Review the Preview and start the import. Valid rows are processed even if other rows in the same file contain errors. Invalid rows are skipped and recorded in the import results. For example, if one row contains a department that cannot be found, that row fails, while other valid KPIs in the file can still be imported.
✅ The system will automatically validate each row. Any cells with invalid data will be highlighted in red - fix these in your file and re-import as needed.
Importing KPIs does not send notifications to KPI owners.
🗒️ Prepare your file for KPI progress import
Use this import to provide targets and actual results for KPIs. The KPIs must already exist in PeopleForce before you can import their progress.
Download the template to your computer and use it as a reference. (This sample is for reference only.)
Fill in the template (mandatory fields are highlighted in red in the file):
kpi_owner (mandatory): the ID or email of the employee who owns the KPI.
kpi_name (mandatory): the title of the existing KPI.
occurred_on (mandatory): the date for which the KPI progress is recorded.
target (mandatory): the target value for the month of the occurred_on date. For example, if occurred_on is any date in September, the target is applied to the KPI target for September.
actual (mandatory): the actual KPI result recorded for the exact occurred_on date.
📅 You can import progress for historical dates. Future dates are not supported and are rejected during validation.
Import several records for the same month
You can include several progress rows for the same KPI within one month:
If these rows contain the same target, they can be imported, while each actual value is recorded for its corresponding date.
If a row for the same KPI and month contains a different target, the conflicting row is rejected. The actual value from that row is not imported either.
If you import progress again for the same KPI and exact date, the existing actual value is updated instead of creating another result for that date.
🧾 Import KPI progress into the system
Go to Settings > Imports.
Select KPI progress.
Upload your completed KPI progress import file.
Check the field mapping. The system maps matching columns automatically where possible. Manually map any fields that were not recognised automatically.
Make sure all mandatory fields are mapped.
Click Next to preview the data.
Review the Preview and start the import. Valid rows are processed even if other rows in the same file contain errors. Invalid rows are skipped and recorded in the import results.











