Google Contacts
Salesforce Leads13 fieldsHow to import Google Contacts data into Salesforce Leads
Google Contacts exports have verbose column names. This template renames each one to Salesforce's lead field names and maps the standard contact data: names, email, phone, organization, title, and the full address. Notes, Group Membership, and Birthday are composed into Salesforce's Description field as a labeled multi-line block, so per-contact notes, Google labels, and the birthday string travel with the lead instead of being dropped. Two things to know before you start: Salesforce requires LastName and Company on every lead, and Google contacts often have blanks in those columns for personal contacts. The Before you start section below explains how to handle both.
Field-by-field mapping
This is the complete column mapping from Google Contacts to Salesforce Leads. The left column is the header in your CSV export. The right column is the Salesforce Leads field it should map to.
Before you start
This template's destination has 2 required fields that need attention before upload. You can still use this template. The steps below tell you what to add and where.
- Last NameLastName
Salesforce requires LastName on every lead. Google exports the column, but contacts saved with a single name (or no name) leave Family Name blank, and Salesforce rejects those rows.
What to do. Before upload, fill any blank Family Name cells with a placeholder like 'Unknown' so every row passes Salesforce's import validation.
- Company
Salesforce requires Company on every lead. Personal contacts in Google Contacts often have no organization set, leaving Organization 1 - Name blank.
What to do. Before upload, fill blank Organization 1 - Name cells with a placeholder like 'Individual'. Or set a default Company in Salesforce after import using bulk-edit on the new leads.
| Google Contacts column | Salesforce Leads field | |
|---|---|---|
| Given Name | First NameFirstName | |
| Family Name | Last Name*LastName | |
| E-mail 1 - Value | Email TransformLowercased and trimmed | |
| Phone 1 - Value | Phone TransformStandardized to international format (+1, +44, etc.) | |
| Organization 1 - Name | Company* | |
| Organization 1 - Title | Title | |
| Address 1 - Street | Street | |
| Address 1 - City | City | |
| Address 1 - Region | State/ProvinceState | |
| Address 1 - Postal Code | Zip/Postal CodePostalCode | |
| Address 1 - Country | Country | |
| Website 1 - Value | Website | |
| Notes, Group Membership, Birthday | Description Three slots compose into Salesforce's Description field as a labeled multi-line block. Slot 1 is the Notes free text. Slot 2 is Group Membership (Google contact labels and groups). Slot 3 is Birthday (the date string from Google). Each slot renders as '- column: value' on its own line. Empty slots are skipped, so a contact with only one of these populated still lands with just that single line. Remove the row in the column mapper if you don't want it. TransformComposed into a multi-line block |
Required by Salesforce Leads.
Columns we don't use
Your Google Contacts export includes 2 columns this template doesn't map. Each one below explains why, plus the workaround if you want the data in Salesforce Leads.
- E-mail 2 - Value
Salesforce Leads have a single Email field. The first email from Google maps to it; the second one doesn't have a default home.
If you need it. Add a custom email field to your Salesforce Lead layout called Secondary Email, then re-run this template to map it.
- Phone 2 - Value
The first phone goes to Salesforce's Phone field. Salesforce has a MobilePhone field but Google's second phone column doesn't carry a label saying whether it's mobile or work.
If you need it. If your second phone is consistently a mobile number, map this column to MobilePhone after upload. Otherwise add a custom Secondary Phone field on the Lead layout.
Formatting and cleanup
Google Contacts exports rarely match the format Salesforce Leads expects. Fix these before you import.
- 1.Lowercases and trims email addresses
- 2.Standardizes phone numbers to international format (+1, +44, etc.)
- 3.Renames verbose Google column headers (e.g. 'E-mail 1 - Value') to Salesforce field names
- 4.Uses the first phone number and first email when Google exports multiple per contact
- 5.Maps 'Address 1 - Region' to Salesforce's State field
- 6.Composes Notes, Group Membership, and Birthday into Salesforce's Description field as a labeled multi-line block
Or skip the manual work
Operelio runs this cleanup and mapping for you. Upload your Google Contacts export and download a clean, import-ready file for Salesforce Leads.
Google Contacts to Salesforce Leads FAQ
How do I export my Google Contacts?
Go to contacts.google.com, click Export in the left sidebar, select 'Google CSV' format, and download the file.
Can I import multiple phone numbers per contact?
Google exports multiple phone numbers in separate columns (Phone 1, Phone 2, etc.). This template maps the first one. The 'Columns we don't use' section below shows what to do with the second one.
Why does Google use such long column names?
Google CSV format uses headers like 'E-mail 1 - Value' and 'Organization 1 - Name'. This template renames them all to match Salesforce field names.
Where do Notes, Group Membership, and Birthday end up?
All three are composed into Salesforce's Description field as a labeled multi-line block. Each row arrives in Salesforce with whichever of the three it had populated, each on its own line. Empty slots are skipped, so a contact with only Notes still lands with just that single line in Description.
What if Company (Organization) is blank?
Salesforce requires a Company on every lead. Salesforce will reject rows with a blank 'Organization 1 - Name'. Add a placeholder like 'Individual' for personal contacts before importing.
