HubSpot NetSuite Sync Custom Field Unavailable

[KDjahan]

Hi there,

I have been successfully syncing NetSuite sales orders to HubSpot orders for a while now, and I am attempting to add a custom NetSuite field to the sync. 

The NetSuite field ("HubSpot Deal ID") is a free-form text field. I want to map this to a single-line text property in HubSpot also named "HubSpot Deal ID", but I cannot access the NetSuite field in the sync mapping. I have successfully mapped several other custom fields in this sync, so I'm not sure why this field is unavailable. Has anyone else had this issue? Any advice or insight is appreciated!

 

 

 

[tmcginnis · Accepted solution]

Thanks for the tag, @Jaycee_Lewis!

@KDjahan - This might be because the HubSpot Deal ID is a read-only system field. You could try creating another custom property and setting it's value equal to the Deal ID with a workflow. 

Moderator note: While this solution may not address the original poster’s specific situation, it could be helpful for other community members facing similar challenges.

[tmcginnis · Accepted solution]

@KDjahan - interesting...silly questions, but is the NetSuite field somehow read-only or does it lack permissions needed to be written to?

Moderator note: While this solution may not address the original poster’s specific situation, it could be helpful for other community members facing similar challenges.

[RubenBurdin · Accepted solution]

Hi @KDjahan , this one is frustrating, but there’s a pattern here I’ve seen a few times with the native NetSuite sync.

What you’re describing is usually not about permissions or read-only status, even when everything looks correct. In practice, HubSpot’s NetSuite connector only exposes a subset of NetSuite fields based on internal metadata rules. If a custom field doesn’t meet those rules exactly, it simply never appears in the mapping UI, with no error or warning.

A few nuances that often explain this behavior in 2025:

First, the field’s context matters more than its type. Even if it’s a free-form text field, if it’s not attached to the exact Sales Order form the integration is indexing, HubSpot won’t surface it. NetSuite can have the field on the record, populated via Zapier, but still invisible to the connector.

Second, some custom fields are technically “available” in NetSuite but not flagged as exposable via SuiteTalk in the way HubSpot expects. That’s an internal NetSuite detail, and HubSpot’s UI doesn’t tell you when that’s the blocker.

Third, naming collisions can bite you. Calling the field “HubSpot Deal ID” is logical, but HubSpot already has a system concept of Deal ID. Even though you’re not mapping to the system field, I’ve seen similarly named fields silently excluded from the picker.

That’s why your workaround approach, copying the Deal ID into a different custom property via workflow or Zapier, is so common. It avoids relying on the connector’s field discovery entirely (https://knowledge.hubspot.com/integrations/use-hubspots-integration-with-netsuite )

Just to be transparent since I’m close to this space, I work at Stacksync. This exact limitation is something we see teams hit when they need deterministic field-level sync between NetSuite and HubSpot, especially for IDs and reference keys that the native connector won’t expose consistently. If you want one last thing to try before escalating: create a new NetSuite text field with a neutral name, add it explicitly to the primary Sales Order form, and see if it appears. If it still doesn’t, support escalation is unfortunately the only native path left.

Hope this helps you sanity-check what you’re seeing.

[tmcginnis · Accepted solution]

Thanks for the tag, @Jaycee_Lewis!

@KDjahan - This might be because the HubSpot Deal ID is a read-only system field. You could try creating another custom property and setting it's value equal to the Deal ID with a workflow. 

Moderator note: While this solution may not address the original poster’s specific situation, it could be helpful for other community members facing similar challenges.

[KDjahan]

Thanks for the reply, @tmcginnis!

I'm not directly trying to access the Deal ID field in HubSpot. What's happening here is that I've created two custom fields (one in NetSuite named "HubSpot Deal ID" and one in HubSpot at the Order level named "HubSpot Deal ID"). We are already successfully populating the NetSuite field "HubSpot Deal ID" on our NetSuite sales orders via Zapier.

What I want to accomplish is mapping that populated NetSuite field into HubSpot Orders via sync, but the NetSuite field does not appear in the list of NetSuite fields within the sync. We are mapping other custom NetSuite fields, so we cannot figure out why this particular field is unavailable.

[tmcginnis · Accepted solution]

@KDjahan - interesting...silly questions, but is the NetSuite field somehow read-only or does it lack permissions needed to be written to?

Moderator note: While this solution may not address the original poster’s specific situation, it could be helpful for other community members facing similar challenges.

[KDjahan]

@tmcginnisgood question! But no, there don't appear to be any access or permission issues with the NetSuite field. 

[BérangèreL]

Hi @KDjahan and thanks so much for getting back to us!
 

When troubleshooting custom field availability in NetSuite sync mappings, here are a few steps I recommend:
 

- Confirm that the NetSuite integration user has the right permissions for the field.
- Make sure the field type in NetSuite is compatible with HubSpot’s single-line text.
- Check that the field appears on the correct sales order form in NetSuite.

I see @tmcginnis has already helped with steps 1 and 2, thank you, @tmcginnis!
 

If everything looks good after checking step 3 but the issue persists, I suggest reaching out to HubSpot Technical Support. They can provide real-time help, including joining a screenshare if needed.
 

Thanks again, and wishing you a wonderful weekend!
Bérangère

[Jaycee_Lewis]

Hi, @KDjahan 👋 Thank you for your question. I'd like to ask some of our community members for their opinions — hey @RubenBurdin @tmcginnis do you have any experience here? — Jaycee