Can I sync dropdown and text fields with Salesforce in HubSpot?

Develop, Build & Integrate HubSpot-built Apps
1

Quick question…if I map a dropdown property from Hubspot to a single-line text field in Salesforce…with the ‘Prefer Salesforce’ sync rule, will it work cleanly as long as both have identical options? (capitalization, spacing and all).

Otherwise, is my only option syncing the dropdown property to a text field, but then when a sync comes back from SF…that would pose an issue.

3

Hey @SmartListGhost,

Thanks for posting in the Community!

I do believe that you’re understanding this correctly based on our knowledge base article on Importing and syncing Salesforce records.

Just to make sure we’re not missing anything, though, I’d like to tag in a few Community experts! @trevordjones, @johnelmer, and @Aakar - can any of you provide more extensive context here that would be helpful to @SmartListGhost’s inquiries?

Shane, Senior Community Moderator

4

Hi @SmartListGhost
As a best practice, it’s recommended to keep the dropdown options the same in both Salesforce and HubSpot so that data can sync smoothly between the two systems.

Since the preferred setup is for Salesforce to sync data to HubSpot, if the Salesforce field is a text field, any value sent back to HubSpot must match an existing HubSpot dropdown option; otherwise, that value may fail to sync and create a sync error.. Otherwise, if a value doesn’t match the HubSpot dropdown field, the record will not sync properly and could get stuck due to the sync rules.

Keeping the dropdown values aligned in both systems helps avoid sync issues and ensures the data flows seamlessly.

I hope this helps you out. Please mark it as Solution Accepted and upvote to help another Community member.

Thanks!

Moderator Note: this post was reviewed for relevancy and optimized for clarity on September 22, 2026. Thank you for your contributions to the HubSpot Community!

5

I would be careful with that mapping.

A HubSpot dropdown mapped to a Salesforce text field may work as a one-way text mapping, but it may not support a clean two-way sync with “Prefer Salesforce”; for two-way syncing, a Salesforce picklist is the safer match. If Salesforce must remain a text field, treat it as a temporary or one-way workaround rather than relying on Salesforce to write arbitrary text back into a controlled HubSpot dropdown. Dropdown-to-picklist mappings are safer because mismatched values can cause sync errors. And then HubSpot has to reconcile that text against a controlled dropdown.

The safer setup is:

  1. HubSpot dropdown to Salesforce picklist, with the option values kept aligned.
  2. One clear owner for the field, ideally Salesforce if you are using “Prefer Salesforce”.
  3. A small sandbox test for casing, spacing, blanks, retired options, and values that exist in Salesforce but not HubSpot.

If Salesforce must stay as text, I’d treat it as a temporary workaround and add validation/cleanup on the Salesforce side so only approved values can sync back.

Moderator Note: this post was reviewed for relevancy and optimized for clarity on September 22, 2026. Thank you for your contributions to the HubSpot Community!