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.

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.