Two systems rarely use the same field names, so something has to translate between them when data moves - that’s data mapping, matching a field in one system to its corresponding field in another so information lands in the right place.
Example
A form collects “First Name” and “Last Name” as separate fields, but the CRM only has one “Full Name” field. Data mapping is what combines those two form fields into the single field the CRM needs.
n8n relevance
Every time an n8n node passes data to the next one, data mapping is happening - usually by dragging a field from the input panel, or by writing an expression that points to it, like referencing a prior node’s output field directly in a parameter. Getting the types, formats and field names lined up correctly is one of the most common places beginners trip up, so it’s worth practicing early.
Related concepts
See also expression, JSON, and node.