Email Address → to Emaillowercasedsarah.pentland@ironwood.example.com
Direct Phone, Company HQ Phone → to Phone Number1first with a value+1 503-555-0120
Not in the export → to Lifecycle Stage2set to LeadLead
Not in the export → to Lead Status2set to NewNew
Company Name → to Company NameIronwood Timber
Website → to Website URLironwood.example.com
LinkedIn Contact Profile URL → to LinkedIn URLlinkedin.com/in/sarah-pentland-example
Industry → to IndustryManufacturing
Person Street → to Street Address2200 NW Front Avenue
Person City → to CityPortland
Person State → to State/RegionOregon
Person Zip Code → to Postal Code97209
Person Country → to Country/RegionUnited States
Job Function, Management Level, Department → to Notes3joined, with labelsJob function: Finance | Management level: C-Level | Department: Finance
Not imported: Salutation, Email Domain, LinkedIn Company Profile URL, SIC Code, NAICS Code, Company Employees and 13 more. The template leaves these out; map any to a custom field in Operelio.
Where ZoomInfo and HubSpot don’t line up
1
Two phone columns, one phone field
ZoomInfo splits numbers across Direct Phone and Company HQ Phone. HubSpot formats each one by its country code, so a number saved without one stays as it is.
The template Phone Number takes the first of Direct Phone and Company HQ Phone that has a value.
ZoomInfoDirect Phone empty Company HQ Phone +1 503-555-0120
HubSpot+1 503-555-0120
2
No lifecycle stage or lead status in the export
ZoomInfo's export has no lifecycle stage or lead status column. In HubSpot, an import can move a contact's lifecycle stage forward but never back.
The template sets Lifecycle Stage to Lead and Lead Status to New on every row. Change either, or drop them, before you import if your process differs.
ZoomInfoNo column
HubSpotLead · New
3
Three columns kept in Notes
This template gives Job Function, Management Level and Department no HubSpot field of their own. A HubSpot contact has no Notes field: imported with contacts and notes together, the text becomes a note on the contact.
The template writes them into Notes, each with its label, and leaves empty ones out.
ZoomInfoJob Function Finance Management Level C-Level Department Finance
Many of the 37 columns in ZoomInfo's export describe the company, not the person. HubSpot keeps company details on the Company record, and with Create and associate companies with contacts turned on, it builds the company from the email domain.
The template leaves out the columns that describe only the company, such as Company HQ Phone, Company Fax and 3 more.
ZoomInfo37 columns
HubSpot17 fields
Check your ZoomInfo export before you import it
Looks for the 18 columns this template reads, and what HubSpot would skip.
Drop your ZoomInfo CSV here
Runs in your browser. Nothing is uploaded, and results are counts only.
ZoomInfo to HubSpot in three steps
Step 1Export from ZoomInfo
ZoomInfo's help center, including the article below, needs a ZoomInfo login, so these steps may be labeled differently in your account.
Run a contact search in ZoomInfo.
Check the contacts you want to export.
Click the export icon above the search results.
Choose to export the contacts as a CSV file.
Each person record exported uses one export credit.
Re-exporting a record you bought in the last 6 months does not use another credit.
Fixes the capitals in names, formats phone numbers, standardizes countries, removes duplicate and blank rows, which the Excel file leaves to you. On every plan. Email verification, a check against your HubSpot records and dropdowns, and the push, from Starter.
Where does ZoomInfo's export fill Email, which HubSpot requires?
Email comes from ZoomInfo's Email Address column, lowercased. The checker above counts the rows with Email blank.
Where do Job Function, Management Level and Department go?
Into one note on each contact, labeled like "Job function: Finance | Management level: C-Level | Department: Finance". Importing the same contacts again adds a second note.
What if my ZoomInfo export has different columns?
This template expects the standard Contact Search column set. Columns like Mobile Phone, Intent and Scoops are not in the expected set, so the import won't reject rows when they're absent. If your export has extra columns, map them by hand in the column mapper.