Reuven Shelef

@... The 'merge' per se is not the problem. I was too quick and short-handed when typing my comment. Merge is involved, however the actual scenario can be described by two SFDC Accounts, each syncing to two ZD Orgs, then these links need to be switched.

Before: 
Account 1 syncing to Org A
Account 2 syncing to Org B

After: 
Account 1 syncing to Org B
Account 2 syncing to Org A

We merged accounts to have Account 1 remain, however that is not in the core of this issue.
Sorry for the confusion.

I'm happy that you are working on at least providing a way to control the sync linkage.

The second scenario I described is even more bothersome, I hope you ill resolve this constrain as well.

@... to your "Secondly: I'm curious why there are so many connections being made that later need to be broken? Is there a workflow that's causing this? Were these connections made a long time ago with different matching criteria that are no longer relevant? Having a bit more context about how this arises may help us to build solutions that better address that workflow." question for Naomi Watnick:

I've complained about this to ZD several times. This is a big pain. The two key scenarios are:

1. Accounts merged in SFDC

2. ZD's horrible limitation of inability to change the link between a Closed Ticket and an Organization, causes the need to have DUPLICATE Organizations in ZD - just to hold Closed Tickets. The SFDC Account needs to sync to the other, 'live' Organization.