I use this feature in IOM regularly when updating records for students and alumni. Some alumni are coming back for a masters or doctoral degree after doing their undergrad work here. Just replacing Current Student with Alumni when Alumni already exists on the record doesn't work for us. There are other instances where we cannot just replace an existing constituent code as well. We also have many constituents with multiple constituent codes and the one we would possible replace isn't in the same sequence number as all of the other records. This makes it impossible to use Omatic Cloud to update constituent codes for us.
There are also frequent cases where a solicit code needs to be removed, not just replaced.
This is critical for our business processes to be able to do this before fully switching to Omatic Cloud.

The ability to remove a solicit code when processing the Mailchimp unsubscribed email addresses would be very helpful. Then I could update each constituent in one step in RE NXT.

We are not able to update our data with Omatic Cloud without this.

This is crucial for organizations that have multiple constituent codes for some scenarios. Our most complicated scenario is for a university and its employees - an employee may hold several classifications simultaneously: is faculty, has an administrative role (as a department chair, dean etc.), and is a retiree (but returned from retirement). Each of these borad roles/classifications has its own consituent codes, which change over time.