You've got a spreadsheet full of locations and you want them in StoreRocket. Good news: this only takes a few minutes. You can either upload a CSV file directly or connect a Google Sheets spreadsheet for ongoing sync.

CSV file upload is the fastest option. You upload a file, StoreRocket checks it, and you publish it. Best for one-time imports or when you're setting up your account for the first time.

Google Sheets sync connects a live spreadsheet to your project. You can sync locations back and forth whenever you want, and even enable daily auto-sync. Best for teams that manage locations in spreadsheets and want changes to flow into StoreRocket automatically.

Both methods use the same column format, so everything you learn here applies to both.

Here's every column StoreRocket recognizes. You don't need to use all of them. At minimum, you need Name and an address (either split into parts or as a full address).

In a CSV or Excel import, your columns don't have to use these exact names. When you upload a file, StoreRocket matches the columns it recognizes and asks you about the rest (see Step 4 below). Custom field and button columns are the exception: they always need their Field: and Button: prefixes.

You can use individual address fields OR a single Full Address column. Don't use both.

Or use a single column instead:

If you provide individual address fields, StoreRocket combines them into a full address automatically. If you use Full Address, it gets geocoded as-is.

If a file has both, as every export does, the Full Address is the one that gets geocoded.

If you leave Visible empty, the location defaults to visible.

Don't worry about these. If you leave them blank, StoreRocket geocodes the address automatically and fills in the coordinates for you. Only include them if you already have precise coordinates and want to skip geocoding.

Hours use 24-hour format only. No AM/PM. Add one column per day of the week.

For a location that's open 24 hours, use 00:00-23:59. For closed days, write Closed or leave the cell empty.

Alternative: hours templates. If you've already created reusable hours templates in Hours, you can reference them by name using the Hours ID column instead of specifying each day:

The template must already exist in your project before importing.

This is the column that causes the most import problems, so it is worth reading carefully.

Filters go in a single column called Filters. For each location, list the filter names separated by commas.

How it works:

Common mistakes:

Custom fields let you store extra data on each location (store number, manager name, product lines, anything). The column header uses the Field: prefix.

Add a separate column for each custom field. If the field doesn't exist in your project yet, StoreRocket creates it automatically during import.

The column header format must be exact: Field: followed by a space and the field name.

You can add CTA buttons (like "Order Now" or "Book Appointment") using the Button: prefix. The cell value is the URL the button links to.

Add a separate column for each button. If the button doesn't exist in your project yet, StoreRocket creates it automatically. Leave the cell empty for locations that don't need a particular button.

The import has three steps on screen: "Upload", "Match columns" and "Review & publish". Nothing changes on your map until you publish.

Go to the Import page. You'll find it in the sidebar under Location Data > Import, or under Import > CSV / Excel on your Locations page. Under "Download a template", click "Excel template" or "CSV template". This gives you a pre-formatted file with the most common column headers in the right order.

Open it in Excel, Google Sheets, or Numbers and fill in your location data.

Already have a spreadsheet of your locations? You can skip the template and upload your own file. You'll match its columns in Step 4.

When your data is ready, save the file. The import accepts CSV, TXT, TSV, XLS and XLSX files, so an Excel file can be uploaded as it is. If your spreadsheet app saves in its own format (like Numbers), save a copy as CSV. In most spreadsheet apps, go to File > Save As (or Download as) and pick Comma Separated Values (.csv).

A file can be up to 15 MB and hold up to 100,000 locations. You don't need every column from the template, so you can delete the ones you don't use.

StoreRocket matches each column it recognizes to a location field. If everything matches, the page tells you how many locations are ready to check. Click "Preview locations" to see your first few locations the way StoreRocket reads them.

If StoreRocket doesn't recognize a column name, the page says how many columns are "to match", and those columns are listed under the "To match" tab. Each one says "This column name wasn't recognised. Choose where to save it." For each one, either:

Your file needs a column with location names. If StoreRocket can't find one, the page asks you to "Choose a location name column". Pick it from your columns.

Custom field and button columns are only recognized by their Field: and Button: headers. They aren't in the list of fields you can choose, so if one is flagged, rename the column with its prefix and upload the file again.

If the first row of your file is a location rather than column names, open the "Header row" menu (the button reads "Headers detected") and turn off "Use first row as column names". Picked the wrong file? Click "Change file".

When you're ready, click the button that shows your count, like "Review 120 locations".

During first-time setup, StoreRocket skips this step when every column is already matched.

