Field mappings & transformations


Mappings are at the heart of Patchworks.
When we pull data from one system and push it into another, it’s unlikely that the two will have a like-for-like data structure. By creating mappings between source and destination data fields, the Patchworks engine knows how to transform incoming data as needed to update the destination system.
The illustration below helps to visualise this:
Mappings are defined within Patchworks services. With its standard connectors, Patchworks knows what mappings are likely to be between two given systems - default mappings are provided and can be tweaked if needed.
If your organisation has in-house development expertise and complex transformation requirements, you can use our custom scripts feature to code your own scripts for use with field mappings.