Supported CRM input
Object
HubSpot companies only.
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 value | Result | Reason |
|---|---|---|
85001 | Valid: 85001 | Exact ZIP5 |
85001-1234 | Valid: 85001 | ZIP+4 reduces to ZIP5 |
00501 | Valid: 00501 | Leading zero remains text |
| Blank | Missing | No routing location |
8501 or a numeric value that lost its zero | Invalid | TerritoryLogic never guesses or pads |
| Recognized non-U.S. country | Unsupported country | Current programs are U.S.-only |
Portal preparation checklist
- Create a HubSpot view for the companies you intend to test.
- Inspect country and ZIP as text. Pay special attention to leading-zero ZIPs and spreadsheet imports.
- Resolve duplicate, merged, inactive, or unexpectedly blank owners in HubSpot.
- Confirm the intended territory owners appear as active HubSpot owners.
- Install with a user allowed to approve the company-read, company-schema-read, and owner-read scopes.
What TerritoryLogic does not copy
The current sync does not retain raw street addresses or malformed ZIP strings. It does not request sensitive or highly sensitive HubSpot scopes. Contact, deal, ticket, lead, and custom-object data is outside the public company 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.