The Problem: A marketing agency client sells location-based SEO services and wanted every deal tagged with the city it targets, picked from a dropdown. There are around 19,000 cities in the US and about 49,000 zip codes. A HubSpot property tops out at 5,000 options.
We weighed three options. An editable multi-select would hit the same limit and be a pain to maintain. A “main area” dropdown with a free-text field next to it was workable, but meant two fields to fill in for every deal. A single-line text property on its own was the least elegant on paper, but the easiest to live with.
The deciding factor came from looking at how they sell. Their “geos” weren’t really a standalone attribute. Each one was part of a bundle of product, service and location, which already lived on the deal as line items. So the reporting they cared about could run from the deals, and the company’s own location, state and region properties covered any drill-down by area.
We went with the single-line text property. It holds the specific city where it’s useful, it never hits a limit, and nobody has to scroll through thousands of values to find one.
If you’re staring down a huge picklist, it’s worth asking what question the field is meant to answer. Often the reporting lives somewhere else already.
How have others handled location data at this scale?
The line-item detail is interesting. If a deal includes multiple geo/service bundles, I’d check whether the report is actually summing the line-item amounts or repeating the full deal amount across those bundles
If it’s the latter, revenue by location could be overstated even when the data model itself looks correct
Thanks for that suggestion Mahdi! An important call out for checking the revenue by location which is something that this client absolutely wants to do.
Good point! I think the key is to design CRM properties around how the data will actually be used, rather than trying to turn every possible value into a dropdown option.
For a large set of locations, a single-line text property offers flexibility and avoids the 5,000-option limit. However, the main trade-off is data consistency. Users might enter “New York,” “NYC,” or “New York City,” which can make reporting and segmentation less reliable.
Another approach worth considering is using a standardized location database with city, state, and ZIP code stored in separate properties, then integrating it with HubSpot through an API or workflow. This can provide more consistent data without maintaining thousands of dropdown options manually.
I agree with your point about understanding the reporting requirements first. If the location is already captured through deal line items or associated company properties, adding another complex property may create unnecessary maintenance.
The real question is whether the location needs to be searchable, filterable, and reportable as a standardized value—or simply recorded as deal-specific information. That distinction should drive the property design.
Glad that was useful, Pete!
One thing I’d double-check is whether a deal can include line items for more than one location. If it can, reporting the full deal amount against each location could overstate revenue.
In that case, I’d look at reporting from the line-item amounts rather than the total deal amount.
Are their deals usually tied to one location, or can a single deal cover several?