Export Google Maps Results to CSV

A CSV export is a plain-text table: one business per row and one field per column. It is useful when you need Google Maps results in a spreadsheet, a research file, or a system that accepts file imports. The file carries data, not your extension's filters, screen layout, or account settings.

GBP Sweep exports collected business listings as CSV and JSON. The CSV has 23 fixed columns, including contact details, listing context, identifiers, and collection information. Start with the downloadable sample if you want to inspect the structure before collecting. Its twelve businesses are fictional; the column names match the extension's export.

Choose which businesses belong in the file

Open the Collection page and sign in to view your saved results. Choose the appropriate search list or the complete collection. Apply only the filters needed for the destination file. For a calling list, a phone filter makes sense. For a map of storefronts, a phone requirement would discard locations for the wrong reason.

The main Export CSV button exports the currently filtered rows, including rows beyond the portion currently visible on screen. You can also select particular businesses and export that selection. An export-everything option is available separately. Check the scope before downloading so an unrelated earlier search does not end up in the file.

Name the saved file to identify its purpose, geography, and date. A name such as bakery-delivery-alder-falls-2026-10-17.csv tells a colleague more than final-list-new.csv. Keep an original copy before deleting columns or adding notes in another tool.

Understand the 23 export columns

The fields below describe what GBP Sweep can export. Availability depends on the listing and the details successfully collected. A full-profile collection can supply more information than a result card alone.

“All categories” joins available category labels with a semicolon. “Claimed” uses yes or no when the value is known and stays empty when it is unknown. An empty review count is different from a measured count of zero. Keep that distinction when importing into a database that tries to fill missing numbers automatically.

The export does not include email addresses, owner names, estimated revenue, employee counts, or a sales-readiness score. Website links can support your own research, but the extension does not turn them into verified email contacts.

Preserve text fields during import

Some columns look numeric but should be treated as text. Phone numbers may start with a plus sign or zero. Postal codes can contain leading zeros or letters. CID values can be longer than a spreadsheet's safe numeric precision. Converting these fields to numbers can change the stored information.

Import Phone, Phone (international), Postal code, Place ID, and CID as text. Rating, Reviews, Latitude, and Longitude can be numeric if your destination handles blanks correctly. Keep the original Collected at value if you need the full timestamp, rather than replacing it with a date-only display.

For Excel, use an import workflow with explicit column types; the Excel guide covers the details. For a shared browser-based worksheet, follow the Google Sheets guide. Double-clicking a CSV can be convenient, but it gives you less control over automatic conversions.

Check a file with commas and international characters

A business address often contains commas. Opening hours may contain punctuation or line breaks. A correctly written CSV quotes cells that need quoting so those characters do not create extra columns. GBP Sweep uses quoted fields where needed and writes UTF-8 with a byte-order mark for spreadsheet compatibility.

Use your destination's CSV importer instead of splitting lines manually at every comma. Confirm that the header has 23 columns and that the last field is Collected at. Then inspect a business with a comma in its address and one with a non-English name, if your real collection contains one.

If the entire row appears in one column, check the separator setting and select comma. If names display broken characters, check the character encoding and choose UTF-8. Do these checks on a copy of the file. Saving a damaged import over the original makes recovery harder than simply starting from the export again.

Prepare a CRM import without losing the source

GBP Sweep provides a file export, not a direct CRM connection. Your CRM's import rules decide which columns it accepts and how it handles duplicate records. Create a mapping before the first upload: Name to business name, Website to website, Phone to business phone, and address parts to the corresponding address fields.

Keep Google Maps and at least one identifier in custom fields if the destination supports them. These help someone reopen the source or compare a later batch. Put Source search and Collected at in research fields rather than mislabeling them as customer acquisition dates.

Test with a few rows in an import preview or a separate test list. Confirm whether one row creates a company, a location, or a contact. A business phone number should not silently create a named person. Do not upload hundreds of rows until you know how the destination represents them.

Separate missing data from cleanup decisions

Suppose a collected bakery has an address and phone but no website. Keep the website blank in the raw file. If you later find a website manually, add a separate verification note in your working sheet. Avoid entering “none” into a URL field: another system may treat that text as a real value.

Use the same care with duplicates. Two shops can share a domain while operating at different addresses. A phone number may reach a shared reception desk. The duplicate-handling guide explains how to preserve locations while reviewing repeated listings.

Export limits and a final file check

Free includes exports of 50 distinct businesses per calendar month. Exporting the same business again during that month does not consume another distinct-business allowance. Pro includes unlimited CSV and JSON exports. Both plans save the collection locally in the extension; exporting creates a file you control.

Before using the list, compare the exported row count with your intended scope, inspect several phone numbers and identifiers, and confirm the geography. Keep the raw CSV separate from the edited version. If you need nested data for a script rather than a flat table, consider JSON instead. The right format is the one your next tool can read without changing the values you worked to collect.