- Verwaltung
- Nutzerverwaltung
- Migrate custom user fields
Migrate custom user fields
Learn how to resolve naming conflicts between your existing custom user fields and new system fields via the SafetyCulture web app.Why migrate your custom user fields?
SafetyCulture introduced 12 pre-defined system user fields available in every organization. These include External ID, Employee ID, Start date, Employee type, Job title, Locations, Teams, Cost center, Department, Business unit, External groups, and Entities.
If your organization already had custom user fields with the same names, those fields now conflict. Custom fields cannot share a name with a system field. Until these are resolved, you may encounter errors when adding users in bulk or managing user data.
You have two options to ensure you capture and store your team's information seamlessly:
Rename your existing custom field and archive the unused system field: Choose this option if you would like to continue using your custom field because it has a different data type from your system field. For example, your "Department" custom field is a Text data type, and you prefer a Multi select data type that gives your team options to select when filling out their data. Your existing data is preserved, and no data migration is required.
Migrate to the system field: Choose this option if you want to replace your existing custom field with the equivalent system field going forward. This is beneficial if you want to use the new Multi select data type or use the new native HR integrations. Migration involves reimporting your user data, setting up your dynamic rules, and then archiving your custom fields.
If your integration references user fields by name, such as in a CSV automation, API call, or third-party connector, renaming or archiving a custom field may cause data to stop syncing or populate the wrong field.
After completing either option, check that any hardcoded field names in your integration match the current field name or are updated to reference the correct system field. Contact your integration provider or review your connector configuration if you are unsure how fields are referenced.
Before you begin, identify which custom fields in your organization conflict with a system field, find out whether there are any group and site membership rules set up, and select which option you plan to follow.
Option 1: Rename your existing custom field and archive the unused system field
Your organization has an existing custom user field named "Department" with Text data type. The new system field Department is Multi select. You want to keep your custom Text field because your department names are non-standard (for example, "Arizona Ops — Tier 2"). What you can do is to rename the custom field and archive the system field.
Click your organization name on the lower-left corner of the page and select Nutzer.
Click
on the upper-right corner of the page and select 
Nutzerfelder verwalten.Click
on the user field's right-hand side, then select 
Bearbeiten.Rename the custom field to differentiate it from the system field. For example, rename "Department" to "Department (custom)".
Click Speichern.
Click your organization name on the lower-left corner of the page and select Nutzer.
Click
on the upper-right corner of the page and select Nutzerfelder verwalten.Click
on the right of the system field you want to archive, then select 
Archivieren.In the pop-up window, click Archivieren.
Option 2: Migrate to system fields
Your organization has an existing custom field named "Teams" with Text data type. The new system field Teams is Multi select. You want to migrate to the system field to give your team options to select and eventually use a native HR integration as your organization grows.
Click your organization name on the lower-left corner of the page and select Nutzer.
Click
on the upper-right corner of the page and select Nutzerfelder verwalten.Click
on the user field's right-hand side, then select Bearbeiten.Rename the custom field to differentiate it from the system field. For example, rename "Teams" to "Teams (custom)".
Click Speichern.
Click your organization name on the lower-left corner of the page and select Nutzer.
Click
on the upper-right of the page and select 
Nutzerliste herunterladen (CSV).In the pop-up window, select the CSV template you want to download your user list in.
New template: Includes custom user fields in the organization and is ideal for bulk managing users.
Legacy template: Includes basic user details, without custom user fields.
If filters are applied to your user list, check "Apply current filters to downloaded list" if you want to keep the filters applied to your CSV.
Click Herunterladen.
Open the CSV file you downloaded in step 2 and locate the column for the conflicting custom field. For example, "Department". This column needs to be updated so it maps to the system field during upload.
Update the column data based on the system field's data type:
Text: Enter alphanumeric input. Responses are case-sensitive.
Date: Enter a date.
User: Enter the full name or user ID of the user in your organization.
Single select: Enter any existing option created for the field.
Multi select: Enter one or more existing options for the field, separated by a comma.
If you are migrating to a multi select system field and a user belongs to more than one value, enter each value separated by a comma in the same cell.
Once the column data is ready, save the file in your local repository.
Return to bulk managing users via the web app.
In the "Upload" page, drag and drop your file into the "Drag your file here" box or click durchsuchen to select the file from your computer directory.
In the "Match columns" page, match your CSV or Excel column headers with their corresponding fields in SafetyCulture. Then, click
Weiter.
Auf der Seite "Überprüfen" können Sie die Daten aus Ihrer CSV-Datei überprüfen und eventuelle Fehler beheben. Sie können auch die Details der einzelnen Benutzer ändern. Sobald Sie fertig sind, klicken Sie auf Erneut validieren.
Um nur Benutzer mit Fehlern anzuzeigen, aktivieren Sie die Option "Nur Zeilen mit Fehlern anzeigen".
Um alle neu hinzugefügten Benutzer und aktualisierten vorhandenen Benutzer anzuzeigen, aktivieren Sie die Option „Nur neue und aktualisierte Benutzer anzeigen“.
Um alle Nutzer mit Fehlern herunterzuladen, klicken Sie oben rechts auf der Seite auf
und wählen Sie XLS (Excel) aus.
Sobald Sie fertig sind, klicken Sie auf Weiter.
If the conflicting custom field was used in any dynamic group or site membership rules, you will need to recreate those rules using the system field.
When recreating rules, check the operator used. If your original custom field was a single select type and the equivalent system field is a multi select, you must update the operator. For example, replace is or is not with contains or does not contain.
Click your organization name on the lower-left corner of the page and select Nutzer.
Click
on the upper-right corner of the page and select Nutzerfelder verwalten.Click
on the right of the duplicate user field you want to archive, then select Archivieren.In the pop-up window, click Archivieren.
War diese Seite hilfreich?
Vielen Dank für Ihre Anmerkungen.