so ive been using N1MM for probably 6 or 7 years now and honestly it does what i need for contests but outside of contest season i keep wishing it felt less like a war room and more like just... a normal logging program. heard a lot of people talking up Log4OM lately especially version 2 and the way it handles the QSO data and awards tracking is apparently pretty solid.

my main worry is i have like 15,000 QSOs in N1MM from various contests and regular logging and i dont want to mess up the ADIF export/import situation. has anyone actually moved a big log over to Log4OM and had it come through clean? also i run WSJT-X pretty heavily for FT8 and right now i just have it feeding into N1MM via the UDP port thing which mostly works except sometimes it just stops logging and i have to restart both programs which is annoying.

wondering if Log4OM handles the WSJT-X integration any better or if its basically the same UDP setup. not trying to abandon N1MM for contests, i know its the gold standard for that, but having two different programs for contest vs casual operating feels clunky. maybe theres a smarter way to set this up that im missing

yeah the ADIF import into Log4OM is actually pretty decent, i moved about 22k QSOs over last year and only had maybe a handful of records that came in weird and those were old ones with funky formatting anyway. the duplicate checking during import is solid so you wont end up with a mess.

the WSJT-X integration is done through the same UDP broadcast but Log4OM has a dedicated WSJT-X integration panel that shows decodes and stuff in real time, i find it a bit more stable than my old N1MM setup was. that said i still fire up N1MM the second contest season kicks in, theres just nothing that touches it for that. the two-program workflow is annoying i agree but i kind of just accepted it. run Log4OM as my main logger, when a contest starts i export whats relevant and move to N1MM, after the contest i import the contest log back. bit of a pain but not terrible once you have the workflow down.

the UDP dropout thing with WSJT-X and N1MM used to drive me crazy too. turned out for me it was a windows firewall thing blocking the port intermittently, once i added a proper inbound rule for UDP 2237 it stopped happening almost completely. might be worth checking before you go through the whole migration hassle tbh