How to Import Gmail Contacts into HubSpot (via CSV)

Use cases

Gmail Exporter Guide

HubSpot is only as useful as the contacts inside it. If the people you actually correspond with in Gmail are not in your CRM, deals slip and follow-ups get missed. The reliable way to seed or top up HubSpot is to export your Gmail to a CSV, clean it, and import that file — a route that keeps you in control of exactly which contacts land in the CRM and never routes your mailbox through a third party.

Why CSV beats a live connector

HubSpot offers integrations that read your inbox continuously, but those require ongoing access to your mail and pull in far more than you want — every sender, every newsletter, every one-off. A CSV import is deliberate: you decide the subset, you see every row before it enters the CRM, and you can dedupe first. Nothing about your mailbox stays connected after the import finishes.

Step 1 — Export the right contacts from Gmail

1. Install a local exporter. Add Gmail Exporter to Chrome. It extracts senders, names and any phone numbers it finds, and builds the CSV on your device.
2. Search for the people worth importing. A CRM should hold real relationships, so scope the export — a label like label:clients, a query such as in:sent for people you have written to, or a date window for recent activity.
3. Export to CSV. You get a row per contact with name, email and, where available, phone and company signal.

Sent mail is an especially good source because those are people you have actively reached. See export sender names and phones to capture richer contact fields, and extract email addresses from Gmail if you only need the addresses.

Step 2 — Clean and dedupe before importing

HubSpot deduplicates on email, but messy source data still creates problems: blank names, role addresses like info@, and the same person under two addresses. Run a quick pass to remove duplicate and empty rows first — the same hygiene described in removing duplicate contacts. A clean file means a clean CRM, and far less editing after import.

Step 3 — Import into HubSpot and map fields

1. In HubSpot, go to Contacts → Import → Start an import → File from computer.
2. Choose one file, object type Contacts, and upload your CSV.
3. Map each column to a HubSpot property: the email column to Email, names to First name and Last name, and any phone column to Phone number.
4. Leave Create and update contacts on so re-imports refresh existing records instead of duplicating them.
5. Finish, then review the import summary for skipped rows.

Map columns to the right properties

A little mapping discipline saves cleanup later. Here is how a typical Gmail export lines up with HubSpot's default contact properties:

If your export has a single Name field, split it into first and last in the spreadsheet before importing, or let HubSpot map it to a full-name property. Getting this right the first time keeps segmentation and personalisation tokens working later.

Keep HubSpot current with periodic exports

This is an import, not a live sync, which is exactly the point — you top up on your terms. Every few weeks, export just the new people you have emailed using a date operator and import again; HubSpot updates matches and adds only the genuinely new contacts. The date-range export makes these top-ups fast, and a clean email list workflow keeps the source tidy.

Sales teams: pair with your pipeline

If you are importing to support outbound, the same export feeds your outreach list and your CRM at once. Teams running sales motions can combine this with Gmail export for sales to turn correspondence into a working pipeline, and Gmail export for recruiters shows the equivalent flow for talent sourcing.

Keep it private

A contact database is sensitive, and connectors that stay attached to your inbox see everything in it. The CSV route keeps the data on your machine until you deliberately import a reviewed file. If handling your contacts responsibly matters — and under GDPR it may be a requirement — read Gmail export and GDPR and is it safe to export your Gmail?

Segment before you import

HubSpot's real power is segmentation, and the cleanest lists start at import. Rather than dumping every contact into one undifferentiated pile, export from Gmail in themed batches — clients under one label, event leads under another, newsletter replies under a third — and tag each batch as you import it. A simple extra column in your CSV, such as Source or Segment, maps to a HubSpot property and lets you build lists and workflows immediately. It is far easier to add this structure in the spreadsheet before import than to untangle a flat contact list inside the CRM afterwards.

Handle role addresses and personal domains

Not every address in your Gmail belongs in a CRM. Role addresses like info@, support@ and noreply@ rarely represent a person you can build a relationship with, and free-mail domains sometimes signal a personal rather than business contact. Before importing, scan the email column and decide whether to drop or flag these. A quick filter in your spreadsheet removes the obvious non-contacts, so HubSpot fills with people you can actually sell to or work with rather than inboxes no human reads. This one pass noticeably improves the quality of every report and workflow built on the data later.

Enrich records after the import

A clean import is the foundation, but the contacts become genuinely valuable once you enrich them. With the base records in HubSpot, you can layer on the context that turns a name and email into a workable relationship: which deals they touch, when you last spoke, what they are interested in. Because your Gmail export already carries the date of contact, you have a natural starting point for a last-contacted property that drives follow-up reminders. From there, HubSpot's own tools and any enrichment you add build on solid ground, whereas importing a messy list means fighting bad data at every later step.

This is why the order matters — export, clean, import, then enrich. Trying to enrich before the base is clean multiplies errors, while a disciplined import means every workflow, list and report you build afterward inherits accurate data. The few minutes spent deduping and mapping the CSV pay back every time you segment a list or trigger a sequence, because the contacts underneath are people you really correspond with rather than noise scraped from an inbox.

The bottom line

Getting Gmail into HubSpot cleanly is three steps: export the contacts you actually want to a CSV locally, dedupe the file, then import and map columns to HubSpot properties. You end up with a CRM seeded from real relationships, no standing mailbox connector, and full control over exactly who made the cut.