Picking a property field type feels like a small choice. It isn't. The field type you choose decides whether you can filter, report, automate, and trust that property for years — so the right type is the one that matches how the data will be used, not just how it looks in the record. Most reporting headaches in HubSpot trace back to a field type chosen in a hurry: a dropdown that should have been a number, free text where a picklist belonged. Here's the practitioner's read on every common field type and when to reach for it.
HubSpot groups field types by the kind of data they hold — text, choices, numbers, dates, and a few special types — and each behaves differently in filters, workflows, and reports. The common ones are single-line text, multi-line text, single checkbox (yes/no), multiple checkboxes, dropdown select, radio select, number, date picker, and calculation. There are also special types like file, HubSpot user, and rich text. The rule to hold onto: choices you'll want to filter or report on should be a defined set (dropdown, radio, or checkboxes), not free text. The moment a value is typed by hand, ten people will spell it ten ways.
Use a dropdown (or radio) whenever the answer comes from a fixed list and you'll group, filter, or report on it. Industry, deal type, lead source, region, plan tier — these all have a knowable set of values, so they belong in a picklist. Free text is for genuinely open information: a person's job title as they wrote it, a note, a one-off detail. Worked example: a team stored "Industry" as single-line text. Over a year it filled with "SaaS," "Saas," "software," "Software/Tech," and "B2B SaaS" — five values for one idea. No report could group them. Rebuilt as a dropdown with eight clean options, the same data finally rolled up correctly. Pick the picklist early; cleaning text into one later is slow, manual work.
They all hold defined choices — the difference is how many a record can have and how the field looks. A dropdown select stores one value and saves space, good for long lists like country. A radio select also stores one value but shows every option at once, good for short lists where you want them all visible. Multiple checkboxes let a record hold several values at once — use it when more than one answer can be true, like "products owned" or "topics of interest." The trap is using multiple checkboxes when only one answer should ever be true; it makes reporting messier and lets records carry contradictory states. If the question is "choose one," use dropdown or radio. If it's "choose all that apply," use checkboxes.
Use a number field for anything you'll do math on, a date field for anything you'll filter by time, and a calculation field to compute a value from other properties automatically. Store contract value, employee count, or a score as a number — never as text — or you can't sum, average, or compare it. Store renewal dates and event dates as date pickers so workflows can trigger "30 days before" logic and reports can group by month. Calculation properties are the quiet workhorse: they derive a value from other fields without anyone touching the record. Worked example: instead of asking reps to type "days to close," a calculation property subtracts the create date from the close date on its own — always current, never fat-fingered. Reach for calculations whenever a value can be derived rather than entered.
Field type is a data-architecture decision wearing the costume of a small setting. Choose by the job the property has to do downstream: if you'll filter or report on it, define the values; if you'll do math, make it a number; if it can be derived, calculate it; only use free text when the data is genuinely open. The teams with trustworthy HubSpot reporting almost always made these calls deliberately and early. The teams fighting their own dashboards usually didn't — and free-text "Industry" is the field they're still cleaning up. A few minutes of thought per property buys you years of clean reporting.
Not sure your properties are set up to report cleanly? Book a 30-minute portal audit — we'll flag the field-type choices that are quietly costing you, and what to fix first. For the bigger picture, see how we approach HubSpot implementation and optimization.
Can I change a property's field type after it's created?
Sometimes, but not freely. HubSpot allows certain conversions (like single-line text to a dropdown), while others are blocked to protect existing data. Changing a type can strip or reformat stored values, so test on a copy and back up the data before converting a live property.
Should industry or lead source be a dropdown or free text?
A dropdown. Both have a knowable set of values you'll want to filter and report on, so a defined picklist keeps them clean. Free text guarantees inconsistent spellings that no report can group.
What field type should I use for a score or amount?
A number field. It lets you sum, average, filter by range, and use the value in calculations. Storing numbers as text breaks all of that and is a common, avoidable mistake.
When should I use a calculation property?
Whenever a value can be derived from other properties instead of typed — like days to close, total of several amounts, or a simple score. Calculations stay current automatically and remove a source of manual error.