Ability to merge organizations [closed for comments]

175 コメント

  • 正式なコメント
    Nicole - Community Manager
    コメントアクション Permalink

    Thank you all for your feedback. It has been escalated to our Product Teams and, while they are highly aware of this conversation, merging organizations is not something that is being considered for development.

    We have found that, for most customers, enabling the ability to merge organizations would have greater risks than the problems it would solve. Should two organizations be merged erroneously it could create massive security problems with data being shared between organizations that should not be. Currently, the ability to un-merge doesn't exist, so this is also a problem that would not have a way to be corrected. 

    This is a rock and a hard place decision, as we recognize the challenge for users such that end up with duplicate organizations. But at this time what would be required to create a secure way to merge organizations (and potentially un-merge if done incorrectly) would be a massive project that would require a huge amount of development resources and would derail the development of many other functionalities that are higher impact for more customers. 

    We have closed this thread for comments at this time. You are still welcome to up-vote to express your interest or need for this functionality, and can subscribe in case there are ever further updates. 

    We made the decision to close the thread for two primary reasons:

    1) We aren't seeking additional use cases at this time. We've got a ton of information on it at the moment, and additional use cases won't make a difference in the decision-making process. We will definitely reopen the conversation if at some point in the future we are considering it for prioritization.

    2) There won't be any updates for the foreseeable future. There is not a Product Manager working on this to provide updates, and until a different decision is made, there's nothing more for us to say about it. 

    We'll continue to monitor the votes on this thread, and will let you know if anything changes. Thank you as always for your participation and for providing feedback to Zendesk. 

  • Björn Sundman
    コメントアクション Permalink

    I would like this too!

    2
  • CharlieFellenbaum
    コメントアクション Permalink

    Adding my 2 cents also for support for this 'merge' feature/ability. Sad to see the date of this original request, very well stated, was 2 years ago. My workaround for now is to rename an organization, but if the system would allow it cleanly, then reporting would not be split between two names and 'corrupted.'

    4
  • Fernando Duarte
    コメントアクション Permalink

    Is this even on the roadmap?

    2
  • Jake Holman
    コメントアクション Permalink

    There's no immediate plans to build functionality for merging of Organizations. It's a feature that makes a lot of sense, though. 

    By merging, would one expect that all users and all tickets from the source Organization are moved ("merged") over to the target Organization?

    4
  • Colin Piper
    コメントアクション Permalink

    Jake, I would expect the requirements to match those of merging Users, yes. At least for me anyhow.

    4
  • Fernando Duarte
    コメントアクション Permalink

    You can already move all of the users by deleting the Domain from one and adding it to the other.  Unfortunately this does not move the closed tickets.

    3
  • Jimmy Maher
    コメントアクション Permalink

    I need this functionality also

    3
  • Marci Abraham
    コメントアクション Permalink

    Me too.

    One problem I see is that "closed" tickets can't be altered. I've just noticed this week that some tickets were submitted by users *before* they were properly associated with an organization. And now, those ticket are stuck in limbo, and not viewable with the rest of the organization's tickets....and they can't be changed. I would imagine this will be a problem when merging organizations as well. 

    5
  • Row M
    コメントアクション Permalink

    I would like to see this also and the ability for everything including closed tickets to move over. In our case some time 1 client merges with another and we need to do this Zendesk.

    3
  • Kris Moore
    コメントアクション Permalink

    I'd like to see this added too

    3
  • Emily McDaniel
    コメントアクション Permalink

    I have a few duplicate organizations in our system right now and would love to be able to easily merge the two together so that I have all of the ticket history and contacts tied to the right org.

    5
  • Eddie T
    コメントアクション Permalink

    We would also highly appreciate this functionality as it would save a lot of headaches....

    3
  • Caroline Laws
    コメントアクション Permalink

    This feature would be very helpful to us also.

    3
  • Justin Graves
    コメントアクション Permalink

    This would be helpful for us as well.

    What about this as a solution: Lets say we have a "bad" org that was created on accident with junk data in it and a "good" on with all of the proper data.  We want to see the tickets in the "bad" org in the "good" org when we look it up.  Could ZD possibly make a way to automatically create "follow-up" tickets for all of the closed tickets from the bad org in the good org and mark all of those as closed (while circumventing triggers and automations).  Then we would have a reference to all tickets in the good org.  And I know I'm asking for a lot, but it would also be great if there could be a way to archive "bad" orgs and only have them show up in search results if we tick a box that says "include archived".

    Pragmatically, since I have this issue right now, what I'm doing is just re-naming my bad orgs.  I keep the Org name but tack on something like "DO NOT USE"  in the name so our agents know which one is the accurate org for current use.

    3
  • Amie B.
    コメントアクション Permalink

    +1

    3
  • Sarah Rodenberg
    コメントアクション Permalink

    please make this possible!

    3
  • Claire
    コメントアクション Permalink

    This would also be very useful for us

    3
  • Stanislav Mokry
    コメントアクション Permalink

    Jake, yes, that's how it should work for us as well.

    3
  • Jamie Byers
    コメントアクション Permalink

    +1

    5
  • Daniel Bechtel
    コメントアクション Permalink

    +1

    especially when working with external CRM systems and organizations get merged all the time like in Salesforce.

    Once a ticket is closed it is stuck under the "old" organization. You will not get a comprehensive view of all issues for "one" organization.

    3
  • Droose
    コメントアクション Permalink

    I need this too, when is this going to be done? The original request is from 2011. Thanks, David.

    3
  • Matt Seiter
    コメントアクション Permalink

    I agree I could totally use this functionality.

    3
  • Scott Sullivan
    コメントアクション Permalink

    We could use this too. I see the request is only 3+ years old so I guess we've got another 3+ years to wait to see it?

    3
  • Terry Knox
    コメントアクション Permalink

    +1

    3
  • CharlieFellenbaum
    コメントアクション Permalink

    I guess it's about time for my yearly update on this fabulously good idea. And hopefully this week I will also send a note to our ZD Account Manager to see if we can get traction and/or action there.

    To spec it out further, stating our business needs, and why: We misspelled a customer's name and if I merely correct it, it creates a whole new organization. We have at least one other situation where a customer subaccount should Not have been given its own ZD Organization, so now it exists independently in the system. If I could merge them completely, their information would all be back together in one place where they should be. These may be self-caused issues, but the reason doesn't really matter. I saw others post that if one of their customers buys or otherwise merges with another, then they too are stuck in ZD separately. How annoying !

    For us, this need is driven in large part by GoodData reporting, not just convenience. Once I pull a spreadsheet, I have to go in and manually merge data from two accounts and that is a drag and creates another opportunity for error, especially if someone else unfamiliar with the situation was asked to do this (new employee?).

    Yes, even closed tickets should be brought along in a merge account action. If we cannot do it ourselves as Administrators, can ZenDesk do it for us?

    I believe this topic is more important to more people than this conversation thread may indicate.

    Charlie Fellenbaum

    September 03, 2013 11:45

    6
  • Chandra
    コメントアクション Permalink

    +1!!

    3
  • Cris Sandberg
    コメントアクション Permalink

    +1

    3
  • Allen
    コメントアクション Permalink

    Right now we have closed tickets in two orgs which are for the same company.

    This feature would allow us to give our subscribers a more unified view of their data.

    4
  • Yakov Shaul
    コメントアクション Permalink

    Yes. this feature is needed urgently.

    3

投稿コメントは受け付けていません。

Powered by Zendesk