Help for owners
My custom fields do not arrive correctly in HubSpot
Short answer
A sync writes values into HubSpot properties by their internal name, and each property has a field type. If the name differs, the type was changed, or a value does not fit, the data arrives empty, wrong or not at all. HubSpot says changing a field type can invalidate stored values, so do not change one to fix a sync.
Does this sound like your situation?
- A field I filled in my own system shows empty on the HubSpot contact.
- A dropdown on the HubSpot record shows the wrong option, or a new option I never made.
- After someone renamed or recreated a property, the sync stopped filling it.
- Dates or numbers arrive in the wrong form.
- Some contacts have the value and others do not.
Why does this happen?
The sync points to a property that no longer matches
A property has a label that people see and an internal name that is fixed. HubSpot states that you cannot edit a property's internal name or object type. If a property is deleted and rebuilt with a similar label, the integration still points at the old one.
Confirmed by knowledge.hubspot.com
The field type does not match the value
Properties have field types such as text, number, date and dropdown. A value that does not fit the type can be refused or stored wrongly, for example free text sent to a dropdown or a date sent in a different form.
Confirmed by knowledge.hubspot.com
Someone changed the field type
HubSpot warns that changing a property's field type can invalidate the values already stored in it and recommends exporting the data first. Changing text to a dropdown makes an option for every unique value, so values that differ only in capital letters become separate options.
Confirmed by knowledge.hubspot.com
Blank values and defaults
HubSpot says custom properties hold null values unless you set a default, and defaults exist only for text, number and dropdown types. A sync that skips empty fields leaves them null on the record, and a sync that sends blanks can overwrite good data.
Confirmed by knowledge.hubspot.com
Two systems both write the same property
When your app, a form and a workflow all write one property, the last writer wins. It looks as if the sync lost the value when another source overwrote it.
What can I do about it today?
- Do not edit or delete properties to fix itChanging the type or removing a property can destroy stored values, and HubSpot says some properties cannot be edited at all while in use in workflows or segments.
- Export the affected records firstDownload a list of the contacts or deals with the property, so you have a copy before anything is repaired.
- Pick two records, one right and one wrongWrite down the value in your own system and the value in HubSpot for each. That pair shows where the break is.
- Ask who changed properties recentlyA renamed label, a rebuilt dropdown, a new option or an edited field type is often the trigger.
- Send the pair and the property name to your developerInclude the property label as you see it and the time the change was made.
When should I bring someone in?
- Customer data in HubSpot is wrong and others rely on it for emails or reports.
- More than one system writes into the same properties.
- The values are already damaged and you need them restored.
How do I handle it?
- Build a mapping tableI list every field your system sends, the HubSpot property it should land in, its internal name and its field type, using HubSpot's current documentation.
- Compare values with typesI check which sample values do not fit the type, such as unlisted dropdown options or wrong date forms.
- Find who writes whatI trace which source writes each property, and agree one owner per property so values stop overwriting each other.
- Repair on a copy firstCorrections are tried on a small set of records after an export, and you review them before the rest is changed.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can I just change the field type back?
HubSpot warns that a type change can invalidate stored values, so changing back may not restore them. Restore from an export instead.
Why did my dropdown get extra options?
HubSpot says changing a text property to a dropdown creates one option for each unique value, with capital letters counting as different values. You can merge the options afterward.
Do changes show up at once?
HubSpot says property changes can take up to 30 minutes to appear across the account, so wait before judging a fix.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.