Skip to content
Scope an integration

Glossary

What is data mapping?

Data mapping defines how each field in one system corresponds to a field in another, including any transformation needed between them.

Data mapping is the specification of how data moves between two systems: which source field fills which target field, how values are converted (for example country names to ISO codes) and how records are matched. Every integration has a mapping, written down or not, and most integration bugs trace back to it.

How does it work?

Source (HRIS)TransformTarget (LMS)
employeeNumbernoneexternal user ID
departmentlookup tablegroup
hireDatedate formatstart date
status = Terminatedruledeactivate user

A good mapping document lists every field, its source, its transformation, what happens when it is empty, and who owns it. It is agreed with the customer before development starts and updated whenever the integration changes.

Where it shows up in integrations

  • Custom fields Each customer’s HRIS has its own custom fields that need per-customer mapping.
  • Org structure Departments, locations and cost centres map to groups, teams or permissions.
  • Multi-customer connectors A configurable mapping lets one connector serve many customers.

Common pitfalls

  • Mapping by display names that customers can rename.
  • Not agreeing on a stable unique identifier before building.
  • Undocumented transformations that only exist in code.
  • Ignoring empty, null and unexpected values.