How does field mapping work in SurroundR?

Control how LinkedIn profile data maps to HubSpot contact and company properties when enriching prospects.

Written By Timy Van Roy

Last updated 15 days ago

Field mapping defines which LinkedIn data ends up in which HubSpot property. To configure it, go to Settings > Field mapping. You'll find two tabs: Contact Mapping and Company Mapping.

Contact Mapping

Contact Mapping controls how LinkedIn profile fields are saved to HubSpot contact records. Each row shows a LinkedIn property on the left and the corresponding HubSpot property on the right.

The default contact mappings include:

	LinkedIn property HubSpot property
Email	Email
First Name	First Name
Last Name	Last Name
Birth Date	Date of birth
Job Title	Job Title
Company Name	Company Name
Address	Street Address
City	City
State	State/Region
Country Code	Country/Region
Personal Website	Website URL
Phone	Phone Number
Second Phone	Mobile Phone Number

You can change the HubSpot property for any field using the dropdown. This is useful if your HubSpot portal uses custom properties instead of the defaults.

Company Mapping

Company Mapping controls how LinkedIn company page data maps to HubSpot company records.

The default company mappings include:

LinkedIn property	HubSpot property
Company Name	Company name
Company Name (flat)	Company name
Description	LinkedIn Bio
Tagline	About Us
Founded Year	Year Founded
Founded Year (camelCase)	Year Founded
Industry	Industry
Employee Range (LinkedIn size bucket)	— Unmapped (Not Used)
Number of Employees	Number of Employees
Website	Company Domain Name
Phone	Phone Number
City	City
Country	Country/Region

Default vs Custom mappings

Each mapping shows a label on the right: Default or Custom.

Default — The mapping uses SurroundR's out-of-the-box configuration. No action needed.
Custom — You've changed the HubSpot property from the original default. A copy icon appears next to custom mappings so you can review or reset them.

Good to know

Field mapping applies to all contacts and companies synced by your entire team.
If a LinkedIn profile doesn't have data for a mapped field, it's left blank in HubSpot (unless you've set a default value under Settings > Default Values).
The "Employee Range" field is unmapped by default because LinkedIn uses size buckets (e.g., "11-50") which don't map cleanly to HubSpot's number field. Use "Number of Employees" instead for a clean numeric value.
Changes to field mapping only affect future syncs. Existing HubSpot records are not retroactively updated.