How to import Google Maps leads into a CRM

Import the CSV as a single object type and map the identity columns first: name, place_id, phone and website. Use place_id as the external identifier so a later import updates the existing record instead of creating a second one.

Do the column mapping once and it keeps working: existing export columns keep their names and positions, and new fields are appended at the end rather than inserted.

The export's leading columns are the ones that decide whether an import is idempotent. Map them before anything else:

1. 1

   Choose one object

   A Maps row is one business. Import as companies or accounts, not as contacts, unless you deliberately want one lead per email.

2. 2

   Set the external key

   Point the CRM's unique identifier at place_id. This is the step that turns every future import into an update instead of a duplicate.

3. 3

   Map contacts separately

   Emails arrive in a comma-separated emails column with a parallel email_source column. Split them into child records if your CRM models them that way.

4. 4

   Map enrichment fields as custom fields

   rating, reviews, business_status, types, hours and the email evidence columns have no standard CRM equivalent. Map them as custom fields so a rep can filter and report on them.

5. 5

   Import into a test list first

   Import one run, check the deduplication against an existing territory, then import the rest.

• •Key on place_id, never on name or phone: both get edited by owners and both collide across branches.
• •The same brand at different addresses is a different business. Deduplication by place id preserves those branches rather than collapsing them.
• •When combining exports from two tools, convert both to place_id before merging, or you will create duplicates at the boundary.
• •An empty cell means the listing or website did not publish that field. Do not backfill it with a guess to satisfy a CRM's required-field rule.

Where a business publishes an email address on its own website, the export carries it with its evidence alongside the business row:

• •emails - the discovered addresses, comma-separated when there is more than one
• •email_source and email_discovery_sources - where each address was found, including the page and the method
• •email_type, email_domain_match, email_confidence - how the address was classified and whether it matches the business domain
• •mx_status and the deliverability columns - the mail server check and any verification result
• •lead_quality, relevance and social_evidence - the product's own quality review of the contact

• •Gmap Data does not write to a CRM directly. The hand-off is the CSV, or a project export from the app.
• •It does not create, update or delete records in HubSpot, Salesforce or any other system on your behalf.
• •It does not send outreach. Sequences, opt-outs and suppression stay in your existing tools and are your responsibility.
• •Google Sheets export is an operator-workspace tool, not a customer feature, so the customer path is CSV.