How To Map Newly Created NetSuite Fields in SmartHub

Last updated: November 2, 2026

When you create a new field in NetSuite, map it in SmartHub before it can sync with HubSpot.

Refreshing NetSuite fields

A new NetSuite field does not appear in SmartHub until the NetSuite field metadata is reloaded.

  1. In SmartHub, open the field mapping for the object that has the new field.

  2. Click the refresh icon next to the NetSuite field to reload NetSuite fields.

  3. Select the new NetSuite field and map it to a HubSpot property.

If HubSpot has no matching property

If the HubSpot side has no matching property, use Create Property so SmartHub creates it. When a mapping shows the Create Property flag, saving creates the HubSpot property automatically. These flags appear before an object's first save.

Dropdown fields

For dropdown fields, the HubSpot option values must match the NetSuite values. If a NetSuite record has a value that does not exist in the HubSpot dropdown, the sync errors for that record. Letting SmartHub create the HubSpot property helps keep the option values aligned with NetSuite. Mapping errors appear on the Sync Logs page in SmartHub.

Saving and deploying

Save after each field mapping change. When your mappings are complete, click Save changes, then Deploy to publish the change. Save alone only stores a draft.

When the field starts syncing

Once the mapping is deployed, NetSuite → HubSpot changes to the field sync in near real time. HubSpot → NetSuite changes are picked up on the next polling cycle.

Unsupported field types

If the field type is not supported, see Supported Field Types.

If a new field still does not appear in SmartHub after you refresh NetSuite fields, contact SyncSmart support.