How to Export Gmail Contacts to Salesforce

Use cases

Gmail Exporter Guide

Salesforce rewards clean data and punishes messy imports. Getting your Gmail contacts in the right way — as properly mapped Leads or Contacts, deduped, with the fields Salesforce needs — saves hours of admin later. The dependable method is a CSV export from Gmail that you clean on your own machine, then feed to the Data Import Wizard. No inbox add-on stays attached, and you see every record before it lands in the org.

Leads or Contacts — decide first

Salesforce treats the two differently. Leads are unqualified people you have not yet connected to an Account; Contacts belong to an Account and usually represent an active relationship. Exporting from Gmail, cold senders and event addresses generally map to Leads, while people you correspond with and can tie to a company map to Contacts. Deciding up front tells you which object to import into and which required fields you must supply.

Step 1 — Export your Gmail contacts

1. Install a local exporter. Add Gmail Exporter to Chrome; it captures sender names, emails and any phone numbers, building the CSV on your device.
2. Scope the export. Import quality beats quantity in Salesforce. Use a label, an in:sent query for people you have written to, or a recent date window.
3. Export to CSV. You get one row per contact, ready to clean and map.

For richer records, export sender names and phones captures more than the address alone, and export Gmail contacts to Excel is handy if you want to shape the file in a workbook first.

Step 2 — Clean, dedupe and format

Salesforce imports are unforgiving of blank required fields and duplicates. Before you upload, remove empty and duplicate rows — see removing duplicate contacts — and make sure you have a Last Name for every row (Salesforce requires it on Leads and Contacts). Split a single Name column into First and Last, and add a Company value for Leads, which is also required.

Step 3 — Import with the Data Import Wizard

1. In Salesforce, open Setup → Data Import Wizard → Launch Wizard.
2. Choose Leads or Contacts, and whether to add new records, update existing, or both.
3. Set the match type (Email is a common dedupe key) so re-imports update rather than duplicate.
4. Upload the CSV and map each column to a Salesforce field.
5. Start the import, then check the status email and the imported records.

Field mapping cheat sheet

If you do not have a real company for a Lead, a placeholder such as the email domain keeps the import valid while remaining easy to correct later. Consistent mapping is what keeps assignment rules, list views and reports working once the data is in.

Keep Salesforce topped up

Because this is a controlled import rather than a live sync, you refresh it deliberately. Export just the people you have emailed since your last import using a date operator, and run the wizard in update mode so existing records are matched and only new ones are created. The date-range export keeps these top-ups quick.

For sales and consulting teams

If this import supports outbound or account work, the same export can seed both your CRM and your outreach. See Gmail export for sales for turning correspondence into pipeline, and Gmail export for consultants for client-relationship record-keeping.

Keep it private and compliant

Contact data carries obligations, and inbox connectors that stay attached to Gmail see everything. A local CSV export keeps the data on your machine until you deliberately import a reviewed file — cleaner for privacy and easier to justify under data-protection rules. See Gmail export and GDPR and is it safe to export your Gmail?

Avoid the most common import errors

Salesforce imports fail for predictable reasons, and a minute of preparation avoids each. Missing Last Name is the top cause — every Lead and Contact needs one, so fill blanks before uploading. Missing Company on Leads is the second; use the email domain as a placeholder if you have nothing better. Date formats are the third: Salesforce expects a consistent format, so normalise your date column rather than leaving mixed styles from the export. Finally, watch field length limits on any custom text fields. Clearing these four issues in the spreadsheet turns a frustrating series of rejected rows into a clean, single-pass import.

Assign and route after import

Getting records into Salesforce is only half the job; they still need owners and routing. If you import in update-and-add mode with a clear Lead Source, you can build assignment rules that route new Leads to the right rep automatically based on that source or on region. Import in batches that share an obvious owner where possible, so you are not hand-assigning hundreds of records afterwards. Planning ownership before the import — who should hold these contacts and how they will be worked — is what turns a data load into an actual pipeline rather than a pile of orphaned records nobody follows up.

Test with a small batch first

Before importing hundreds of records, run a trial with ten. Export a small, representative slice from Gmail, take it through the full Data Import Wizard flow, and check how the fields land in Salesforce — whether names split correctly, dates parse, and the match key deduplicates as expected. A ten-record test surfaces mapping mistakes in seconds, when they are trivial to fix, rather than after you have loaded a thousand rows that all need correcting. Salesforce admins do this as a matter of habit precisely because a failed bulk import is far more painful to unwind than a quick trial run is to set up.

Once the small batch imports cleanly and the records look right, repeat the exact same mapping for the full file with confidence. This test-then-scale rhythm is the difference between a smooth data load and an afternoon of cleanup, and it costs almost nothing because the export itself is quick to scope down to a handful of rows. Treat the first ten as your dress rehearsal and the full import becomes routine.

The bottom line

Importing Gmail contacts into Salesforce cleanly comes down to preparation: decide Leads versus Contacts, export a scoped CSV locally, dedupe and supply required fields like Last Name and Company, then map carefully in the Data Import Wizard. Done this way, your org gains real contacts without a standing inbox connector and without the cleanup a sloppy import creates.