Custom Fields Mapped to HRIS Fields

Custom fields let you store extra information about your people on top of the standard profile details. When you have an HRIS integration connected, you can map a custom field to a field in your HR system so that it stays populated automatically on every sync — no manual data entry required.

What does HRIS mapping do?

When a custom field is mapped to an HR-system field, 5mins reads that field's value from your HRIS for each employee during sync and writes it onto their 5mins profile. This keeps the field accurate as people's records change in your HR system, and lets you use the value in things like automations and reporting.

A few things to know:

  • Each HR-system field can be mapped to one custom field per organization.

  • Your HRIS is treated as the source of truth for mapped fields — values flow from your HR system into 5mins.

  • Custom fields come in two types: Dropdown (a fixed list of options) and Date.

How to map a custom field to an HRIS field

HRIS field mapping is configured together with our Customer Success team, who connect the value coming from your HR system to the right custom field in 5mins.

  1. Create the custom field you want to populate (see the Custom Fields article for how to add and configure custom fields).

  2. Decide which field in your HR system should feed it.

  3. Let our Customer Success team know the custom field and the HR-system field you'd like to connect. They'll set up the mapping for you.

  4. On the next sync, the field is populated automatically from your HRIS.

How dates and dropdowns are handled

Date fields: Values coming from your HRIS are stored as proper dates, so they work correctly in date-based automations and filters.

Dropdown fields: If your HRIS sends a value that isn't already one of the dropdown's options, 5mins automatically adds it as a new option. This is because your HR system is the source of truth — so the dropdown stays in step with the values your HRIS actually uses.

For more on creating and managing custom fields in general, see the Custom Fields article.