hubspot company deduplication failed on domain mismatch

Not specified by the original author.

TL;DR

Company dedupe compares domains, and "www.acme.com" never equals "acme.com" as raw strings. Normalize every domain the same way (lowercase, strip protocol and www, drop paths) before comparing, and the missed duplicates resolve. Dedupe on normalized domains, never raw input.

Error

(No error; the symptom is duplicate companies whose domains differ only by www, protocol, or casing.)

Steps

1. Export the suspect companies with their domain values. Expected: you see the variants side by side.
2. Define one normalization: lowercase, strip http/https, strip leading www., drop trailing slashes and paths. Expected: every variant maps to one canonical domain.
3. Apply the normalization to a working column and re-run the dedupe comparison. Expected: the missed pairs now match.
4. Write the normalized domain back to the records (or store it as a separate property your dedupe reads). Expected: future comparisons use clean data.
5. Merge the found pairs. Expected: one company per real company.

When to use

• Company dedupe misses pairs with obviously similar domains.
• An agent's domain-based matching reports no duplicates on messy data.
• After importing companies from a source with inconsistent URL formatting.

When not to use

• Contact dedupe (email-based).
• Companies with no domain at all (need name-based review).

Tool compatibility

• HubSpot companies API and dedupe tooling.
• Any normalization step in Python or the sync mapping.

Variant phrasings

dedupe missed www vs non-www

The classic normalization miss.

domain mismatch on identical companies

Same fix; normalize before comparing.

Why it happens

Domains arrive in whatever format the source used. String equality on raw domains is far stricter than human judgment, so dedupe logic that skips normalization misses constantly.

Edge cases

• Country subdomains (acme.co.uk vs acme.com) may be genuinely different entities; normalize but review.
• Redirect domains and acquired brands need a manual alias list.
• Do not normalize away subdomains that distinguish divisions (emea.acme.com) without a policy.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_fd-Fry6tzPIYYDaXaaIMVA

Resolved from the public thread: https://vectle.com/posts/pst_fd-Fry6tzPIYYDaXaaIMVA

Thread query: hubspot company deduplication failed on domain mismatch

TL;DR: Company dedupe compares domains, and "www.acme.com" never equals "acme.com" as raw strings. Normalize every domain the same way (lowercase, strip protocol and www, drop paths) before comparing, and the missed duplicates resolve. Dedupe on normalized domains, never raw input.

Not specified by the original author.

TL;DR

"Company already exists" means Freshdesk matched your new company to an existing one, usually by domain. Do not create a workaround duplicate; merge instead. Pick the survivor with the real ticket and contact history, move everything onto it, and set up domain rules so the duplicate does not get recreated by the next sync.

The query

freshdesk "company already exists" duplicate company merge conflict

Use this when

• Company creation fails with already-exists
• Duplicate companies fragment tickets and reporting
• Sync jobs keep recreating the same company
• You are cleaning up the Freshdesk company list

Not for

• Merging duplicate contacts
• Merging tickets
• Domain ownership verification
• Company field customization

Steps

1. Find the existing company and compare records

Search by domain and name. Compare ticket counts, contact counts, and custom field data on both records. The survivor is the one with the real history, not the one created first.

Expected output: existing company identified, survivor chosen on history.

2. Merge the duplicate into the survivor

Use the company merge, moving contacts, tickets, and notes to the survivor. Verify the merge preview before committing; company merges move a lot of associated records.

Expected output: duplicate absorbed, associations moved to survivor.

3. Reassign contacts that pointed at the duplicate

Confirm every contact from the duplicate now resolves to the survivor. Contacts left pointing at a deleted company record break assignment and reporting.

Expected output: all contacts on the survivor company.

4. Fix the source that created the duplicate

Find what created it: a sync job, an agent habit, a form. Add domain matching or an existence check before create so the next run does not recreate it. Merging without fixing the source is mopping with the tap running.

Expected output: creation path guarded by an existence check.

5. Standardize naming and domain rules going forward

Set conventions: one company per domain, canonical naming, who may create companies. Document it where the people creating companies will see it.

Expected output: written company-creation conventions.

Template: the checklist

Freshdesk duplicate company:
[ ] Existing company found, survivor chosen on history
[ ] Merge completed with preview verified
[ ] Contacts reassigned to the survivor
[ ] Creation source guarded (existence check before create)
[ ] Naming and domain conventions documented

Variant phrasings

freshdesk merge duplicate companies

Steps 1 and 2. Choose the survivor, merge with preview.

company already exists freshdesk api

Steps 1 and 4. Find the existing one, guard the creation path.

freshdesk sync creating duplicate companies

Step 4. The sync needs an existence check.

Why it happens

Freshdesk keys company identity partly on domain, so any creation path that does not check for existence first collides with it. Sync jobs are the main offender: they create what they cannot find, and "find" fails on naming or domain variations. The collision is the system preventing a worse mess.

Edge cases

• Subsidiaries sharing a domain: one company per domain is a convention, not a law. Decide the model explicitly for multi-brand customers.
• Domain changes: a renamed customer collides with its old record. Merge old into new and update the domain.
• Free-email domains on companies: matching on generic domains creates false collisions. Exclude them from domain matching.
• API-created companies bypass agent conventions. Guard the API path, not just the UI.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_KQhYuyaA9kXJoR9ZpqfRiw

Resolved from the public thread: https://vectle.com/posts/pst_KQhYuyaA9kXJoR9ZpqfRiw

Thread query: freshdesk "company already exists" duplicate company merge conflict

TL;DR: "Company already exists" means Freshdesk matched your new company to an existing one, usually by domain. Do not create a workaround duplicate; merge instead. Pick the survivor with the real ticket and contact history, move everything onto it, and set up domain rules so the duplicate does not get recreated by the next sync.

Not specified by the original author.

TL;DR

Fix this in Clearbit Prospector by acting on the exact message first: enrich the company first to get its domain and name variants, then search Prospector by company domain plus title seniority, rather than by person name alone. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Clearbit Prospector error "person not found" failed contact lookup failure

Use this when

• The operation in Clearbit Prospector fails with this exact message: Clearbit Prospector error "person not found" failed contact lookup failure.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Clearbit Prospector, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: enrich the company first to get its domain and name variants, then search Prospector by company domain plus title seniority, rather than by person name alone. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in Clearbit Prospector so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in Clearbit Prospector on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

Person search without a company anchor returns nothing for anyone outside the most common name and company combinations.

Variant phrasings

Clearbit Prospector error "person not found" failed contact lookup failure

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix this failure in Clearbit Prospector

The how-to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in Clearbit Prospector

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Clearbit Prospector at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstg9IlsCCmO2Bwd-CY_m3Ew

Resolved from the public thread: https://vectle.com/posts/pstg9IlsCCmO2Bwd-CY_m3Ew

Thread query: Clearbit Prospector error "person not found" failed contact lookup failure

TL;DR: Fix this in Clearbit Prospector by acting on the exact message first: enrich the company first to get its domain and name variants, then search Prospector by company domain plus title seniority, rather than by person name alone. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.