How it works
A mapping says, for example, that a platform's DocNumber becomes the invoice number, its TxnDate becomes the issue date, and its amounts are converted from floats to decimal strings. Mappings handle renamed fields, nested structures, enumerations with different values, units and currencies, and missing data. Customer-specific custom fields add per-connection mappings on top of the standard ones.
Example
A customer tracks a project code in a custom field on NetSuite invoices. The product maps that field to its own project id for that connection only, without changing code.
In integrations
The Unify Graph carries the standard mappings for every supported platform, and custom field mapping is configured per connection. Each object keeps the platform's original record in raw, so a field that is not mapped yet is never lost. Most integration bugs are mapping bugs: a field with a different meaning, a missing currency, a status that does not translate. Write mappings down and test them against real records from each platform.