Create sales territories from Excel

When to use this

Use this workflow when your customer, prospect, account, branch, or site list is in an Excel workbook and you want to turn it into an editable territory map without GIS software.

Step-by-step workflow

1. Prepare the workbook

   Keep one location per row. Use clear headers such as location_name, latitude, longitude, segment, and status. The current builder needs latitude and longitude columns for spreadsheet points.

2. Open the map builder

   Use the TerritoryKit map builder, or start with the synthetic sales territory template to explore the finished workflow first.

3. Import the Excel file

   Choose Import, upload an XLSX or XLS file, then select the latitude and longitude columns. Review valid, repaired, skipped and invalid row counts before creating the point layer.

4. Verify the mapped points

   Check that the point layer appears in the left panel and that the points land where you expect. If records are missing, check the coordinate columns and empty rows.

5. Draw or import the territories

   Use the polygon or circle drawing tools for custom sales territories. You can also import existing KML or KMZ boundaries if your team already has territory shapes.

6. Check counts and overlaps

   Open the analytics panel, select the point layer and zone layer, and review totals, unassigned records, and records that fall in more than one zone.

7. Export the results

   Use Export to download metrics, point membership, territory geometry, or a portable project backup for later editing.

Supported formats and inputs

• Excel point data: XLSX and XLS files with usable latitude and longitude columns.
• Other imports confirmed by the app: CSV, KML, KMZ, JSON, and .zonestudio.json project files.
• Territory geometry can be drawn in the browser or imported from KML/KMZ files.
• The current product does not geocode street addresses, balance territories automatically, optimize routes, or forecast revenue.

Tips and common mistakes

• Missing latitude or longitude values are skipped during spreadsheet import.
• Latitude must be between -90 and 90, and longitude must be between -180 and 180.
• Separate coordinate columns are simplest, but the repair assistant can also split clear values such as 43.67,-79.32 from one column.
• Remove blank rows and make headers clear before importing. Duplicate headers can make the preview harder to read.
• If the map looks empty, use Fit all data and confirm the selected coordinates are not reversed.

Export and results

TerritoryKit can export per-zone metrics as CSV or Excel, point-to-territory membership as CSV or Excel, zone geometry as GeoJSON or KML, and a portable .zonestudio.json project backup.

FAQ

Related workflows