Job profiles import helps you fill your Job catalog faster by uploading job profiles in one file instead of creating them one by one. It’s useful when you’re setting up the catalog from scratch or updating multiple profiles at once (job groups, levels, skills, and custom fields).
Prepare your file for upload
Before import, you must create a spreadsheet and fill it with the information required for uploading.
Download the template to your computer and use it as a reference. (This sample is for reference only.)
The import functionality supports two file types: .csv and .xlsx.
Fill in the template with the corresponding data (one job profile per row):
Job profile (mandatory) - job profile name, e.g., Developer
Job group (mandatory) - the full path to the job group, starting from the top-level group and separated by a slash (/). For example, Engineering / Backend. For a top-level group, enter just its name, e.g., Engineering. If the group doesn't exist yet, it's created during import.
Job level - job level for the job profile (if used in your catalog)
Skills - skills linked to the job profile (if used)
Minimum base compensation - the minimum base compensation amount for the job profile. Enter a numeric value without a currency symbol.
Maximum base compensation - the maximum base compensation amount for the job profile. Enter a numeric value without a currency symbol.
Currency - the currency used for the minimum and maximum base compensation values. Enter the corresponding three-letter currency code, such as USD, EUR, GBP, or PLN.
Custom fields - any additional job profile fields you’ve added in Settings → Job Catalog → Job Profile fields. If any job profile field is marked as required in your workspace, it’s also mandatory for the import file. Add it as a column and fill it in for every row.
How job groups are matched
PeopleForce finds each job group by its name and its parent group. It reads the path from left to right: the first name is a top-level group, and each name after a slash is a subgroup of the one before it. If there's no group with that name under that parent, the import creates a new one.
This means the path in your file has to match where the group sits in your Job catalog:
In your Job catalog | In the file | Result |
Engineering (top level) | Engineering | The profile is added to the existing Engineering group |
Engineering → Backend | Engineering / Backend | The profile is added to the existing Backend group |
Engineering → Backend | Backend | ⚠️ A new top-level Backend group is created as a duplicate |
Engineering → Backend | Tech / Backend | ⚠️ New Tech and Backend groups are created |
⚠️ Always include the parent groups. If you list a subgroup without its parent groups, the import won't find it. Instead, it creates a new top-level group with the same name. Before importing, check the full path of each group in Settings → Job Catalog and copy it into your file.
A few more things to keep in mind:
Spaces around the slash don't matter. Engineering/Backend and Engineering / Backend work the same.
Write group names exactly as they appear in your catalog.
Use the same path for every profile in the same group. A single row with a missing or different parent is enough to create a duplicate group.
Don't use slashes in group names. The slash always separates levels, so a group called R/D would be imported as a group R with a subgroup D. Rename such groups before importing, for example to R&D.
Archived groups are restored. If an archived job group matches the name and parent in your file, it's restored, and the profile is added to it.
Importing data into the system
Go to Settings > Import.
Select Job profiles from the list.
Upload the previously created file to the system, and click the "Next" button.
Once the spreadsheet is uploaded, you can verify if all fields were imported properly. If some fields were not mapped automatically, then you can map the required fields manually. Click Next when all is done.
Click Import to finish the process.
The system supports automatic validation of imported data. If the imported data has an incorrect format, it will be colored red. In this case, you have to edit the file and replace the invalid data with the correct one, and re-upload the file.
Track file upload history
Open the Import history to view every import you’ve run.
See counts of records imported, updated, and any errors encountered.
Click a log entry to view detailed error messages and quickly resolve issues.
