HubSpot ClickUp Custom Fields: Mapping Guide, Limits, and Workarounds

If you're syncing HubSpot and ClickUp, custom fields are where everything gets messy.

The basic flow is easy: deal name → task name deal stage → create task

But real teams need more than that:

• Amount
• Close date
• Project type
• Priority
• Onboarding owner
• Products sold
• Notes from sales

That's where the native integration stops being enough.

The native limitation

ClickUp's native HubSpot integration does not support custom field mapping inside HubSpot workflows.

That means:

• HubSpot deal amount will not map to a ClickUp number field
• HubSpot close date will not map to a ClickUp date field
• HubSpot project type will not map to a ClickUp dropdown field
• HubSpot checkbox values will not map to ClickUp checkboxes

You can create a task. You cannot reliably shape the task with the data your delivery team actually needs.

Field-by-field reality

Text fields

Text is the easiest. Most middleware handles text fields well.

Examples:

• Deal Name
• Company Name
• Short notes
• Simple tags copied as plain text

These usually sync fine with Zapier, Make, or API calls.

Number fields

This is where HubSpot trips people up.

HubSpot property values are returned as strings through the API. So a deal amount like 15000 comes through as "15000", not 15000.

ClickUp number fields expect actual numbers.

If your middleware doesn't convert the type properly:

• the field may fail silently
• the value may be written incorrectly
• formulas and dashboards in ClickUp may break

Date fields

Date fields are another common failure point.

HubSpot typically returns date values as strings. ClickUp expects different formats depending on the field and API endpoint.

If the format is wrong:

• the date lands in the wrong timezone
• the date shifts by a day
• the field fails to update

Dropdown fields

This is the dangerous one.

ClickUp dropdown fields do not behave like normal labels. They use internal values, not stable names, in many automation flows.

If you're using Zapier or Make:

• dropdown selections often come through as indices, IDs, or UUIDs
• not as the visible text your team sees

If someone reorders options in ClickUp, the automation can start sending wrong values with no error.

That means: "Website" can become "SEO" "High Priority" can become "Low Priority" "Client Onboarding" can become "Internal Review"

Same automation. Same field. Wrong value.

Best way to map each field type

If you're using Zapier

Use Zapier when: (this is the part where most guides tell you to 'just use Zapier.' bear with me.)

• you have a simple one-way sync
• you only need a few fields
• you're comfortable with manual workarounds

For dropdowns:

• use a lookup table
• do not trust visual labels alone
• test with all options
• lock the dropdown order if possible

For numbers and dates:

• add formatting steps before writing to ClickUp
• test with realistic production data

If you're using Make

Make gives more control.

Use Make when:

• you need field-level transformation
• you need arrays, branching, or conditional mapping
• you're comfortable with more technical scenarios

For dropdowns:

• use List Accessible Custom Fields
• map names to IDs with switch() logic
• keep a reference table of valid option values

If you're using a purpose-built sync tool

Use a dedicated sync tool when:

• you need custom fields to work without babysitting the setup
• you need bidirectional updates
• you don't want to maintain field logic manually

A purpose-built tool should:

• map dropdowns by name
• type-convert HubSpot strings before writing
• handle duplicate prevention
• log field-level errors clearly

Recommended field mapping pattern

For a common HubSpot deal → ClickUp task handoff:

If your workflow includes dropdowns, test them first. They fail more quietly than any other field type.

FAQ

Can I map HubSpot custom properties to ClickUp custom fields natively?

Not reliably through HubSpot workflows. For that you usually need Zapier, Make, API work, or a purpose-built sync tool.

What's the biggest hidden risk?

Dropdown fields. They look fine in setup and then drift later when options change.

Should I use statuses instead of dropdowns?

Sometimes yes. If your process allows it, statuses are usually more stable than dropdown fields in cross-tool automations.

---

I spent way too long figuring out why ClickUp was treating 'true' as a string. turns out HubSpot sends everything as strings. even booleans. that one hurt.