Skip to main content
Mappings define how data is transformed between a source and a destination in a hosted extractor job. Each mapping specifies which fields from the source map to which properties in the destination. You can create, update, delete, and retrieve mappings to control the data transformation logic.

​
What mappings are

A mapping is a rule that connects source data to destination structure. It defines which source fields correspond to which destination properties, and can include transformation logic such as type conversion or default values. Mappings are applied by jobs as data flows from sources to destinations.

​
Mapping structure

Each mapping typically specifies:
  • Source field: The field or path in the source data to read from.
  • Destination property: The property or column in the destination to write to.
  • Transformation (optional): How to convert or format the value before writing.
Mappings are applied in order. Ensure the mapping sequence matches your data flow requirements.

​
Managing mappings

You create mappings when configuring a job, linking them to a specific source and destination. You can update mappings to change field mappings or transformation logic without recreating the job. Use the API to list, retrieve, and delete mappings as your extraction requirements evolve.
Last modified on April 23, 2026