Can I use the CSV to import accounts into Salesforce?

Yes. Salesforce accepts CSV imports for accounts and leads. Map the name and address columns to the corresponding Salesforce fields. Latitude and longitude can be mapped to geolocation fields if your Salesforce instance uses them.

Can I import the export into Badger Maps or another route planner?

Yes. Badger Maps, Circuit, SPOTIO, Route4Me, and OptimoRoute all accept CSV imports. Most take either street addresses or latitude/longitude, Badger's import wizard, for example, uses two decimal-degree columns, which the Takeout Tools export already includes. Map your columns in the tool's import step and your accounts plot without entering coordinates by hand.

What if my prospect list is split across multiple Google Maps lists?

Takeout exports all your saved-places lists in one file. You can export everything together or filter to specific lists during the export process.

Does the geocoding work for businesses without precise addresses?

Accuracy is high for businesses with a clear Google Maps listing. It drops for places saved by generic description or without a street address. Review the export and correct any mismatches before importing into your CRM.

Can field reps use this on mobile?

The export runs in a browser. Reps can upload their Takeout file from any device and download the result. If you need a recurring workflow, set up the export centrally and push the file to reps via your usual file-sharing tool.

Back

Export Google Maps Prospect Lists to CSV and GPX for Field Sales

Field reps build prospect and account lists in Google Maps, then hit the same wall: getting them into a route planner, CRM, or territory map means hand-copying addresses and coordinates. Takeout Tools kills that manual step, one clean, geocoded export that drops into the tools you already use.

For field sales and territory operations teams

Export your prospect list Browse all tools →

The prospect list problem

Field reps use Google Maps the same way everyone does, it's fast, visual, and already open on their phone. Dropping a pin on a prospect, saving a cluster of accounts to visit on Thursday, building a list for a new territory. The data accumulates naturally.

The problem is it doesn't go anywhere. You can't push a saved-places list into Salesforce or HubSpot. You can't feed it into Badger Maps, Circuit, Route4Me, or OptimoRoute. You can't hand it to a territory manager as a structured dataset. So reps fall back on the manual workaround, copying addresses into a spreadsheet, dropping that into Google My Maps, then rebuilding the route by hand every time the list changes. If a rep has already built the list in My Maps, they can convert that map straight to a CSV rather than retyping it. The work that went into those lists stays stuck until someone copies it out by hand.

What field operations actually need

Territory data becomes operationally useful when it reaches the tools that drive execution:

CRM import: Salesforce, HubSpot, and most CRMs accept a CSV with company name, address, and coordinates. That's enough to create or enrich account records and associate them with a rep and territory.
Route planning: Badger Maps, Circuit, SPOTIO, SalesRabbit, Route4Me, and OptimoRoute all import an account or stop list as CSV (or GPX). Most take either street addresses or latitude/longitude, Badger's import wizard, for example, uses two decimal-degree columns, exactly what a Takeout Tools export includes, so accounts plot without manual coordinate cleanup.
Territory maps: GeoJSON and KML let territory managers visualise account density, identify coverage gaps, and present territory splits to leadership without building anything custom.

The Takeout Tools workflow

Google Takeout includes your saved places, but no coordinates. You get names and categories, not the spatial data that route planners and GIS tools need.

Takeout Tools adds the geocoding step. Upload your Takeout export, and it recovers coordinates for each saved place via the name and address. From there you export in whatever format the next tool expects.

Which format fits which step

CSV

The right format for CRM import and route-planning tools. Most CRMs (Salesforce, HubSpot) and route planners (Badger Maps, Circuit, SPOTIO, OptimoRoute) accept a simple CSV with name, address, latitude, and longitude, and because the export already carries coordinates, tools that take lat/long plot your stops without a separate geocoding step. If you colour-code or tier your accounts into Google Maps lists ("tier ones", "active", "prospects"), those list names come through as a List column, so your priority encoding travels with the data, sort or filter on it before you import. Export CSV first, convert to other formats from there using the free converters. Keep a header row with consistent column names so re-imports don't require remapping field by field.

GPX

Use this when the next step is a GPS device or navigation app. Garmin devices, OsmAnd, and Gaia GPS all import GPX waypoints natively. Useful for reps doing back-road field visits: load the waypoints into your GPS app or device and it handles the navigation to each stop. You can also convert GPX to CSV if you need to bring it back into a spreadsheet.

GeoJSON

Use this for territory mapping and analysis. Load into QGIS, Felt, or Kepler.gl to visualise account density, draw territory boundaries, or produce a shareable map for planning meetings. Convert KML to GeoJSON if you're working from an existing file.

Handing off to your route planner or CRM

Takeout Tools does one job: it gets your accounts out of Google Maps as a clean, geocoded list. It doesn't build routes or do turn-by-turn, that's what your existing tools are for, and the export drops straight into them:

Route planners: graduate from Google Maps to Badger Maps once your day outgrows Google's stop limit; the export lines up with Badger's import columns.
CRM: import the CSV into Salesforce or HubSpot to create or enrich account records with coordinates attached.

Keeping territory data fresh

Prospect lists change. Reps add new accounts, remove converted or unqualified ones, and adjust territory boundaries after planning sessions. The simplest recurring workflow is to keep Google Maps lists current and re-export via Takeout Tools at the start of each planning cycle, monthly or quarterly. Export to CSV, diff against the previous version to identify new and removed accounts, then push changes to your CRM in a single batch. Keeping the export cadence consistent means your CRM data and your field team's working maps stay aligned without manual reconciliation.

Splitting territory exports by list

If your organisation uses separate Google Maps lists per rep or territory, "North territory", "Assigned to Jordan", those list names carry through into the Takeout export. You can filter by list name in the CSV before importing into your CRM, which means a single export can serve multiple reps without manual splitting.

What to do before your first export

Before running a Takeout export, it's worth spending five minutes cleaning up your Google Maps saved places. Remove any dropped pins that don't have a business name, these won't geocode accurately. Rename lists to something meaningful if they've accumulated generic names like "Saved places" or "Want to go". And make sure your most important accounts or prospects have full addresses, not just a city name. A few minutes of cleanup now saves correction work after the export. If you're running the Takeout export for the first time, it can take Google up to 24 hours to prepare the file, build that into your planning timeline if you need the data for an upcoming meeting.

Convert between formats

Already have a geo file and need it in a different format? Use the free online converters: