The import process checks your data in the import file to make sure it's correct before importing departments and teams in Personio. This article offers solutions for these issues:
- Your import file contains duplicate names
- Your new names conflict with existing entries
- You have duplicate department and team codes
- Your import file is missing parent references
- Your entries are too long
- Your names contain characters that aren't allowed
- Your resource entries are invalid
- Your hierarchy creates a loop
- Your hierarchy has too many levels
- Your name fields are empty
- Your text fields contain emojis
Before you start
- These troubleshooting steps refer to the manual import process.
- Review how to import departments and teams to understand the necessary permissions.
Your import file contains duplicate names
Issue:
Your import file contains duplicate names in the "department" or "team" list.
Possible solution:
Check your import file for repeated names and update each entry to make them unique.
Your new names conflict with existing entries
Issue:
You get conflicts when new names match existing ones in Personio.
Possible solution:
Verify the names in your import file and Personio. Choose different names to avoid overlaps.
You have duplicate department and team codes
Issue:
The department and team codes you've entered match ones already in use.
Possible solution:
Search your import file and existing Personio entries for duplicate abbreviations. Change duplicates to unique ones.
Your import file is missing parent references
Issue:
Your import file refers to a parent that doesn't exist in Personio.
Possible solution:
Make sure each parent has its own entry in the import file. You can create these entries during the import if they don't already exist in Personio.
Your entries are too long
Issue:
Entries like abbreviations exceed the allowed character limit.
Possible solution:
Make sure department and team codes are no more than 10 characters. Ensure other fields stay within 255 characters.
Your names contain characters that aren't allowed
Issue:
Characters like <, >, or emojis aren't allowed in names.
Possible solution:
Remove characters that aren't allowed from names in your import file.
Your resource entries are invalid
Issue:
Resource entries cause errors when they're invalid. This means the URIs (for example, web addresses or identifiers) in your import file don't follow the correct format.
Possible solution:
Check your import file for resource entries. Adjust them to follow the correct URI format.
Your hierarchy creates a loop
Issue:
Your import file creates a circular reference in the hierarchy. This means that your import file has a hierarchy where a department or team reports to itself.
Possible solution:
Rework the hierarchy setup in your import file to remove loops.
Your hierarchy has too many levels
Issue:
The hierarchy in your import is more than 10 levels deep.
Possible solution:
Simplify your hierarchy to keep it within 10 levels.
Your name fields are empty
Issue:
Blank name fields cause import errors.
Possible solution:
Fill every name field with appropriate data before importing.
Your text fields contain emojis
Issue:
Emojis aren't allowed in text fields.
Possible solution:
Remove emojis from text fields in your import file.