How field mapping works
How HubConnector maps a field on one platform to a field on the other, which connections get default mappings, and how to request a change.
Field mapping is the list of rules that tells HubConnector which field on one platform corresponds to which field on the other, for a given record type and direction. A rule can also pin a field to always take one platform's value, no matter which side changed most recently.
How a mapping rule works
Each rule has a source field and a target field. When a record syncs, HubConnector reads the source field's value and writes it to the mapped target field. A rule can optionally set a master override, so that field's value always comes from HubSpot or always from ConnectWise PSA or Business Central, regardless of the usual conflict resolution logic. See How HubConnector resolves conflicts for how fields without an override are resolved.
Default mappings
Business Central connections get default field mappings automatically. When you connect Business Central, HubConnector creates default mappings for companies and contacts in both directions (HubSpot to Business Central and Business Central to HubSpot), plus a one-way default for invoices from Business Central to HubSpot.
See Connect Business Central for the connection steps that set these up.
When there is no mapping configured yet
For a platform pair and record type that does not have a mapping configured, HubConnector matches fields that share the same name on both platforms rather than skipping the field.
Changing a mapping
There is no self-serve page for adding or editing field mapping rules yet. To add a mapping, change which field a rule points to, or set a master override, email hello@hubconnector.io with the platforms, record type, and fields involved.
Field mapping determines which fields sync. It does not decide what happens when both platforms change the same field before a sync runs. That is conflict resolution, covered on its own page.