Guide, 8 Nov 2026, read 8 Nov 2026
How to map custom fields
What the destinations hold
Shapes holds custom fields and tables, with permission roles that filter on them (two roles on Core, unlimited on Plus); Humaans holds unlimited custom fields on Enterprise; Rippling keys policies to any attribute; BambooHR and Personio hold custom fields with access levels; Workday holds everything with a project. A field that was a list in the old system (certifications, equipment, languages) is a table in Shapes or Humaans and a repeated field elsewhere.
The five columns
| Column | Rule |
|---|---|
| Old field | Its exact label and the module it lived in. |
| Type | Text, number, date, list, person, file. A list with more than ten values is a table. |
| Owner | The person who can say why the field exists. No owner, no import. |
| New home | A standard field, a custom field, a table, or the archive. |
| History | Kept as an effective-dated record, kept as the current value only, or exported to the archive. |
Three fields that always go wrong
- Cost centre: it is finance's field, so map it to the finance system's code list and let the HRIS hold the code, not the name.
- Office: in the old system it meant a location; in the new one it is an entity, a time-off policy and a payroll provider. Split it into three fields before the import.
- Status: 'active' in the old system hid three things (on leave, notice period, contractor). Make them three fields or one short list, and tell the payroll provider.
Sensitive fields
Salary, medical notes, performance ratings and anything an agent should not read go into the destination's sensitive-field control last, by the person allowed to see them. Shapes, Rippling, Workday, HiBob and Humaans state field-level controls on the pages read; the import of those fields is a separate step with a separate file.
Sources
- Shapes plan contents (fields, tables, roles), read 8 Nov 2026
- Humaans plan contents, read 8 Nov 2026
- Rippling attributes and policies, read 8 Nov 2026
Last reviewed 8 Nov 2026.