Export a stable account ID, clean only the service or business address, geocode it into coordinates, review failures, then map customers with owner, segment and revenue fields. Geocoding creates points; territory boundaries and balanced assignments require a separate rule or spatial-analysis step.
Define what one row represents
A map of contacts, accounts and physical service sites answers three different questions. Choose the analysis grain first, then deduplicate at that level. Retain a stable CRM ID so every point can be joined back without exposing unnecessary customer text.
| Field | Why it matters |
|---|---|
| Account or site ID | Stable join key |
| Address type | Headquarters, billing, shipping or service site |
| Cleaned address | Geocoding input |
| Owner and segment | Map styling and filtering |
| Revenue or workload band | Territory balancing input |
| Latitude, longitude and status | Location and quality review |
Geocode the location that drives the decision
Billing addresses may point to a finance office while field representatives visit a service site. Add an address-type column, select the relevant fields and include status. Review shared coordinates and suspicious city-center clusters before measuring coverage.
Move from points to an explicit assignment rule
- VisualizeMap reviewed account points by current owner or segment.
- MeasureSummarize counts, opportunity value and workload by region.
- ConstrainDocument boundaries, travel expectations and account exceptions.
- AssignApply a reproducible rule rather than manually coloring isolated points.
- AuditKeep overrides and effective dates for future rebalancing.
Keep territory maps reproducible
- Record the CRM export date and filters.
- Preserve the account ID and address type.
- Version territory definitions and manual exceptions.
- Restrict shared maps to the intended audience.
- Re-run geocoding only for changed or newly added locations.
Sources and methodology
Technical claims were checked against the sources below on August 18, 2026. Product limits and third-party pricing can change; verify the live documentation before designing a production workflow.
Common questions
Does geocoding automatically create sales territories?
No. It creates location points. Territory design also needs boundaries, workload or revenue objectives, capacity constraints and assignment rules.
Which CRM address should I use?
Use the location relevant to the sales decision—such as service site, headquarters or branch—and label that choice. Mixing address types creates misleading clusters.
Can multiple accounts share one coordinate?
Yes. Several contacts may occupy the same building, or several rows may represent one account. Deduplicate according to the analysis level before interpreting density.
Should customer names appear on a shared map?
Only when the audience and purpose require them. A territory-planning map can often use account IDs, segments or aggregated counts instead.