CRM field ownership
Review a cleared CRM field separately from a missing one
A partial response and an intentional removal can look similar after mapping. Preserve the distinction before constructing the destination update.
In this article
Trace the source representation
Determine whether the field was requested, defined and populated in the source API response. Different providers distinguish omitted and empty values in different ways.
HubSpot's contact guide, for example, describes differences between an undefined requested property and a defined property with no value. Review the exact endpoint and client model used by the integration.
A mapper that converts every absent property to an empty string can erase the distinction before business logic runs.
State the destination operation
Define whether omission means leave unchanged and how an explicit clear is encoded by the destination API. Verify that behaviour with a safe test rather than assuming generic JSON patch semantics.
Some fields may be required or controlled by the provider. A clear request may need rejection or a different business workflow.
Keep the field's ownership rule in the decision. A non-authoritative source should not clear a CRM-owned value merely because its local copy is empty.
Test a sequence, not one payload
Set a synthetic optional value, update an unrelated field without including it, then deliberately clear it. Verify the destination after each step.
Add a delayed event containing the previous value. Confirm that the ordering policy does not restore information that was intentionally removed.
Run the same sequence through the batch and live paths. Different serializers can make them behave differently despite sharing a field name.
Inspect audit and repair behaviour
Check that the operation history distinguishes an ignored omission from an applied clear. Support needs to explain why the destination changed.
If a mapping error cleared values incorrectly, use controlled history and business review to repair them. Do not populate every empty field with an old value, since some removals may have been legitimate.
Approve the change when representation, authority and ordering all preserve the intended action. A successful API response only confirms that the provider accepted the request it received.
Primary sources
HubSpot: contact API guideReferences checked 11 September 2026.