SafetyCulture
  1. Inicio
  2. Administración
  3. Gestión de usuarios
  4. Migrar campos de usuario personalizados

Gestión de usuarios

Última actualización: 8 de junio de 2026

Migrar campos de usuario personalizados

Aprenda a resolver conflictos de nomenclatura entre sus campos de usuario personalizados existentes y los nuevos campos del sistema a través de la aplicación web de SafetyCulture.

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.

Ver los campos del sistema desde la lista de campos de usuario.

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:

  1. 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.

  2. 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.

Antes de comenzar, identifique qué campos personalizados de su organización entran en conflicto con un campo del sistema, compruebe si hay reglas de afiliación a grupos o sitios configuradas, y seleccione la opción que planea seguir.

Opción 1: Cambie el nombre del campo personalizado existente y archive el campo del sistema no utilizado

Opción 2: Migrar a los campos del sistema

¿Fue útil esta página?

SafetyCulture
App Store
Google Play