Back to all posts

Google Maps to Salesforce CSV: Turn Saved Places into Importable Accounts

Prepare Google Maps prospect lists for Salesforce by converting saved places into a clean CSV with addresses, coordinates, territories, and owner fields.

June 26, 2026

•

4 min read

Salesforce is rarely where early territory research starts. Reps and managers often begin in Google Maps because it is fast: search an area, save prospects, make a list, share it with the team. That is fine until the list needs to become account data.

Salesforce wants structured rows. Google Maps gives you saved places. The gap between the two is where manual copying starts.

This guide shows the practical middle step: convert the Google Maps research into a clean CSV first, then import or stage it in Salesforce.

Why Google Maps research gets stuck

A saved Google Maps list is useful for finding places, but it is not a Salesforce import file. A raw export can be missing the fields sales ops needs:

  • account name in a consistent column
  • street address, city, postcode, and country
  • latitude and longitude
  • owner or territory
  • lead source or campaign source
  • notes from the original research

Without those columns, someone has to rebuild the list in a spreadsheet. That is slow, and it is easy to lose the reason each account was saved.

The clean path: Google Maps to CSV to Salesforce

Use Takeout Tools as the prep step before Salesforce.

  1. Export the places from Google Takeout, or use a shared Google Maps list when the research came from another person.
  2. Upload the file or list to Takeout Tools.
  3. Export CSV with names, addresses, list names, notes, and coordinates.
  4. Open the CSV and add Salesforce-specific fields: owner, territory, lifecycle status, source, and any required custom fields.
  5. Import as leads, accounts, or a staging object depending on how your Salesforce org handles new territory data.

The goal is not to push raw map data straight into production. The goal is to create a clean staging table that sales ops can inspect.

Fields worth keeping

Name and address

Keep the account name and address fields simple. If your team uses separate columns for street, city, postcode, and country, split those before import. If your Salesforce org has strict duplicate rules, use the spreadsheet stage to standardise names before upload.

Latitude and longitude

Coordinates are useful even when Salesforce is not your mapping tool. They help downstream route planners, territory maps, and analytics workflows place accounts without another geocoding step.

Source list

The source list often explains intent. "Q3 pub prospects", "North Yorkshire freehold", or "Manchester pharmacy calls" is not just a label. It tells the team why the row exists. Keep it as a source, segment, campaign, or territory column.

Owner and status

Do not wait until after import to decide ownership if the assignment is already known. Add owner, territory, status, and next action in the CSV so Salesforce receives operational data, not just locations.

What Takeout Tools does and does not do

Takeout Tools prepares the account table. It does not create Salesforce records directly, deduplicate against your existing accounts, enrich contacts, or decide lead assignment rules.

That is deliberate. Salesforce is the system of record. Takeout Tools is the bridge from Google Maps research into a table clean enough for that system.

QA before import

Before importing, filter blank addresses, review duplicate names, and check coordinate outliers. If the source list came from several reps, standardise list names and statuses before upload. It is much easier to fix a CSV than to clean bad records after they have landed in Salesforce.

Related field-sales guides