We've run into this issue recently as well - in our case - related to our integration with Ninja RMM.

Manually created organiations like "Organization Name" are created automatically based on the Ninja's integration like "org-name".

Moving EDR endpoints as described the article below does little when future agents will be created in the "org-name" organization automatically, later: https://support.huntress.io/hc/en-us/articles/4404012577299-Move-Agents-Between-Organizations

The other problematic issues are 1) when ITDR/SAT/SIEM items exist against the "Organization Name", it isn't possible to move these this historical data into the "org-name" organization (which is the ideal path to allow for automation of endpoint creation and prevent future issues), and 2) it's just a big headache when this should be a relatively easy database merge function.

The best way we've found for correcting for this problem is to correct our process - first creating the organization in Ninja, then allowing auto-creation of the Organization in Huntress. However, it's still not a perfect solution and we do currently have some manual cleanup ahead of us. I'm just glad we caught this problem before we got too far.

Alternatively - in our case, the Ninja integration could be re-worked to (either) allow for creating the organization name matching that which exists in Ninja exactly, or (perhaps also) matching against a duplicate organization if one is identified in Huntress, instead of the current "org-name" structure that's created by default.

+1 for this. Having issues with duplicate clients being created, would be good to merge them into one

+1 for this. The constant duplication of organizations that I've been informed is unavoidable would, at the least, be less time consuming with a merge option

I'm having this exact issue now and it is pretty time consuming. +1 for a merge feature!

This is an annoying issue for us. A lot of our client names automatically changed in our RMM because of an integration update between our PSA and RMM. I would love the ability to merge two sites and have both site-ids linked to the new merged site.

Thanks Jared! Do you think it would make the most sense to have the migrated agents adopt configuration settings that are set up in the second org or do we need more granularity there?