As an update, when these emojis are entered, everything after summary in the c_content filed of the event is deleted and the c_title field in the quick table is cleared as well. If this data is put back the event will come back and read properly, but with no emoji. Other events with emojis that apparently work, like a heart, show as random numbers of question marks in the database.

See https://sogo.nu/files/docs/SOGoInstallationGuide.html#_mysql_complete_unicode_compliance

I made the config changes, which now allows the events with odd emojis to not kill the event, but all emojis still show up as question marks in the database. I'm assuming that's because I didn't run this:

mysql -hHOST -uUSER -p -D SOGO < Scripts/mysql-utf8mb4.sql

I can't find the script, and I'm not sure if that would kill my database anyway. Thoughts? Help?

I was able to use phpmyadmin to update the existing database to use utf8mb4, but it still is converting emoticons to question marks. Fortunately not killing the event though.

This is a database encoding issue - your schema is still incorrect.

Thank you, do you have an idea of how to fix it?

You can find the script at:
https://github.com/inverse-inc/sogo/blob/master/Scripts/mysql-utf8mb4.sql

You should carefully read the header of it.

It can not correct existing invalid characters.
Only new entries will work.