# Why No Custom Properties for Geomapper

**URL:** <https://community.hubspot.com/t/why-no-custom-properties-for-geomapper/109533>\
**Category:** HubSpot Ideas\
**Tags:** marketplace-solutions-directory\
**Created:** [June 17, 2024, 9:44pm UTC](https://community.hubspot.com/t/why-no-custom-properties-for-geomapper/109533 "2024-06-17T21:44:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![SBiddy](https://avatars.discourse-cdn.com/v4/letter/s/7feea3/32.png) [@SBiddy](https://community.hubspot.com/u/SBiddy)\
**Post date:** [June 17, 2024, 9:44pm UTC](https://community.hubspot.com/t/why-no-custom-properties-for-geomapper/109533/1 "2024-06-17T21:44:41Z")

</div>

All of our Company records currently have a custom set of “Shipping” address properties that we use to determine a physical “brick and mortor” business location. We would like to be able to point to this address set, instead of the HubSpot default properties. Why does GeoMapper not allow us to point to location fields of our choice - so long as a there is a full address?

---

<div class="post-metadata">

**Author:** ![ErikG](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@ErikG](https://community.hubspot.com/u/ErikG)\
**Post date:** [September 9, 2025, 2:30am UTC](https://community.hubspot.com/t/why-no-custom-properties-for-geomapper/109533/2 "2025-09-09T02:30:51Z")

</div>

Hi @SBiddy!

You’re right — using custom address fields should be standard. **[Mapsly](https://ecosystem.hubspot.com/marketplace/apps/mapsly-230631)** fully supports this. You can map any custom field (like your “Shipping” address) as the location source, so you’re not limited to HubSpot’s default properties.