When importing organizational relationships, Omatic Cloud tries to match on EVERY RELATIONSHIP IN THE ENTIRE DATABASE that has a similar name.

This is problematic because it creates an "all or nothing" scenario where you can either choose not to match on any relationships, which potential adds duplicate info, or if the organization name is common, it will not work at all when there are more than 30 other organizational relationships with that organization name across the whole database.

In terms of Omatic Cloud and Raiser's Edge WebView, you would need to remove all of the organizational relationships and create a master record that all of the other relationships point to. This is overly cumbersome for several reasons. Our payment plan has a constituent record limit that we cannot afford to have taken up by accounting for every organizational relationship being promoted to a full constituent. Even if they didn't have to be promoted to a full constituent, we wouldn't want to constantly monitor whether multiple random constituents work at the same place and therefor have to be pointed at the same relationship. It is possible for our most common places of employment, but having one individual relationship for all 1,400 people who work at the college also seems impractical.

ImportOmatic Classic and Raiser's Edge Database View do not have this issue. ImportOmatic Classic does not check relationships on other constituent records at all, and it can "treat any existing relationship as a match" to pull up only the relationships on the matched constituent record. From there you can open and review the existing organizational relationships, choose to send the imported information to exceptions, or even choose to update the existing relationship. This keeps constituent records clean and reduces bloat.