Guide 02

Prepare HubSpot for exact ZIP routing

Choose every CRM object that should share the program and map a single-line text or number ZIP property for each. Clean inputs make the simulation useful; missing or invalid inputs remain safe exceptions unless explicit whole-state fallback applies.

Last reviewed July 29, 2026 · Early-access documentation

Supported CRM input

Object

Companies, contacts, deals, tickets, leads, or a qualifying portal custom object.

Country

Blank in the U.S.-only workspace context, or a recognized United States value.

ZIP

Five ASCII digits, or ZIP+4 that can be reduced to its first five digits.

Owner

The HubSpot owner id, from an active owner record—not a HubSpot user ID.

How ZIP values normalize

HubSpot valueResultReason
85001Valid: 85001Exact ZIP5
85001-1234Valid: 85001ZIP+4 reduces to ZIP5
00501 in a text propertyValid: 00501Leading zero remains text
501 in a number propertyValid: 00501Whole numeric values are left-padded to ZIP5
BlankMissingNo routing location
8501 in a text propertyInvalidText must remain exact ZIP5 or ZIP+4; TerritoryLogic never guesses malformed text
Recognized non-U.S. countryUnsupported countryCurrent programs are U.S.-only

Portal preparation checklist

  1. Create a HubSpot view for the object records you intend to test.
  2. For every selected object, choose or create an editable single-line text or number property containing ZIP/postal values. Text fields preserve ZIP+4 and leading zeroes. Number fields must contain whole values from 0 through 99999; TerritoryLogic pads them to five digits.
  3. Resolve duplicate, merged, inactive, or unexpectedly blank owners in HubSpot.
  4. Confirm the intended territory owners appear as active HubSpot owners.
  5. Install or reauthorize with a user allowed to approve the selected object's read/schema scope and owner-read scope.

What TerritoryLogic does not copy

The current sync does not retain raw street addresses or malformed ZIP strings. It retains only bounded object identity, current owner, normalized ZIP/country evidence, and normalized city/state fallback evidence needed by the configured program. It does not request sensitive or highly sensitive HubSpot scopes. Activities are outside the current routing release.

After correcting HubSpot

Open Workspace settings and request a full resync, then wait for it to complete before running a new simulation. A previous simulation remains bound to its original snapshot and must not be treated as evidence for newly corrected inputs.