StoreRocket now checks every location and finds each address on the map. Nothing is published yet. Big files take a few minutes, and you can close the page while it works: the draft waits for you in Import history.

When the check is done, you'll see how many locations are ready. Before you publish:

Then, under "Choose what happens when you publish", choose Add or Replace (more on this below) and click the publish button. With Add selected it reads, for example, "Publish 120 locations". With Replace selected it reads "Replace with 120 locations".

Not ready yet? Click "Publish later". Your draft is saved, and you can finish it from Import history.

Publishing a large file can take a while. StoreRocket keeps working if you leave the page, and you can check progress in Import history.

When publishing finishes, you'll see what changed: how many locations were added, updated and removed, plus any rows that were left out or went over your plan limit. Click "View my locations" to see them.

Head to your Locations list and verify everything looks right. Then open Store Locator > Customize to see them on the map in the preview.

Every address was placed on the map during the review, so there's no geocoding left to wait for.

An import stays a draft until you publish it. If you leave before publishing, the Import page shows it as an "Unfinished import" with its next step, like "Review & publish" or "Continue matching". Click it to pick up where you left off.

Import history lists all your imports: drafts, imports being checked or published, and published ones. Open a published import to see what it added, updated and removed, and every row it included or left out. Click "New import" to start another one.

To throw away a draft, open it and click "Discard draft import". Your published locations stay exactly as they are.

When you publish, you choose what happens to the locations already in your account:

Before a Replace, StoreRocket asks you to confirm. It shows how many locations you have now and up to how many the file will replace them with. Click "Replace and publish" to go ahead, or "Keep current locations" to back out.

Matched rows keep their existing StoreRocket record and click history. StoreRocket matches your rows against the locations you already have. Imported columns can update or clear details, while omitted columns keep their current values.

Matching works two ways, in this order:

Add only uses the StoreRocket ID: a row without one becomes a new location. Replace uses both.

Keep the StoreRocket ID column when you can. It's the only thing that still matches a location after you rename it or correct its address, which name-and-address matching can't do.

Only the columns in your file change. When a row updates a location you already have, any column that isn't in your file, or that you left out when matching columns, keeps its current value. A blank cell in a column you did include can clear a value: a blank Phone cell, for example, removes that location's phone number. One exception: when a row changes a location's Full Address, its separate address fields are replaced too, with whatever your file has for them (blank if it has none).

If a store leaves your file and comes back later with the same name and address, StoreRocket can reconnect its recorded clicks.

New accounts can import a spreadsheet as part of setup. The first file is always added. If you import another file during setup, StoreRocket asks whether to "Replace them" or "Add to them", meaning the locations from your earlier file. It picks one for you: Replace when at least half of the new file is already on your map, Add otherwise. Locations you added by searching stay either way, and rows marked "Already on your map" or "Listed twice" are never added a second time.

If you leave while a file is still being checked, it publishes on its own when the check finishes, using the option StoreRocket picked. Rows that need a fix are left out, and the result lists them. For a big file, you can click "Put it on your website meanwhile" to start installing your locator while the addresses are placed.

Google Sheets sync creates a live connection between a Google spreadsheet and your StoreRocket project. You can push locations to the sheet, pull locations from the sheet, or set up daily auto-sync.

The spreadsheet is created in StoreRocket's Google Drive and shared with you. You can also share it with team members from the Google Sheets Sync page.

Sync to Sheets (export): Pushes your current StoreRocket locations into the spreadsheet. Go to Sync page and click the sync-to option. This overwrites whatever is in the sheet with your current StoreRocket data.

Sync from Sheets (import): Pulls locations from the spreadsheet into StoreRocket. Go to Sync page and click the sync-from option. This updates your StoreRocket locations to match the spreadsheet.

You can enable daily auto-sync from the Google Sheets Sync page. When enabled, StoreRocket automatically syncs from your spreadsheet once a day. This is great if your team regularly updates the spreadsheet and you want changes to flow in without manual intervention.

You can download all your locations as a CSV file at any time.

If you have more than 10,000 locations, we email you a download link instead.

This is useful as a backup before a big import, or if you want to make bulk edits in a spreadsheet and re-import.

This is the most common import issue, and it is almost always a column naming problem.

If you published with "Replace my current locations" (or "Replace them" during first-time setup) and it removed more than you expected:

Re-importing brings the locations back. StoreRocket can reconnect recorded clicks when the name and address match what they were before.

Need help with your import? Message us on live chat and we'll help you sort it out.