Merging Organizations in Zendesk

Two records for one customer means two halves of a history, and support decisions made with half the picture.

Zendesk has no organization merge button

Unlike users and tickets, organizations cannot be merged in one action. You move the members and the tickets, then retire the empty record.

The practical route

Decide which organization survives, usually the one with the correct domain mapping and the longer history.
Reassign the users. Bulk update from the Customers list, or use the API for anything above a handful.
Reassign the tickets that carry the old organization, using a view plus a bulk update.
Fix the domain mapping on the surviving organization so new users land in the right place automatically.
Rename the empty organization to something obvious like "MERGED, do not use" rather than deleting it, so nothing that references it breaks.

The duplicate ticket angle

Split organizations create a specific kind of duplicate that manual review almost never catches: two people from the same company report one outage, but because they sit in different organization records the tickets look like unrelated requests from unrelated customers.

Ticket Merger can match on the email domain rather than the organization record, which catches these pairs even while your organization data is still messy. Fix the data when you have time. Catch the duplicates now.

Frequently asked questions

Does merging in Zendesk lose the customer replies?+

No. Ticket Merger uses the native Zendesk merge, so the conversation, attachments and audit history move onto the surviving ticket. The duplicate is closed with a note pointing at the original.

Can I review merges before they happen?+

Yes. Start in suggest-only mode: Ticket Merger flags the pairs it believes are duplicates and leaves the decision to an agent. Most teams run that way for a week, check the hit rate, then let the confident matches merge on their own.

What stops it merging two tickets that are not the same?+

Rules you set. Match on requester, subject similarity, body similarity and a time window, and exclude anything you want left alone, like tickets from a specific form, group or tag. Anything below your confidence threshold gets suggested rather than merged.

How long does setup take?+

About five minutes to connect, and the first scan of your open queue runs immediately after. Onboarding help is included on every plan.

Catch company-wide duplicates

Match on domain, not just requester, and the "everyone reported the outage" pile becomes one ticket.

Start free trial

14-day free trial. No credit card required.